Upload
frwbtnbtyni85653
View
117
Download
8
Tags:
Embed Size (px)
Citation preview
EDSFEW!!!!
Ä!!!!ä
Communication Manual
EthernetCAN
EMF2180IB
Communication module
2180 communication module (EthernetCAN)5
5−4 EDSFEW EN 4.0
5 Communication module 2180 EthernetCAN
5.1 Before you start 5.1−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Your opinion is important to us 5.1−1. . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Document history 5.1−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 General information 5.2−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Technical data 5.3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 General data and operating conditions 5.3−1. . . . . . . . . . . . . . . . .
5.3.2 Protective insulation 5.3−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.3 Dimensions 5.3−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Installation 5.4−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Elements of the communication module 5.4−1. . . . . . . . . . . . . . . .
5.4.2 Mechanical installation 5.4−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3 Electrical installation 5.4−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Commissioning 5.5−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Commissioning with the system bus configurator 5.5−1. . . . . . . .
5.5.2 Commissioning with the web server 5.5−6. . . . . . . . . . . . . . . . . . .
5.5.3 Before switching on 5.5−14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4 First switch−on 5.5−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Data transfer 5.6−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Data transfer via CAN 5.6−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.2 Data transfer via Ethernet 5.6−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Lenze codes and CANopen objects 5.7−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1 Description of the codes relevant for CAN 5.7−4. . . . . . . . . . . . . . .
5.7.2 Description of the CANopen objects implemented 5.7−16. . . . . . . .
5.7.3 Description of the general codes 5.7−18. . . . . . . . . . . . . . . . . . . . . . .
5.7.4 Description of the codes important for Ethernet 5.7−20. . . . . . . . . .
5.8 Troubleshooting 5.8−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.1 Signalling of the CANopen RUN LED and ERROR LED 5.8−1. . . . . . .
5.9 Index 5.9−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2180 communication module (EthernetCAN)Before you start
Your opinion is important to us
55.1
5.1.1
5.1−1EDSFEW EN 4.0
5.1 Before you start
Tip!
Information and auxiliary devices related to the Lenze productscan 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 togive you the best possible support for handling our product.
If you have suggestions for improvement, please e−mail us to:
feedback−[email protected]
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
2180 communication module (EthernetCAN)General information
55.2
5.2−1EDSFEW EN 4.0
5.2 General information
These instructions are valid for
Communication module Type designation from hardwareversion
from softwareversion
EthernetCAN EMF2180IB 1x 1x
These instructions are only valid together with the documentation for thestandard devices permitted for the application.
2180FEW099
Type code 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 (EPM−HXXX)
ƒ I/O system IP20 (EPM−TXXX)
The communication module is used for setting parameters during remotemaintenance or programming and commissioning the usable devices:
Validity information
Identification
Application range
Features
2180 communication module (EthernetCAN)Technical data
General data and operating conditions
55.3
5.3.1
5.3−1EDSFEW EN 4.0
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 CANbus
Max. 100
Baud rate when communicating via CAN– 20 kbit/s– 50 kbit/s– 125 kbit/s– 250 kbit/s– 500 kBit/s– 1000 kbps
when communicating via Ethernet– 10 Mbit/s– 100 Mbit/s
Voltage supply (external) viaseparate power supply
18 30 V DC, max. 100 mA (in accordance with EN 61131−2)
Operating conditions Values Deviations from the standard
Climatic conditions
Storage 1 K3 to IEC/EN 60721−3−1 − 10 ... + 60 °C
Transport 2 K3 acc. to IEC/EN60721−3−2
− 10 ... + 70 °C
Operation 3 K3 acc. to IEC/EN60721−3−3
0 ... + 60 °C
Enclosure of attachedmodule
IP20
Degree of pollution 2 acc. to IEC/EN 61800−5−1
2180 communication module (EthernetCAN)Technical dataProtective insulation
55.35.3.2
5.3−2 EDSFEW EN 4.0
5.3.2 Protective insulation
2180FEW001F
Terminal Type of insulation (according to EN 61800−5−1)
Ethernet Functional insulation
CAN bus Functional insulation
Voltage supply No insulation
2180 communication module (EthernetCAN)Technical data
Dimensions
55.3
5.3.3
5.3−3EDSFEW EN 4.0
5.3.3 Dimensions
2180FEW001B
a 117 mmb 99 mme 22.5 mm
2180 communication module (EthernetCAN)Installation
Elements of the communication module
55.4
5.4.1
5.4−1EDSFEW EN 4.0
5.4 Installation
5.4.1 Elements of the communication module
2180FEW001D
Fig. 5.4−1 Communication module EthernetCAN 2180
Pos. Name Description
Ethernet connection RJ45 socket
CAN connection Sub−D socket
Connection for voltage supply Plug connector with spring connection, 4−pole
PE connection When fitted, the communication module isautomatically connected to the DIN rail.The DIN rail must be connected to PE!
Pos. Colour State Description
(B)Yellow Off Baud rate: 10 Mbits/s
On Baud rate: 100 Mbits/s
Blinking The IP address of the module is not assignedyet; it is currently being detected.
(E)Red See 5.5−17 ERR LED
(R)Green RUN LED
(P)Green On 2180 EthernetCAN is supplied with power.
green on The connection to the Ethernet network isestablished (LINK).
green On or blinking
Data are being transmitted or received(ACTIVITY).
Note!
Refer to the instructions on the signals provided by the ERRORLED and RUN LED in the Troubleshooting chapter ( 5.8−1).
Connections
Displays
2180 communication module (EthernetCAN)InstallationMechanical installation
55.45.4.2
5.4−2 EDSFEW EN 4.0
5.4.2 Mechanical installation
2181FEW002B
Fig. 5.4−2 Snap communication module to DIN rail
2181FEW001E
Fig. 5.4−3 Unlock communication module and lift off DIN rail .
Mounting
Dismounting
2180 communication module (EthernetCAN)Installation
Electrical installation
55.4
5.4.3
5.4−3EDSFEW EN 4.0
5.4.3 Electrical installation
2180FEW008
Fig. 5.4−4 Communication via Ethernet and CAN
Step Activity Terminal(see graphic)
Additionalinformation
1. Establish a connection to the CAN bus:Plug the Sub−D plug ("EWZ0046", seeaccessories) into the communicationmodule.
5.4−5
2. Connect the following components viaEthernet with each other:
5.4−7
Communication module
PC
Servo Drives 9400
Other Ethernet nodes
3. Connect voltage supply to the plugconnector
5.4−4
Installation steps
2180 communication module (EthernetCAN)InstallationElectrical installation
55.45.4.3
5.4−4 EDSFEW EN 4.0
5.4.3.1 Voltage supply
2181FEW001G
Terminal data
Electrical connection Plug connector with spring connection
Possible connections rigid: 2.5 mm2 (AWG 12)
flexible:
without wire end ferrule2.5 mm2 (AWG 12)
with wire end ferrule, without plastic sleeve2.5 mm2 (AWG 12)
with wire end ferrule, with plastic sleeve2.5 mm2 (AWG 12)
Stripping length 10 mm
Stop!
In order to avoid damages to the pluggable terminal strips andthe contacts:
ƒ The terminal strips must be wired before plugging them in!
ƒ Pluggable terminals strips that are not assigned must beplugged on as well.
E82ZAFX013
Terminal data
Handling of pluggableterminal strips
Use of pluggable terminalstrip with spring connection
2180 communication module (EthernetCAN)Installation
Electrical installation
55.4
5.4.3
5.4−5EDSFEW EN 4.0
5.4.3.2 CAN bus connection
2180FEW001K
View Pin Assignment
16
591, 4, 5, 6, 8, 9 −
2 CAN−LO
3 CAN−GND
7 CAN−HI
Between CAN_LOW and CAN−HIGH the CAN bus has to be terminated byresistors (120). The Sub−D plug with an integrated terminating resistor(order no. EWZ0046, not included in the scope of supply) complies with therecommendation DS 102−1 of CiA.
L
EW
Z0046
OFF
ON
OFF
ON
ON
OFF
OUTIN IN IN
On Off On120 120 120
LE
WZ
00
46
LE
WZ
00
46
LE
WZ
00
46
2181FEW004
We recommend the use of CAN cables in accordance with ISO 11898−2:
CAN cable in accordance with ISO 11898−2
Cable type Paired with shielding
Impedance 120 (95 ... 140 )
Cable resistance/cross−section
Cable length 300 m 70 m/m / 0.25 0.34 mm2 (AWG22)
Cable length 301 1000 m 40 m/m / 0.5 mm2 (AWG20)
Signal propagation delay 5 ns/m
Assignment of the Sub−D plugconnector
Specification of thetransmission cable
2180 communication module (EthernetCAN)InstallationElectrical installation
55.45.4.3
5.4−6 EDSFEW EN 4.0
It is absolutely necessary to comply with the permissible cable lengths.
1. Check the compliance with the total cable length in Tab. 5.4−1.
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.4−1 Total cable length
2. Check the compliance with the segment cable length in Tab. 5.4−2.
The segment cable length is determined by the cable cross−section used andby the number of nodes. Without repeaters the segment cable lengthcorresponds to the total cable length.
Nodes
Cable cross−section
0.25 mm2 0.5 mm2 0.75 mm2 1.0 mm2
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.4−2 Segment cable length
3. Compare both values.
If the value given in Tab. 5.4−2 is smaller than the required total cable lengthfrom Tab. 5.4−1, repeaters must be used. Repeaters divide the total cablelength into segments.
Bus cable length
2180 communication module (EthernetCAN)Installation
Electrical installation
55.4
5.4.3
5.4−7EDSFEW EN 4.0
5.4.3.3 Connecting the Ethernet cable
2181FEW004A
Note!
Only use common prefabricated cables (according to ISO/IEC11801 or EN 50173) of category CAT5e.
Ethernet cable specifications
Ethernet standard Standard Ethernet (according to IEEE 802.3), 100base TX (fastEthernet)
Cable type S/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 orEN 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
100BaseTX − CrossOver Cable 100BaseTX − Standard Patch Cable
1Tx+ Tx+1
2Tx- Tx-2
3Rx+ Rx+3
4 4
5 5
6Rx- Rx-6
7 7
8 8
1Tx+ Tx+1
2Tx- Tx-2
3Rx+ Rx+3
4 4
5 5
6Rx- Rx-6
7 7
8 8
E94YCEI002
ƒ The "100BaseTX − CrossOver Cable" is used for direct coupling of PC andcommunication module.
ƒ The "100BaseTX − Standard Patch Cable" is used in conjunction withhubs and switches.
Specification of thetransmission cable
Pin assignment
Use of cables
2180 communication module (EthernetCAN)Commissioning
Commissioning with the system bus configurator
55.5
5.5.1
5.5−1EDSFEW EN 4.0
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 bemet to work with the communication module:
ƒ Microsoft Windows 2000/XP
ƒ IBM−compatible PC with IntelPentium−266 processor or higher
ƒ 128 MB main memory with Windows2000/XP
The following Lenze programs allow for a communication via thecommunication 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)
ƒ L−force Engineer
Note!
One of the programs mentioned offer alternativecommunication paths for CAN. In this case, please always selectthe communication path "OPC".
System requirements
Available Lenze programs
2180 communication module (EthernetCAN)CommissioningCommissioning with the system bus configurator
55.55.5.1
5.5−2 EDSFEW EN 4.0
Note!
The driver installation under Windows 2000/XP requiresadministrator rights!
For a perfect operation of the communication module, install the "CAN"communication software with a version 2.0. It is included in the Lenzeprograms and is loaded on the PC during the installation.
Note!
ƒ The following program version do not contain the requiredminimum 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 thedownload area of the Lenze homepagehttp://www.Lenze.com
ƒ 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 isdisplayed in the information dialogue of the system busconfigurator and other Lenze programs.
The Lenze system bus configurator for the comfortable configuration of thecommunication modules used is installed together with the CANcommunication software.
Installing the required driver
System bus configurator
2180 communication module (EthernetCAN)Commissioning
Commissioning with the system bus configurator
55.5
5.5.1
5.5−3EDSFEW EN 4.0
5.5.1.2 Configuring the communication module
Before the Lenze tools can communicate via communication module, itmust be configured accordingly.
To open the system bus configurator, select the following in the start menu
ProgramsLenzeCommunicationSystem bus configurator.
The following parameters must be set:
ƒ CAN parametersThese are saved in the communication module and contain specificdata for the CAN bus, as for instance, baud rate, parameter datachannel or time−out.
ƒ Parameters for access to the communication moduleThe communication module is an Ethernet node. Each Ethernet nodehas 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 relevantnameplate. The MAC address is firmly burnt into the device and cannotbe changed. If an Ethernet connection to the communication modulealready exists, the MAC address can be read out online. The IP address is a logical address which must be adapted to thecorresponding Ethernet network.
2180 communication module (EthernetCAN)CommissioningCommissioning with the system bus configurator
55.55.5.1
5.5−4 EDSFEW EN 4.0
1. Press the button "Add" and select the 2180 communication module.
2. Select the communication module from the list in the system busconfigurator.
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 alphanumericname, use the possible setting
ƒ via code C1216 ( 5.7−10) or
ƒ via the web interface:
2180FEW016
5. Enter the MAC address of the nameplate or detect the MAC addressonline.
6. Enter the desired IP address and transfer this online to thecommunication module. This then carries out a reset which may last afew seconds (observe LEDs!).
7. When the communication module is ready again for operation, changeto the index card "General".
8. Press the button "Diagnostics". Then, a connection to thecommunication module is tried to be established. First, it is comparedwhether the configured CAN parameters are identical with those in thedevice. If not, an adjustment is carried out.
9. Afterwards the CAN bus can be searched for connected nodes. Confirmthe safety note with "Yes" or select "No" to interrupt the diagnostics.
Steps to be taken forconfiguring thecommunication module
2180 communication module (EthernetCAN)Commissioning
Commissioning with the system bus configurator
55.5
5.5.1
5.5−5EDSFEW EN 4.0
When the communication module succeeded in communicating with thecorresponding bus nodes, the system bus node addresses of the bus nodesfound are listed in the field "Device status".
If the communication module is not able to communicate with the busnodes, an error message is displayed.
The communication module answers with its CAN address or with "0" if noaddress exists (dependent on C00350). The data telegrams forcommunicating with the communication module itself, however, are notvisible on the CAN bus.
Note!
Additional information about the configuration of thecommunication module can be found in the online help of thesystem bus configurator.
If the configuration of a communication module is successful, the Lenzetools can use it for communication.
Only the selection of the bus system used is performed in the Lenze tools, allsystem bus−specific settings and the selection of the communicationmodule are carried out exclusively via the system bus configurator.
Note!
While some of the older program versions of the Lenze tools stilloffer setting options for interrupt and I/O address, they aremeaningless in the context of the communication module 2180.
After completing theconfiguration
2180 communication module (EthernetCAN)CommissioningCommissioning with the web server
55.55.5.2
5.5−6 EDSFEW EN 4.0
5.5.2 Commissioning with the web server
The commissioning via the integrated web server is an alternative to thecommissioning with the system bus configurator.
The integrated web server enables the device to be configured by a simpleweb browser.
This function extension is available from version 1.7 onwards!
When the DHCP function is activated, the DHCP server automatically assignsan IP address to the device.
ƒ If an invalid combination of IP address and subnet mask is detected, anerror message is output via the website:
2180FEW019
ƒ In this case, both values (IP address / subnet mask) will not be saved inthe EEPROM of the communication module.
ƒ The gateway IP will only be accepted as valid if it is inside the ownnetwork (exception: Gateway IP: 0.0.0.0).
2180 communication module (EthernetCAN)Commissioning
Commissioning with the web server
55.5
5.5.2
5.5−7EDSFEW EN 4.0
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 busconfigurator.
ƒ The IP address must be located in the range that can be addressed bythe connected PC.
If one of the two prerequisites is not met, the IP address must bereconfigured using the system bus configurator:
2180FEW017
2180 communication module (EthernetCAN)CommissioningCommissioning with the web server
55.55.5.2
5.5−8 EDSFEW EN 4.0
Note!
The Lenze setting of the IP address is "0.0.0.0". With this (invalid)IP address the communication module automatically searchesduring the start an own IP address in the range 169.254.xxx.xxxaccording to APIPA.
Start your web browser and then enter as URL the IP address of the 2180communication module:
2180FEW010
Fig. 5.5−1 Entering the IP address (instead of "xxx.xxx.xxx.xxx")
The homepage of the communication module appears. You can perform alladditional configurations from this location.
2180FEW011
Assigning a fixed IP address
2180 communication module (EthernetCAN)Commissioning
Commissioning with the web server
55.5
5.5.2
5.5−9EDSFEW EN 4.0
The 2180 communication module can also dynamically obtain its IP addressfrom the DHCP server with the help of the web server using thecorresponding configuration.
2180FEW013
Note!
ƒ Since the procedure for the dynamically assigned IP addresscan seldom be found in industrial environments, its use is notrecommended.
ƒ Additional information for the configuration of an Ethernetnetwork can be found in the Lenze Ethernet CommunicationManual.
Assigning a dynamic IPaddress
2180 communication module (EthernetCAN)CommissioningCommissioning with the web server
55.55.5.2
5.5−10 EDSFEW EN 4.0
This function extension is available from version 1.7 onwards!
DHCP can be activated via code C1228 ( 5.7−13):
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 andafter DHCP is deactivated plus mains switching or reset it can still be used.
2180 communication module (EthernetCAN)Commissioning
Commissioning with the web server
55.5
5.5.2
5.5−11EDSFEW EN 4.0
All settings that can be performed under the category "Configuration" areprotected by a combination of user name and password. The default settingat delivery is as follows:
ƒ User name: Lenze
ƒ Password: Lenze
The user name and the password can be changed any number of times andare case−sensitive.
Submit serves to store the changed data in the EEPROM of the 2180communication module (EthernetCAN). They will be active after the nextrestart.
2180FEW012
Note!
This page is only used for Lenze−internal purposes and cannot beaccessed freely.
Entering user name andpassword
Firmware update ("FW update")
2180 communication module (EthernetCAN)CommissioningCommissioning with the web server
55.55.5.2
5.5−12 EDSFEW EN 4.0
The following statistics are displayed:
ƒ Current transfer rate (10/100 Mbit/s)
ƒ Transmission mode (half/full duplex)
ƒ MAC−ID of the 2180 communication module
ƒ Static parameter of the Ethernet connection
2180FEW014
Displaying Ethernet statistics
2180 communication module (EthernetCAN)Commissioning
Commissioning with the web server
55.5
5.5.2
5.5−13EDSFEW EN 4.0
After starting the 2180 communication module, alarms and events areregistered.
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 communicationmodule.
ƒ Date and time are only correct if a time server is configured.Without configuration of the time server, the time countalways starts with the restart of the communication moduleon 01.01.1970 at 0.00h.
Displaying alarms and events
2180 communication module (EthernetCAN)CommissioningBefore switching on
55.55.5.3
5.5−14 EDSFEW EN 4.0
5.5.3 Before switching on
Stop!
Prior to switching on the mains voltage, check the wiring forcompleteness, 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 toincorrectly 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.7−4)
ƒ C0351: "Set baud rate" ( 5.7−5)
Automatic addressassignment and automaticdetection of the baud rate
2180 communication module (EthernetCAN)CommissioningFirst switch−on
55.5
5.5.4
5.5−15EDSFEW EN 4.0
5.5.4 First switch−on
2180FEW001H
Fig. 5.5−2 Signalling on the front of the communication module
Pos. Colour State Description
(B)Yellow Off Baud rate: 10 Mbits/s
On Baud rate: 100 Mbits/s
Blinking The IP address of the module is not assignedyet; it is currently being detected.
(E)Red See 5.5−17 ERR LED
(R)Green RUN LED
(P)Green On 2180 EthernetCAN is supplied with power.
green on The connection to the Ethernet network isestablished (LINK).
green On or blinking
Data are being transmitted or received(ACTIVITY).
Signalling
2180 communication module (EthernetCAN)CommissioningFirst switch−on
55.55.5.4
5.5−16 EDSFEW EN 4.0
1. The initialisation phase of the periphery starts:
LED (voltage supply, green) is lit.
2. After the initialisation of the CAN controller:
LED (RUN−LED, green) is blinking.
3. Ethernet connection is established:
LED is lit.
ƒ LED displays whether the baud rate of the Ethernet connectionamounts to 10Mbits/s or 100 Mbits/s.
ƒ If the LED is blinking, the communication module is detecting its IPaddress. The communication via Ethernet is only then possible if thisprocess is completed.
The device is now ready for operation.
Signalling sequence afterswitch on
2180 communication module (EthernetCAN)CommissioningFirst switch−on
55.5
5.5.4
5.5−17EDSFEW EN 4.0
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: pre−operational, F: none
Green blinking every 0.2 sRed blinking 1 x, 1 s OFF
S: pre−operational, F: warning limit reached
Green blinking every 0.2 sRed blinking 2 x, 1 s OFF
S: pre−operational, F: node guard event
Constant green Z: operational, F: no errors
Constant greenRed blinking 1 x, 1 s OFF
Z: operational, error: warning limit reached
Constant greenRed blinking 2 x, 1 s OFF
Z: operational, F: node guarding event
Constant greenRed blinking 3 x, 1 s OFF
Z: operational, F: sync message error
Green blinking every 1 s Z: stopped, F: no errors
Green blinking every 1 sRed blinking 1 x, 1 s OFF
S: stopped, F: warning limit reached
Green blinking every 1 sRed blinking 2 x, 1 s OFF
S: stopped, F: node guard event
Tab. 5.5−1 Signalling according to DR303−3
Signalling acc. to DR303−3
2180 communication module (EthernetCAN)Data transfer
Data transfer via CAN
55.6
5.6.1
5.6−1EDSFEW EN 4.0
5.6 Data transfer
5.6.1 Data transfer via CAN
2180FEW008
Master and drive controller communicate with each other by exchangingdata messages via the CAN bus. The data area in the data message containseither network management data, parameter data or process data.
In the drive controller, different communication channels are allocated tothe parameter data and process data.
The communication module is suitable (apart from the transfer of IEC61131programs and application data, e.g. curve data) only for the transfer ofparameter data.
Parameter data (SDO, Service Data Objects) Parameter data channel
These are e. g. Operating parameters Diagnostics information Motor dataAs a rule the transfer of parameters is not astime−critical as the transfer of process data.
Provide access to all Lenze codes and allCANopen indices.
Changes to parameters are normally storedautomatically in the drive controller (noteC0003).
The structure of the CAN messages is described in the CAN communicationmanual.
2180 communication module (EthernetCAN)Data transferData transfer via CAN
55.65.6.1
5.6−2 EDSFEW EN 4.0
Note!
For the value range of the Lenze code, please refer to theoperating instructions for the drive controller (see ’Code list’).
When communication modules are used, the properties and the behaviourof a drive controller integrated into the network can be changed by a higherlevel master (e. g. a PLC).
The parameters to be changed are contained in the codes of Lenze drivecontrollers.
The drive controller codes are addressed using the index on access via thecommunication module .
The index for the Lenze code number is in the range between 16576 (40C0hex)and 24575 (5FFFhex).
Conversion formula:Index [dec] = 24575 − Lenze code number
dec hex
Index = 24575 − Lenze code Indexhex = 5FFFhex − (Lenze code)hex
Index = 24575 − 1 = 24574 Indexhex = 5FFFhex − 1 = 5FFEhex
The communication module has two parameter data channels which areboth activated in the Lenze setting.
Note!
In order to establish the compatibility with CANopen, the secondparameter data channel must be switched off via code C1200,see ( 5.7−8).
Access to the drive controllercodes
Indexing of codes using theexample C0001 (operating mode)
CANopen parameter channels
2180 communication module (EthernetCAN)Data transfer
Data transfer via Ethernet
55.6
5.6.2
5.6−3EDSFEW EN 4.0
5.6.2 Data transfer via Ethernet
The communication between PC and the communication module 2180 iscarried out using a proprietary protocol that is based on TCP/IP. The portnumber 22080 is used for the communication module.
The port number may have to be cleared if a firewall or something similar isused.
Port 3677 is used to search for communication modules.
Port 80 is used to operate the web server.
Tip!
The search via Ethernet is only possible within one network. Thetelegrams are not transmitted via routers.
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
55.7
5.7−1EDSFEW EN 4.0
5.7 Lenze codes and CANopen objects
The behaviour of the communication module is defined by settingparameters for (Lenze) codes. These codes are exchanged as part of amessage via the CAN bus.
In the following table you will find an overview of codes relevant for thecommunication module and the CAN objects implemented. Please note thereferences to additional information.
Note!
Convention for differentiating between the implementedCANopen indices and Lenze codes:
ƒ CANopen index: I− + (index)
ƒ Lenze code: C + (code number)
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
55.7
5.7−2 EDSFEW EN 4.0
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)
Leadingcolumns
Meaning
Subcode Number of the subcode
Lenze Lenze setting ("default setting) of the code
Display codeThe 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 FIX32 32 bit value with sign; decimal with 4 decimal positions
S8 8 bit value with sign
S16 16 bit value with sign
S32 32 bit value with sign
U8 8 bit value without sign
U16 16 bit value without sign
U32 32 bit value without sign
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 istransferred to the controller () / not transferred ().
CANopen The reference to the corresponding CANopen object (according to CANopenspecification DS301V402) is given () / not given ().
How to read the code table
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
55.7
5.7−3EDSFEW EN 4.0
Code Subcode Index [hex] Name see
C0002 5FFD Parameter set management 5.7−18
C0093 5FA2 Type 5.7−18
C0099 5F9C Software version 5.7−18
C0150 5F69 Drive controller status word 5.7−18
C0200 − 5F37 Software manufacturer’s productcode
5.7−19
C0202 1234
5F35 MPC 5.7−19
C0350 5EA1 CAN node address 5.7−4
C0351 − 5EA0 CAN baud rate 5.7−5
C0358 − 5E99 Reset node 5.7−5
C0359 5E98 CAN status 5.7−6
C0360 12
5E97 Telegram counter 5.7−7
C0361 12
5E96 Bus load 5.7−7
C1200 5B4F Parameter data channel operatingmode
5.7−8
C1201 5B4E Communication time−out (CAN) 5.7−8
C1202 5B4D Time limit for node search 5.7−8
C1203 5B4C Repeat tests 5.7−9
C1209 5B46 Detection of the baud rate 5.7−9
C1210 5B45 IP address 5.7−20
C1211 5B44 Subnet mask 5.7−21
C1214 5B41 MAC−ID 5.7−22
C1215 5B40 Time exceeded during automatic baudrate detection
5.7−9
C1216 5B3F User−specific device name 5.7−10
C1217 5B3E Cycle time of CAN device monitoring 5.7−10
C1219 5B3C Activation of CAN device monitoring 5.7−11
C1220 5B3B CAN device monitoring 5.7−12
C1224 5B37 Gateway 5.7−22
C1227 5B34 Delay time for search telegrams 5.7−13
C1228 5B33 Activation DHCP 5.7−13
C1229 5B32 Activation of IP settings, device reset 5.7−14
C1230 5B31 IP address 5.7−14
C1231 5B30 Subnet mask 5.7−15
C1232 5B2F Default gateway 5.7−15
Index [hex] Subindex Name See
I−1000 0 Device type 5.7−16
I−1001 0 Error register 5.7−16
I−1017 0 Producer heartbeat time 5.7−16
I−1018 0...4 Identity object 5.7−17
Overview
CANopen objectsimplemented
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
55.75.7.1
5.7−4 EDSFEW EN 4.0
5.7.1 Description of the codes relevant for CAN
Code
C0350Name
CAN node addressIndex: 0x5EA1 (24225)
Subcode Lenze Values Access Data type
− 0 1 [1] 63 (127) rw I32
RSP PS transfer CANopen:
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 adedicated node address. It can then not be addressed from the CAN bus (noparameter setting, node guarding etc.), but only serves as a dialling−infeature for reading parameters via the CAN bus.
If the communication module should have an address, check, after the baudrate has been detected, whether this address is still free. Then, theimplemented CANopen object 1000 is tried to be read. If another nodealready has this address, another free address is selected automatically.
Note!
Node addresses in the range of 64 ... 127 can only be assigned ifthe 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
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
55.7
5.7.1
5.7−5EDSFEW EN 4.0
Code
C0351Name
CAN baud rateIndex: 0x5EA0 (24224)
Subcode Lenze Values Access Data type
− 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
RSP PS transfer CANopen:
The baud rate over the CAN bus can be set using this code.
Changes to the setting are applied after:
ƒ Reconnection to the mains
ƒ 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 thecommunication module and compared with the baud rate configured.
If the two values are different, the baud rate determined is used. The baudrate 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 bedetermined. The subsequent behaviour of the communication moduledepends on the selection configured in code C0351:
ƒ Selection 0 ... 5 After a time−out that can be configured using code C1215, the CAN busis 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 ratecan be detected.
Code
C0358Name
Reset nodeIndex: 0x5E99 (24217)
Subcode Lenze Values Access Data type
− 0 0: No function rw I32
1: CAN reset
RSP PS transfer CANopen:
After a reset any changes to communication parameters such as baud rateor node address are applied.
Entries with new baud rates or changes to the node address only becomevalid after a node reset.
A node reset can be performed by:
ƒ Reconnection to the mains
ƒ Reset node via the bus system
ƒ Reset node using code C0358
C0351:Set baud rate
C0358:Reset node
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
55.75.7.1
5.7−6 EDSFEW EN 4.0
Code
C0359Name
Diagnostics of the bus statusIndex: 0x5E98 (24216)
Subcode Lenze Values Access Data type
− 0: Operational ro I32
1: Pre−Operational
2: Warning
3: Bus−Off
− 4: Stopped
RSP PS transfer CANopen:
This code displays the current operating status of the CAN controller. Herea 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 withthe following actions:
– A drive is defined as the master using code C0352. When connectingto the mains an automatic state change for the entire drive system isperformed 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. usingthe 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 nodeis 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 controlelectronics
– An excessively high bus load
– CAN node is not connected to the bus
C0359:Diagnostics of the bus status
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
55.7
5.7.1
5.7−7EDSFEW EN 4.0
ƒ Selection 3: Bus Off
The frequency of the erroneous messages has resulted in the CAN nodedecoupling itself from the bus. It is possible to switch to the"Pre−Operational" state with:
– A trip reset
– A reset node
– Reconnection to the mains
ƒ Selection 4: Stopped
Only NMT telegrams can be received.
The state can be changed to "Pre−Operational" by:
– Reconnection to the mains
– Reset node via the bus system
– Reset node via the code C0358
Code
C0360Name
Diagnostics of the telegram counterIndex: 0x5E97 (24215)
Subcode Lenze Values Access Data type
1, 2 (see table below) 0 [1] 4294967295 ro I32
RSP PS transfer CANopen:
Subcode Meaning
Messages Message counter (number of messages) 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, thecounting process starts again at 0.
Code
C0361Name
Diagnostics of the bus loadIndex: 0x5E96 (24214)
Subcode Lenze Values Access Data type
− 0 [1 %] 100 ro I32
RSP PS transfer CANopen:
Using this code the percentage total bus load can be determined. Erroneousmessages 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 areconnected, these messages are also to be taken into account.
C0360:Diagnostics of the telegramcounter
C0361:Diagnostics of the bus load
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
55.75.7.1
5.7−8 EDSFEW EN 4.0
Code
C1200Name
Operating mode − parameter data channelIndex: 0x5B4F (23375)
Subcode Lenze Values Access Data type
− 2 0 [1] 2 rw I32
RSP PS transfer CANopen:
This code indicates which of the two parameter data channels is used tocommunicate with other nodes. The unused parameter data channels canbe switched off, if required.
All Lenze controllers have two parameter data channels with differentaddressing. 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 compliancewith CANopen and there is no limitation on the address space.
In this case, the parameter data channel SDO2 is inactive.
Code
C1201Name
Communication time−out (CAN)Index: 0x5B4E (23374)
Subcode Lenze Values Access Data type
1500 0 [1 ms] 10000 rw I32
RSP PS transfer CANopen:
The time set defines the time frame within which a CAN node must respondto a request.
If there is no response of the node, the requesting module assumes that thenode is not available.
Code
C1202Name
Time limit for node searchIndex: 0x5B4D (23373)
Subcode Lenze Values Access Data type
1000 0 [1 ms] 10000 rw I32
RSP PS transfer CANopen:
For node search, the time set is regularly maintained. It must be selectedhigh 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 delaytime for search telegrams increased with code C1227.
C1200:Parameter data channeloperating mode
C1201:Communication timeout(CAN)
C1202:Time limit for node search
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
55.7
5.7.1
5.7−9EDSFEW EN 4.0
Code
C1203Name
Repeat testsIndex: 0x5B4C (23372)
Subcode Lenze Values Access Data type
0 0 [1] 10 rw I32
RSP PS transfer CANopen:
The value to be set in code C1203 indicates the number of repetitions ofthose CAN telegrams which have not reached the receiver.
The condition for this functionality is the activation of the deviceidentification with code C1219 ( 5.7−11).
This function extension is available from version 1.70 onwards!
The Lenze setting of the repeat tests was changed from 1 to 0 in order toobtain a corresponding return value from the comunication module if a busnode is not available ("DEVICE_NOT_PRESENT").
Code
C1209Name
Read out baud rateIndex: 0x5B46 (23366)
Subcode Lenze Values Access Data type
0123416
500 kbit/s250 kbit/s125 kbit/s50 kbit/s1000 kbpsnothingdetected
ro I32
RSP PS transfer CANopen:
Code C1209 can be used to determine which transfer rate was detected onthe CAN bus.
When "16" is indicated, there is no data traffic on the CAN bus.
Code
C1215Name
Time−outIndex: 0x5B40 (23360)
Subcode Lenze Values Access Data type
1000 0 [1] 60000 rw I32
RSP PS transfer CANopen:
By defining a time−out in code C1215, the baud rate (display with codeC1209) on the CAN bus can be detected.
The baud rate is not checked if the value configured in code C1215 is set tozero.
When the time−out configured in code C1215 elapses, the CAN bus isaccessed (for further information and limitations: see description of codeC0351).
C1203:Repeat tests
C1209:Read out baud rate
C1215:Time−out (automatic baudrate detection)
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
55.75.7.1
5.7−10 EDSFEW EN 4.0
Code
C1216Name
User−specific device nameIndex: 0x5B3F (23359)
Subcode Lenze Values Access Data type
<leer> see description rw VS
RSP PS transfer CANopen:
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 Gerätename is stored safe against mains failure in the communicationmodule.
Note!
The automatic transfer of the device name to a DNS server doesnot take place.
When the Lenze setting is loaded (C0002), the device name is notreset or changed.
Tip!
This code can also be configured via the gateway configurationwebsite of this communication module.
Code
C1217Name
Cycle time of CAN device monitoringIndex: 0x5B3E (23358)
Subcode Lenze Values Access Data type
5000 1000 [ms] 30000 rw U32
RSP PS transfer CANopen:
This code serves to the set the cycle time for the CAN device monitoring(C1220).
Tip!
This code can also be configured via the gateway configurationwebsite of the 2180 communication module (EthernetCAN).
C1216:User−specific device name
C1217:Cycle time of CAN devicemonitoring
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
55.7
5.7.1
5.7−11EDSFEW EN 4.0
Code
C1219Name
Activation of CAN device monitoringIndex: 0x5B3C (23356)
Subcode Lenze Values Access Data type
1 0: not activated1: activated
rw U32
RSP PS transfer CANopen:
This code serves to activate the device monitoring.
The activated device monitoring enables the detection of bus nodes withdisturbed bus communication.
Tip!
This code can also be configured via the gateway configurationwebsite of the 2180 communication module (EthernetCAN).
C1219: Activation of CANdevice monitoring
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
55.75.7.1
5.7−12 EDSFEW EN 4.0
Code
C1220Name
CAN device monitoringIndex: 0x5B3B (23355)
Subcode Lenze Values Access Data type
0 0 0 [1] 60000 rw U8
1 ... 4 (see table ) 0 0 [1] 60000 rw U8
RSP PS transfer CANopen:
This code serves to
ƒ activate the CAN device monitoring.
ƒ detect the CAN communication disturbed for each bus node and recordit 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 0: not activated 1: activated
Recording disturbed bus nodes
For this purpose, the code contains a bit mask in its subcodes 1 ... 4 in whichevery bus node (maximum number: 127) with disturbed buscommunication or when being missing is recorded by the value "1".
#The status bit immediately changes to the "0" status when thecommunication of the bus node has been re−established.#
Subcode Node mask
MSB LSB
1 31 ... ... 0
2 63 ... ... 32
3 95 ... ... 64
4 127 ... ... 96
Tip!
ƒ For test purposes, the bit mask can be described by the user.The values written in C1220 are accepted at the end of thecycle time of the CAN device monitoring (C1217).
ƒ In the »Engineer«, we recommend to switch over tohexadecimal view.
C1220: CAN devicemonitoring
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
55.7
5.7.1
5.7−13EDSFEW EN 4.0
Code
C1227Name
Delay time for search telegramsIndex: 0x5B34 (23348)
Subcode Lenze Values Access Data type
0 0 [1 ms] 100 rw I32
RSP PS transfer CANopen:
Selection Meaning
0 Quickest possible search
1 ... 10 Delay time 1 ms
11 ... 19 Delay time 10 ms
20 ... 29 Delay time 20 ms
... ...
... ...
90...100 Delay time 90 ms
Searching the CAN bus during the start of a PC program can lead to faults ifa bus is heavily loaded. In order to prevent this, a delay time between thetransmission telegrams can be set. This, however, leads to an increase of thetotal search time. If required, C1202 must be adapted accordingly.
Code
C1228Name
Activation DHCPIndex: 0x5B33 (23347)
Subcode Lenze Values Access Data type
0 0: not activated1: activated
rw U32
RSP PS transfer CANopen:
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.7−14), value "2" or "3".
The parameter setting of this code is stored immediately safe against mainsfailure in the communication module.
C1227:Delay time for searchtelegrams
C1228: Activation of DHCP
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
55.75.7.1
5.7−14 EDSFEW EN 4.0
Code
C1229Name
Activation of IP settings, device resetIndex: 0x5B32 (23346)
Subcode Lenze Values Access Data type
0 0 [1] 4 rw U32
RSP PS transfer CANopen:
The code
ƒ stores the IP adress, the network mask and the gateway address safeagainst 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 gatewayaddress are stored safe against mains failure in thecommunication module.
2 Device reset Reset of the communication module
3 Saving IP settings and devicereset
First the IP adress, the network mask and thegateway address are stored.The a device reset is executed.
Tip!
The separate storage safe against mains failure of the IP settingscan be achieved by writing subcode 4 of the following codes:
ƒ IP address: C1210 ( 5.7−20)
ƒ Network mask: C1211 ( 5.7−21)
ƒ Gateway address: C1224 ( 5.7−22)
Code
C1230Name
IP addressIndex: 0x5B31 (23345)
Subcode Lenze Values Access Data type
− 0 [1] 60000 ro U32
RSP PS transfer CANopen:
This code shows the currently active IP address.
Tip!
An IP address changed with code C1210 ( 5.7−20) will only beactive after mains switching. Up to then, the active IP addressdiffers from the configured IP address.
C1229: Activation of IPsettings, device reset
C1230: IP address
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
55.7
5.7.1
5.7−15EDSFEW EN 4.0
Code
C1231Name
Subnet maskIndex: 0x5B30 (23344)
Subcode Lenze Values Access Data type
− 0 [1] 60000 ro U32
RSP PS transfer CANopen:
This code shows the currently active network mask.
Tip!
A network mask changed with code C1211 ( 5.7−21) will onlybe active after mains switching. Up to then, the active networkmask differs from the configured network mask.
Code
C1232Name
Default gatewayIndex: 0x5B2F (23343)
Subcode Lenze Values Access Data type
− 0 [1] 60000 ro U32
RSP PS transfer CANopen:
This code shows the currently active gateway address.
Tip!
A gateway address changed with code C1224 ( 5.7−22) willonly be active after mains switching. Up to then, the activegateway address differs from the configured gateway address.
C1231:Subnet mask
C1232:Default gateway
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the CANopen objects implemented
55.75.7.2
5.7−16 EDSFEW EN 4.0
5.7.2 Description of the CANopen objects implemented
I−1000: Device type
Index
1000hex
Name
Device type
Subindex Defaultsetting
Values Access Data type
0 − 0 ... 232 − 1 ro U32
The CANopen object I−1000 indicates the device profile for this device. It isalso possible to include additional information here that is defined in thedevice 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
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 thecommunication module
0 0 0 1 0 0 0 1 Communication error
Index [hex] Subindex Name Data type Value range Rights
I−1017 − Producer heartbeattime
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 startsat the transition from the NMT state INITIALISATION to the NMT statePREOPERATIONAL (if predefined value > 0).
Note!
Unlike "node / life guarding" monitoring, the heartbeat protocoldoes not contain a Remote Transmit Request" (RTR).
It is therefore not necessary for the recipient to answer after aheartbeat.
I−1001hex:Error register
I−1017hex:Producer heartbeat time
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the CANopen objects implemented
55.7
5.7.2
5.7−17EDSFEW EN 4.0
I−1018: Module device description
Entry of vendor ID
Index [hex] Subindex Name Data type Value range Authorisation
I−1018 0 ... 4 Module devicedescription
Identity Module−specific 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
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the general codes
55.75.7.3
5.7−18 EDSFEW EN 4.0
5.7.3 Description of the general codes
Code
C00002Name
Device commandsIndex: 0x5FFD (24573)
Subcode Lenze Values Access Data type
− 0 0, 1 rw I32
RSP PS transfer PLC−STOP CANopen:
C0002 shows the status of the device command executed last. C00150 canbe used to enquire the current status of the device control.
Values(extract)
Designation Info
0 Load Def. Load Lenze setting Only possible with controller inhibit and
stopped user program.
1 Load PS Load parameter setThe parameter set stored in the memorymodule is loaded Only possible with controller inhibit and
stopped user program.
Code
C0093Name
TypeIndex: 0x5FA2 (24482)
Subcode Lenze Values Access Data type
ro FIX32
RSP PS transfer CANopen:
The display for communication module 2180 is "21800000".
Code
C0099Name
Software versionIndex: 0x5F9C (24476)
Subcode Lenze Values Access Data type
x.y(x: major version, y: index)
ro FIX32
RSP PS transfer CANopen:
Code
C0150Name
CAN node addressIndex: 0x5F69 (24425)
Subcode Lenze Values Access Data type
ro B16
RSP PS transfer CANopen:
The binary interpretation of the displayed decimal value reflects the bitstatuses of the status word:
ƒ Bit 0: Ready for operation
ƒ Bit 1: Dial−up connection is available
ƒ Bit 2: Internal error
C0002 (extract):Device commands
C0093:Device type
C0099:Software version
C0150:Status word
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the general codes
55.7
5.7.3
5.7−19EDSFEW EN 4.0
Code
C0200Name
Software manufacturer’s product codeIndex: 0x5F37 (24375)
Subcode Lenze Values Access Data type
ro VS
RSP PS transfer CANopen:
During initialisation of the module it is determined which device isconnected as a user based on the manufacturer’s product code.
Value displayed for the communication module 2180:
"33S2180F_10000".
Code
C0202Name
EKZnIndex: 0x5F35 (24373)
Subcode Lenze Values Access Data type
1 ... 4 ro FIX32
RSP PS transfer CANopen:
The corresponding octet of the manufacturers product code (MPC) isdisplayed dependent upon the subcode digit (n=1...4).
C0200:Software ID
C0202:EKZn
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes important for Ethernet
55.75.7.4
5.7−20 EDSFEW EN 4.0
5.7.4 Description of the codes important for Ethernet
Code
C1210Name
IP addressIndex: 0x5B45 (23365)
Subcode Lenze Values Access Data type
0 0 [1] 255 rw FIX32
RSP PS transfer CANopen:
The IP address is the identification number of a node (or a device) in thenetwork. Every network node receives a unique address in the network.Compared to the MAC−ID, the IP address is a logic address that can bechanged 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 inthe 169.254.xxx.xxx subnet according to the APIPA system.
The IP addresses always consist of 4 octets (4 x 28). To make the octets morereadable, they are divided by periods (e.g. 128.133.10.123).
The first octet determines the network class. The network class specifies thenumber 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
This function extension is available from version 1.70 onwards!
After the codes C1210 and/or C1211 have been changed, the combinationof IP address and subnet mask is checked for validity.
Wenn eine Ungültigkeit vorliegen sollte, wird das Gateway auf dieIP−Adresse 0.0.0.0 gesetzt und DHCP auf das dynamische Zuweisen derIP−Adresse gestellt.
C1210:IP address
2180 communication module (EthernetCAN)Lenze codes and CANopen objects
Description of the codes important for Ethernet
55.7
5.7.4
5.7−21EDSFEW EN 4.0
Code
C1211Name
Subnet maskIndex: 0x5B4D (23373)
Subcode Lenze Values Access Data type
1 ... 4 0 0 [1] 255 rw FIX32
RSP PS transfer CANopen:
The IP address, see C1210 ( 5.7−20), is superimposed by the subnet mask.The subnet mask serves to identify which part of the IP address is marked bythe 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 beentered. 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.
This function extension is available from version 1.70 onwards!
After the codes C1210 and/or C1211 have been changed, the combinationof IP address and network mask is checked for validity.
Wenn eine Ungültigkeit vorliegen sollte, wird das Gateway auf dieIP−Adresse 0.0.0.0 gesetzt und DHCP auf das dynamische Zuweisen derIP−Adresse gestellt.
C1211:Subnet mask
2180 communication module (EthernetCAN)Lenze codes and CANopen objectsDescription of the codes important for Ethernet
55.75.7.4
5.7−22 EDSFEW EN 4.0
Code
C1214Name
MAC−IDIndex: 0x5B41 (23361)
Subcode Lenze Values Access Data type
ro VS
RSP PS transfer CANopen:
Each module has a 48−bit identification, the so−called MAC−ID (Media AccessControl). The MAC−ID is stored non−volatilely 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 eachmanufacturer a so−called OUI (Organisationally Unique Identifier). The OUIrepresents the first 24 bits of the card address. The remaining bits of theaddress are assigned by the manufacturer for each card. The numbering ofeach card must be unique.
Code
C1202Name
GatewayIndex: 0x5B37 (23351)
Subcode Lenze Values Access Data type
1 ... 4 0 0 [1] 255 rw FIX32
RSP PS transfer CANopen:
If the communication module is in another subnetwork than the PC, the IPaddress of the corresponding router must be entered into this code.
Note!
The data are only accepted after the subcode 4 has been written.
C1214:MAC−ID
C1224:Gateway
2180 communication module (EthernetCAN)Troubleshooting
Signalling of the CANopen RUN LED and ERROR LED
55.8
5.8.1
5.8−1EDSFEW EN 4.0
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 andshows errors on the basis of missing CAN messages (SYNC, GUARD orHEARTBEAT). It is lit red.
No. ERROR LED STATUS Description
1 OFF No error The device is ready for operation.
2 Singlelighting up
Warning limit isreached
At least one of the error counters of the CANcontroller has reached or exceeded the warninglevel (too many error frames).
3 Flicker AutoBaud/LSS The automatic baud rate detection or LSS servicesare running. (ERROR LED and RUN LED flickeralternately).
4 Doublelighting up
Error controlevent
A guard event (NMT slave or NMT master) orheartbeat event (heartbeat consumer) hasoccurred.
5 Triple lightingup
Sync error The sync message has not been received withinthe time configured for the time monitoring ofthe communication cycle..
6 On Bus Off The CAN controller is in the bus−off state.
The CANopen RUN LED displays the CANopen−NMT status. It is lit up green.
No. CAN RUN LED STATUS Description
1 Flicker AutoBaud/LSS The automatic baud rate detection or LSS servicesare running. (ERROR LED and RUN LED flickeralternately). Optional
2 Singlelighting up
STOPPED The device in the STOPPED state.
3 Blinking PRE−OPERATIONAL
The device is in the PREOPERATIONAL state.
4 On OPERATIONAL The device is in the OPERATIONAL state.
CANopen ERROR LED
CANopen RUN LED
2180 communication module (EthernetCAN)TroubleshootingSignalling of the CANopen RUN LED and ERROR LED
55.85.8.1
5.8−2 EDSFEW EN 4.0
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 offfor 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 theLED
A short lighting up (approx. 200 ms) followed by a long off phase(approx. 1000 ms).
Double lighting up ofthe LED
LED shortly lights up twice in one sequence (approx. 200 ms),interrupted by an off phase (approx. 200 ms). The sequence iscompleted by a long off phase (approx. 1000 ms).
Triple lighting up of theLED
LED shortly lights up thrice in one sequence (approx. 200 ms),interrupted by an off phase (approx. 200 ms). The sequence iscompleted by a long off phase (approx. 1000 ms).
5.8.1.1 Operating mode − diagnostic interface
Note!
In this operating mode, the CANopen ERR LED is lit if no device isconnected.
Message states and lightingrates
2180 communication module (EthernetCAN)Index
55.9
5.9−3EDSFEW EN 4.0
5.9 Index
AApplication range, 5.2−1
BBus cable length, 5.4−6
CC0002: Device commands, 5.7−18
C0093: Device type, 5.7−18
C0099: Software version, 5.7−18
C0150: Status word, 5.7−18
C0200: Software ID, 5.7−19
C0202: EKZn, 5.7−19
C0350: CAN node address, 5.7−4
C0351: CAN baud rate, 5.7−5
C0351: Set baud rate, 5.7−5
C0358: Reset node, 5.7−5
C0359: Diagnostics of the bus status, 5.7−6
C0360: Diagnostics of the telegram counter, 5.7−7
C0361: Diagnostics bus load, 5.7−7
C1200: Parameter data channel operating mode, 5.7−8
C1201: Communication timeout (CAN), 5.7−8
C1202: Time limit for node search, 5.7−8
C1203: Repeat tests, 5.7−9
C1209:Read out baud rate, 5.7−9
C1210: IP address, 5.7−20
C1211: Subnet mask, 5.7−21
C1214: MAC−ID, 5.7−22
C1215: Automatic baud rate detection, 5.7−9
C1216: User−specific device name, 5.7−10
C1217: Cycle time of CAN device monitoring, 5.7−10
C1219: Activation of CAN device monitoring, 5.7−11
C1220: CAN device monitoring, 5.7−12
C1224: Gateway, 5.7−22
C1227: Delay time for search telegrams, 5.7−13
C1228: Activation of DHCP, 5.7−13
C1229: Activation of IP settings, device reset, 5.7−14
C1230: IP address, 5.7−14
C1231: Subnet mask, 5.7−15
C1232: Default gateway, 5.7−15
Cable cross−section, 5.4−6
Cable length, 5.4−6
Cable specification, 5.4−5, 5.4−7
CANopen objects, 5.7−1
CANopen objects implemented, 5.7−3
CANopen parameter channels, 5.6−2
Code numbers, Access via the communication module,5.6−2
Code numbers / index, Conversion, 5.6−2
Commissioning, 5.5−1
− before you start, 5.1−1
Commissioning with the system bus configurator, 5.5−1
Commissioning with the web server, 5.5−6
Connections, 5.4−1
DData transfer, 5.6−1
Data transfer via Ethernet, 5.6−3
Description of the CANopen objects implemented, 5.7−16
Description of the codes important for the Ethernetinterface, 5.7−20
Description of the codes relevant for CAN, 5.7−4
Description of the general codes, 5.7−18
Device type (I−1000), 5.7−16
Dimensions, 5.3−3
EElectrical installation, 5.4−3
Elements of the communication module, 5.4−1
Error register, 5.7−16
Examples, Indexing of Lenze codes, 5.6−2
FFirst switch−on, 5.5−15
GGeneral data, 5.3−1
HHardware version, type code, 5.2−1
2180 communication module (EthernetCAN)Index
55.9
5.9−4 EDSFEW EN 4.0
II−1000: Device type, 5.7−16
I−1001, Error register, 5.7−16
I−1017, Producer heartbeat time, 5.7−16
I−1018: Module device description, 5.7−17
Identification, 5.2−1
Index, Conversion, 5.6−2
Indexing of Lenze codes, 5.6−2
Installation, 5.4−1
− electrical, 5.4−3
− mechanical, 5.4−2
Installation of required drivers, 5.5−2
LLenze Codes, C1227, 5.7−13
Lenze codes, 5.7−1
− C00002, 5.7−18
− C0093, 5.7−18
− C0099, 5.7−18
− C0150, 5.7−18
− C0200, 5.7−19
− C0350, 5.7−4
− C0351, 5.7−5
− C0358, 5.7−5
− C0359, 5.7−6
− C0360, 5.7−7
− C0361, 5.7−7
− C1200, 5.7−8
− C1201, 5.7−8
− C1202, 5.7−8
− C1203, 5.7−9
− C1209, 5.7−9
− C1210, 5.7−20
− C1211, 5.7−21
− C1214, 5.7−22
− C1215, 5.7−9
− C1216, 5.7−10
− C1217, 5.7−10
− C1219, 5.7−11
− C1220, 5.7−12
− C1224, 5.7−22
− C1228, 5.7−13
− C1229, 5.7−14
− C1230, 5.7−14
− C1231, 5.7−15
− C1232, 5.7−15
Lenze−Codestellen, C0202, 5.7−19
MMechanical installation, 5.4−2
Module device description (I−1018), 5.7−17
OOperating conditions, 5.3−1
PPluggable terminal strip, Use, spring connection, 5.4−4
Pluggable terminal strips, handling, 5.4−4
Producer heartbeat time, 5.7−16
Protective insulation, 5.3−2
SSegment cable length, 5.4−6
Signalling, 5.5−15
Signalling acc. to DR303−3, 5.5−17
Software version, type code, 5.2−1
Specification of the transmission cable, 5.4−5, 5.4−7
System bus configurator, 5.5−2
System requirements, 5.5−1
TTechnical data, 5.3−1
Terminal data, 5.4−4
Total cable length, 5.4−6
Transmission cable, specification, 5.4−5, 5.4−7
Troubleshooting, 5.8−1
Type code, 5.2−1
VValidity of the documentation, 5.2−1
Voltage supply, 5.4−4
EDSFEW.%g%
Ä.%g%ä
Communication Manual
Remote maintenance
Preface and general informationIntroduction
11.1
1.1-1EDSFEW EN 04/2005
1 Preface
1.1 Introduction
The competitive environment of machine and system engineering calls forsolutions which optimise production costs. Thus, modular machine andsystem engineering is becoming ever more popular, as it allows individualsolutions to be developed easily and cost-effectively through the use ofmodular ”building blocks”. In addition, the remote maintenance option isalso indemandtoday. Itoffersbettersupportofcommissioningoroperatingpersonnel across almost all phases of the product life cycle, and helps tofurther reduce costs.
Choosing the right remote maintenance software and hardwarecomponents depends to a large extent on the field in which they are to beused. It is important to consider how much integration is required intoavailable systems andwhether or not any existing remote connections canalso be employed. The chapter ”Scenarios of remote maintenance” in thisCommunication Manual provides an overview of the different scenarios.
Decision support
Preface and general informationAbout this Communication Manual
11.2
1.2-2 EDSFEW EN 04/2005
1.2 About this Communication Manual
This Manual is intended for all persons who install, commission andmaintain the networking and remote service of a machine.
The manual exclusively contains descriptions of LENZE communicationmodules and software for the remote maintenance. Details on therespective bus systems can be found in the corresponding CommunicationManuals.
TheManual ismeant as an addition to theMounting Instructionswhich arepart of the scope of supply.
ƒ The features and functions of the communication modules aredescribed 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. Basicdevices are servo inverters, frequency inverters, drive PLC and motorstarters (starttec).
ƒ Notes on troubleshooting and fault elimination.
The manual does not describe the software of an original equipmentmanufacturer. No responsibility is taken for corresponding informationgiven in this manual. Information on how to use the software can beobtained from the documents of the master system.
Thetheoretical connectionsareonlyexplainedinsofarastheyarenecessaryfor comprehending the function of the corresponding communicationmodule.
Eachchapter is acompleteunitandprovidescomprehensive informationonthe relevant topic.
ƒ The Contents and Index help you to find all information about a certaintopic.
ƒ Descriptions and data of other Lenze products (controllers, drive PLC,Lenze geared motors, Lenze motors) can be found in the correspondingcatalogues, Operating Instructions andManuals. The requiredinformation can be ordered at your Lenze sales partner or downloadedas PDF file from the Internet.
Target group
Content
How to find information
Preface and general informationAbout this Communication Manual
11.2
1.2-3EDSFEW EN 04/2005
The Manual is designed as a loose-leaf collection so that we are able toinform you quickly and specifically about news and changes. Each page ismarked by the publication date.
Tip!Current documentation and software updates for Lenze productscan be found on the Internet in the ”Downloads” area underhttp://www.Lenze.com
Paper or PDF
Preface and general informationLegal regulations
11.3
1.3-4 EDSFEW EN 04/2005
1.3 Legal regulations
Lenze communication modules are unambiguously designated by thecontents 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 inthis Communication Manual.
ƒ is an accessory module which is used as an option for the Lenzecontrollers or Lenze drive PLC. Detailed information on the applicationrange can be found in the chapter ”General information”.
ƒ must be mounted and installed so that it fulfils its function and doesnot 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 communicationmodule and function module in this Communication Manual. This means:
ƒ Before you start working, read this part of the Communication Manualcarefully.
ƒ Always keep the Communication Manual close to the communicationmodule/function module during operation.
Any other use shall be deemed inappropriate!
Labelling
Manufacturer
CE conformity
Application as directed
Preface and general informationLegal regulations
11.3
1.3-5EDSFEW EN 04/2005
The information, data, and notes met the state of the art at the time ofprinting. Claims referring to communication modules/function moduleswhich have already been supplied cannot be derived from the information,illustrations, and descriptions given in this Communication Manual.
The specifications, processes, andcircuitrydescribed in thisCommunicationManual are for guidanceonly andmustbe adapted to your ownapplication.Lenzedoesnottakeresponsibility forthesuitabilityof theprocessandcircuitproposals.
The specifications in this Communication Manual describe the productfeatures without guaranteeing them.
Lenze does not accept any liability for damage and operating interferencecaused by:
ƒ Disregarding this Communication Manual
ƒ Unauthorised modifications to the communication module/functionmodule
ƒ Operating errors
ƒ Improper working on and with the communication module/functionmodule
See terms of sales and delivery of the Lenze Drive Systems GmbH.
Warranty claims must be made to Lenze immediately after detecting thedeficiency 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/OperatingInstructions
D -
Liability
Warranty
Disposal
GuideGlossary
22.1
2.1-1EDSFEW EN 04/2005
2 Guide
2.1 Glossary
A
APIPA Automatic Private IP-AddressingThis standardised mechanism enables an Ethernet device to get an IPaddress on its own.The following IP address area is reserved for APIPA : 169.254.xxxx.xxxx.
ASP Application Service Provider: ASPs manage the communicationinfrastructure in the company.
AT Most of the modems (Hayes-compatible) are addressed via the AToperations set. The AT commands serve to initialise the modem and toestablish 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 viagateways or routers
Bus server Fieldbus-specific OPC server to DRIVECOM specification.
C
CAL CAN Application LayerCommunication standard (CiA DS 201-207), which provides the objects,protocols, and services for the event or polling-controlled transmissionof CANmessages and the transmission of greater data ranges betweenCAN nodes. Furthermore, CAL offers effective processes for anautomatic assignment of message identifiers, the initialisation andmonitoring of network nodes and the assignment of an individualidentification to network nodes.
CAN Controller Area Network”Serial, message-oriented and not node-oriented bus system for max. 63nodes.
CANopen Communication profile (DS301, version 4.01), which has been developedin conformity with the CAL under the umbrella association of the CiA(”CAN in Automation”).
CiA CAN in Automation (e. V.)International users’ and manufacturers’ organisation which has thetarget to impart knowledge on the internationally standardised CANbus system (ISO 11898) worldwide and advance the technicaldevelopment.Internet: http://www.can-cia.org
Code Parameters of Lenze devices for setting the device functions.
COM ComponentObjectModelWindows-based technology which enables the communication betweensoftware components via standard interfaces
Controller Generic term for Lenze frequency inverter, servo inverter and PLCs.
GuideGlossary
22.1
2.1-2 EDSFEW EN 04/2005
D
DCOM Distributed ComponentObjectModelCOM serves to distribute the objects to be executed to variouscomputers within on local area network.
DHCP Dynamic Host Configuration ProtocolThe parameters IP address, subnet mask and gateway can be centrallyfiled within one network. This can lead to simplification in case of greatnetworks. When a device is started, it gives its MAC address to the DHCPserver and requests the other parameters. This type of networkconfiguration is very common in the office world, but still ratherunusual in the field of industrial communication. Reason: Some DHCPservers assign the IP addresses dynamically, i. e. at each start the samedevice can be assigned with another IP address. This may cause thedevices to not be identified via their IP addresses anymore. However,there are DHCP servers the IP addresses of which can be reserved forspecial terminals. Such DHCP servers are also useful in the industrialfield.
DNS Domain Name SystemIt is also possible to work with names instead of an IP address within anetwork. Each IP address can be assigned with a name. The names aremanaged via a DNS server.
DRIVECOMUserGroup e.V.
Is an association of international drive manufacturers, universities, andinstitutes which has the target to develop a simple integration of drivesin open automation systems.Internet: http://www.can-cia.org
DriveServer Lenze software which serves to implement a simple integration ofdrives into open automation structures based on OPC.
G
Gateway Normally, there is not only one Ethernet segment but a network ofseveral segments that are coupled via defined transitions, gateways orrouters. With a change from one segment to another, the medium canalso change, e. g. when routing via a telephone network. The net ID,which is part of the IP address and the subnet mask show that there aredifferent segments. If it is noticed that an addressed receiver is notlocated in the same segment, the message is transmitted to theconfigured gateway address, which is responsible for the forwarding.
H
HTML Hyper TextMarkup Language. Text-based file format used for webpages. It includes the text itself and instructions for representations andreferences to other documents.
HTTP Hypertext Transfer Protocol. Protocol for transmitting HTML documents.
I
IP address Internet ProtocolEach network node has one IP address which must be definite within anetwork. It is a ”logic” address which can be changed per software (cp.MAC address). It consists of 32 bits. It is always indicated by fourdecimal numbers separated by a dot (dot notation) for betterreadability.The IP address consists of a net ID and a host ID. The net ID describes thenetwork segment and the host ID describes the node. The division of the32 bits into net ID and host ID depends on the class of the IP address,which can be detected from the first byte.
L
LECOM Lenze bus system based on RS232, RS485 or optical fibre
GuideGlossary
22.1
2.1-3EDSFEW EN 04/2005
M
MAC address Media Access ControlThe MAC address is unequivocal worldwide and cannot occur twice. It isoften printed on the device and cannot be changed. This unequivocaladdress enables the device to be addressed at any rate, independent ofthe 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 MACaddress is represented by six bytes in hexadecimal form, the singlebytes being separated by dots. The first three bytes refer to themanufacturer, 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 NetworkmanagementThe service element network management (NMT) provides functions forconfiguration, initialisation and monitoring of the network nodes in thedistributed system.
O
OLE Object Linking and EmbeddingInserting functional objects in other applications, e. g. a MicrosoftExcel table in a MicrosoftWord document.
OPC OLE for Process ControlDefines an interface based on the MicrosoftWindows technologiesOLE, COM and DCOM, which enables a data exchange between thedifferent automation devices and PC programs without driver andinterface problems.Internet: http://www.opcfoundation.org
P
PDF Portable Document FormatThis file format is developed by the Adobe company for exchangingelectronic documents. Adobe’s freely available software AdobeReader serves to display and print PDF files, independent of theapplication and platform used.
PLC Programmable logic controller”.
Port number The TCP telegram contains a port number. It shows which applicationprogram is to obtain the data.Example: Port number 80 stands for the HTTP protocol which is used forthe transmission of HTML documents that can be displayed with a webbrowser.
GuideGlossary
22.1
2.1-4 EDSFEW EN 04/2005
S
SNMP Simple NetworkManagement Protocol
SOAP SimpleObject Access ProtocolDefines XMLmessages that can be exchanged between heterogeneousapplications per Internet by means of HTTP.
Subnet mask Network segments are described via the net ID (cp. IP address). If thenumber of the network segments is not enough, a segment can befurther divided. If, for instance, the class of the IP address permits thenet ID to have a length of 16 bits, the 16-bit net ID can be furtherdivided. The subnet mask consists like the IP address of 32 bits whichare represented in four decimal numbers separated by dots. Those bitsthat are to be used to distinguish a network segment must be set to 1 inthe subnet mask, the others must be set to 0. The subnet mask255.255.255.0, for instance, would cause the IP address with a net ID ofonly 16 bits to be continued to be used with 8 bits to identify differentnetwork segments. If the receiver of an IP telegram is located in anothernetwork segment, the gateway address is activated (cp. gateway).
System bus (CAN) Lenze bus system following the communication profile CANopen(DS301, version 4.01).
T
TCP Transport Control ProtocolThe data transmission based on IP protocols is not secured, i. e. errorsmay occur during the transmission. Therefore a master protocol isrequired which recognises and corrects these faults and ensures that thetelegramwill be repeated. The TCP is a connection-oriented protocolwhich provides the user data with a check sum. Moreover, each datapackage gets a sequence number. If bigger data volumes aretransmitted, a segmentation is done and the data are distributed toseveral telegrams. In order to recover the original data the sequencenumber is used.
U
UDP User Datagram ProtocolLike the TCP, the UDP is a protocol based on IP. It uses a connectionlessservice and is therefore faster than TCP. The disadvantage is that nofeedback is created with regard to a successful data transmission. Thus,another check through the application program is required. Sequencesof longer data are neither supported.
V
VPN Virtual Private NetworkA technology which enables confidential data to be transported viaopen networks such as the Internet.
X
XML ExtensibleMarkup Languageis similar to HTML but with user-definable structures.
Safety instructionsContents
3
3-1EDSFEW 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 instructionsPersons responsible for safety
33.1
3.1-1EDSFEW EN 04/2005
3.1 Persons responsible for safety
An operator is any natural or legal person who uses the drive system or onbehalf of whom the drive system is used.
The operator or his safety personnel is obliged
ƒ to ensure the compliance with all relevant regulations, instructions andlegislation.
ƒ to ensure that only qualified personnel works on and with the drivesystem.
ƒ to ensure that the personnel has the Operating Instructions availablefor all work.
ƒ to ensure that all unqualified personnel are prohibited fromworkingon 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 - areauthorised by the person responsible for the safety of the plant to performthe required actions and who are able to recognise potential hazards.(Definition for skilled personnel to VDE 105 or IEC 364)
Operator
Qualified personnel
Safety instructionsGeneral safety instructions
33.2
3.2-1EDSFEW EN 04/2005
3.2 General safety instructions
ƒ These safety instructions do not claim to be complete. If you have anyquestions or problems please contact your Lenze representative.
ƒ The communication module meets the state of the art at the time ofdelivery and generally ensures safe operation.
ƒ The data in this manual refer to the stated hardware and softwareversions of the communication modules.
ƒ The communication module may create a hazard for personnel, for theequipment itself or for other property of the operator, if:
– non-qualified personnel work on and with the communicationmodule.
– the communication module is used improperly.
ƒ The specifications, processes, and circuitry described in this Manual arefor guidance only and must be adapted to your own specificapplication.
ƒ Provide appropriate measures to prevent injury to persons or damageto material assets.
ƒ The drive systemmust only be operated when it is in perfect condition.
ƒ Retrofitting or changes of the communication module are generallyprohibited. In any case, Lenze must be contacted.
ƒ The communication module is a device intended for use in industrialpower systems. During operation, the communication module must befirmly connected to the corresponding controllers. In addition, allmeasures described in the Manual of the controller used must betaken. Example: Mounting of covers to ensure protection againstaccidental contact.
Safety instructionsDefinition of notes used
33.3
3.3-1EDSFEW EN 04/2005
3.3 Definition of notes used
The following signal words and symbols are used in this documentation toindicate 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 toprevent dangerous situations)
Pictograph and signal word Meaning
Danger!
Danger of personal injury through dangerouselectrical voltage.Reference to an imminent danger that may result indeath or serious personal injury if the correspondingmeasures are not taken.
Danger!
Danger of personal injury through a general sourceof danger.Reference to an imminent danger that may result indeath or serious personal injury if the correspondingmeasures are not taken.
Stop!Danger of property damage.Reference to a possible danger that may result inproperty damage if the correspondingmeasures arenot 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 scenariosContents
4
4-1EDSFEW 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. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote maintenance scenariosIntroduction
Customer benefit by remote maintenance
44.1
4.1.1
4.1-1EDSFEW EN 04/2005
4.1 Introduction
4.1.1 Customer benefit by remote maintenance
Remotemaintenance in the different life cycle phases of a product providesthe following customer benefit:
Advantage Customer benefit
More efficient problem solving by fast remotesupport from the systemmanufacturer orcomponent supplierFaster response times, shorter development timeDesign engineers are available in the central officeBetter availability of the specialists of the system andcomponent manufacturerKnow-how transfer betweenmounting site andcompany and company headquarters
Time saving, production can beginearlier
Advantage Customer benefit
Faster error diagnosis, measures for eliminatingerrors are implemented faster, short response timeLower travel costs, better applications planningIncrease of the customer loyalty, developing newbusiness areasService can be better prepared - The right man withthe right spare part
Shorter standstill times, lowercostsIncrease of productivityIncrease of competitiveness
Advantage Customer benefit
Direct control of the functions without on-sitepresenceCost savings
Increase of productivity thanks toimproved process control
Phase: Project planning
ConfigurationParameter settingProgramming
Phase: Service / maintenance
DiagnosticsTroubleshootingFault eliminationSystemmaintenanceSoftware updates
Phase: Production
Process optimisationProduction monitoringQuality assuranceRecipe change
Remote maintenance scenariosIntroductionInternal and external remote maintenance
44.14.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, automobileindustry, packaging technology, or process engineering, greatcommunication systems are designed for themanufacturing plantwithin abuilding.
The components and networks required for the infrastructure are installedfor 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 plantoperators:
ƒ Visualisation of the plant situation down to the lowest level from acontrol room.
ƒ Influence on the process and the system components down to thelowest 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 thesystem)
– 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 thefield level (fieldbus)
ƒ Control access to secondary devices
Customer requirements
Technical requirements
Remote maintenance scenariosIntroduction
Internal and external remote maintenance
44.1
4.1.2
4.1-3EDSFEW EN 04/2005
4.1.2.2 External remote maintenance
Theclassical expression ”remotemaintenance”describes the remoteaccessvia 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 adistance.
ƒ Influence on the process and the system components down to thelowest level from a control room.
The customer requirementsgives rise to the technical requirement that is tomake thedataexchange transparent fromthedistanceviaany telephoneorInternet connections to the plant.
Connection to the plant means
ƒ A control is the communication partner of the remote connection. Acontrol access takes place, cp. ( 4.1-6).
ƒ A controller is the communication partner of the remote connection.Further controllers are interconnected via an internal bus. Gatewayfunctions in the controller is required.
Infrastructure
Customer requirements
Technical requirement
Remote maintenance scenariosIntroductionTerminal access
44.14.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 thesame interface as the system PC. One of the first solutions for this methodin WindowsR environment was the PC program pcAnywhereR.
Thismethod is unfavourablewhen, for instance, themaintenance staff hasto set another interface than the one the machine operator requires tooperate his system for reading out the drive information. Furthermore, allsoftware packages must be installed on the machine computer. A freeinformation access to data, e. g. of a drive is typically not given (e. g. OPCDriveServer is required).
Another method is applied for the MicrosoftR Terminal Server. It providesthe opportunity to start and operate the application from a client(e. g. maintenance PC) on which the software is not installed. Every user ofthe Terminal Server starts an own application entity. Thus, the applicationdoes not need to fulfill any special requirements in terms of theimplementation except that it must provide the option to enable severalusers to process the same data at the same time.
A disadvantage is that a PCmust be available in themachine.Moreover, thetransparent data access cannot be guaranteed without further measures(e. g. OPC-DriveServer) and the complete maintenance software must beinstalled on the machine PC.
WindowsRXPR supports the remote desktop connection. Here, the entirecontentof thescreen is forwardedtoanotherPCwithina localareanetwork.
Redirecting the terminal
Microsoft Terminal Server
Remote desktop connection
Remote maintenance scenariosIntroduction
Transparent data connection
44.1
4.1.4
4.1-5EDSFEW EN 04/2005
4.1.4 Transparent data connection
The transmission of complete user interfaces is affected by considerabledelay timeswith regard to operation due to the toohigh data volumes tobetransmitted. 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 remotemaintenancescenarios:
Connecting path
1. Classical fieldbuses
2. Ethernet
3. Modem
4. ISDN
5. GSM
6. Internet
The transparent transmission of fieldbuses via remote connections areindispensable for current mechanical engineering applications. In thegeneral DV environment, however, special solutions are required. Forcoupling Ethernet components, standard devices which have alreadybecome established in the office communication.
The implementation of different solutions requires a varying degree ofspecial know-how.Many of the solutions shown here do not demandmoreknow-how than usually required for the fieldbus-based applications. Thosesolutions which require further IT knowledge are marked correspondingly.
Remote maintenance scenariosIntroductionControl access
44.14.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 beremote-maintained. This is the casewhen, for instance, a control is providedwith the exclusive bus access to a device. If so, the controlmust provide thehigher-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 theaccess 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.
Remote maintenance scenariosTechnical scenariosSolution overview
44.2
4.2.1
4.2-7EDSFEW EN 04/2005
4.2 Technical scenarios
4.2.1 Solution overview
Switched connection 4 2-8Switched connection 4.2-8
CAN via modem 4 2-9CAN via modem 4.2-9
Diagnostic interface 9400 via modem 4 2-10Diagnostic interface 9400 via modem 4.2-10
CAN via ISDN or GSM 4 2-11CAN via ISDN or GSM 4.2-11
Teleservice with S7 control 4 2-12Teleservice with S7 control 4.2-12
Ethernet connection 4 2-13Ethernet connection 4.2-13
Direct Ethernet connection 4 2-14Direct Ethernet connection 4.2-14
CAN via Ethernet 4 2-14CAN via Ethernet 4.2-14
9400 Ethernet communication module 4 2-169400 Ethernet communication module 4.2-16
S7 Ethernet connection 4 2-16S7 Ethernet connection 4.2-16
S7 via IBHLink 4 2-17S7 via IBHLink 4.2-17
Motion Control ETC 4 2-17Motion Control ETC 4.2-17
Connection via PC 4 2-18Connection via PC 4.2-18
System bus (CAN) 4 2-18System bus (CAN) 4.2-18
LECOM 4 2-19LECOM 4.2-19
S7 via MPI / PROFIBUS 4 2-20S7 via MPI / PROFIBUS 4.2-20
PROFIBUS 4 2-21PROFIBUS 4.2-21
Internet connection 4 2-22Internet connection 4.2-22
Remote maintenance scenariosTechnical scenariosSwitched connections
44.24.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 ofremote maintenance.
The installation expenses are low due to the laying of a simple analoguetelephone line to thesystem.Theaccessprotectioncanbeeasily achievedbymeansofpasswordmechanismandcallback.A lockableswitch, for instance,is a further protectivemeasure by activating the telephone line only in caseof need.
Isolated applications relating to the single components aredisadvantageous. This, in turn, could increase the installation expenses andcomplexity of the remote maintenance due to the remote maintenancewith devices of different manufacturers (and thus different modems).
Connecting the single components to be remote-maintained to ahigher-level system put things right. Therefore, however, comprehensiveconsiderationsconcerningsafetyare required.Often, suchtaskscannotonlybe solved by the systemmanufacturer but need to be coordinatedwith theresponsible IT department. For this reason, the switched connections are acommon and preferred solution.
Remote maintenance scenariosTechnical scenarios
Switched connections
44.2
4.2.2
4.2-9EDSFEW EN 04/2005
4.2.2.1 CAN via modem
ModemCAN 2181
System bus (CAN)
Analog telephonenetwork
2180FEW102
The communication module 2181 ModemCAN enables the CAN bus to beconnected to an analog telephone line. The communication module isprovidedwith an analogmodemwhich is approved in all countries that areinternationally relevant and thus permits a worldwide remotemaintenance. If required, an external modem can be connected if theinternal modem is not suitable in the corresponding country or a GSM orISDNmodem is needed.
The communication module offers a password function as accessprotection. Furthermore, it is possible to configure the device so that aconnection can only be established after calling back a preconfiguredtelephone number.
Telephone CAN
Diagnosticinterface 9400
Internalmodem
Externalmodem
2180FEW103
Remote maintenance scenariosTechnical scenariosSwitched connections
44.24.2.2
4.2-10 EDSFEW EN 04/2005
4.2.2.2 Diagnostic interface 9400 via modem
ModemCAN 2181
System bus (CAN)
Analog telephonenetwork
ETHERNET Powerlink
2180FEW104
In addition to the system bus (CAN) interface the communication module2181 ModemCAN offers a diagnostic interface which can be directlyconnected with the controllers of the 9400 series. It is particularly suitablefor the temporary connection to a system. The Gateway function in the9400 serves to access all other devices which are interconnected via thesystem bus (CAN) or ETHERNET Powerlink. In case of a fixed installation, adirect connection to the system bus (CAN) is to be preferred.
Remote maintenance scenariosTechnical scenarios
Switched connections
44.2
4.2.2
4.2-11EDSFEW EN 04/2005
4.2.2.3 CAN via ISDN or GSM
Telephone network
ISDN
GSM
ISDN
GSM
System bus (CAN)
ModemCAN 2181
2180FEW105
In connection with modems of original equipment manufacturers it ispossible to use the communication module 2181 ModemCAN also forremote maintenance via GSM or ISDN systems. A condition for this is thatthesemodems canbeaddressedvia a RS232 interface and react to standardAT commands.
Remote maintenance scenariosTechnical scenariosSwitched connections
44.24.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 ofSiemens. If the Siemens control is already provided with a remotemaintenance connection, it isuseful touse it for remotemaintenanceof thecontrollers as well.
The remote connection is established via an analog telephone line with amodemwhich isconnectedtotheteleserviceadapter.This is thenconnectedto 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 partswhichmustbe installedonthePCwhich isusedforremotemaintenanceanda librarywith functionblocks whichmustbe integrated into theS7program(this solution corresponds to the concept ”control access”, see ( 4.1-6)).
Remote maintenance scenariosTechnical scenariosEthernet connection
44.2
4.2.3
4.2-13EDSFEW EN 04/2005
4.2.3 Ethernet connection
The simplicity and comprehensibility of the solutions described before areadvantageous for smaller systems. For bigger systems, however, it isunfavourable that single machine parts or even single devices require anindependent telephone line. Such systems requirea solutionwith auniformaccesspathviawhichall componentscanberemote-maintained, ifpossible.
The access to remote-maintained components via Ethernet is favourable.For remoteaccess toEthernetnetworks tried-and-testedstandardsolutionsexist which can be selected according to the demands required in terms ofsafety, availability and different transmission media.
Many devices already have Ethernet interfaces on board. If these are notavailable, theEthernetconnectioncanbeimplementedbymeansoffieldbusconverters. The corresponding solutions are described in the following.
Remote maintenance scenariosTechnical scenariosEthernet connection
44.24.2.3
4.2-14 EDSFEW EN 04/2005
4.2.3.1 Direct Ethernet connection
Ethernet
EthernetCAN 2180
System bus (CAN)
2180FEW107
The communication module 2180 EthernetCAN connects the system bus(CAN) to a higher-level Ethernet network. Thus, the fieldbus nodes can beintegrated into higher-level systems. This enables already availablenetworks (in-house network) to be used for data transmission and the useof central remote maintenance accesses (Remote Access Services).
CAN via Ethernet
Remote maintenance scenariosTechnical scenariosEthernet connection
44.2
4.2.3
4.2-15EDSFEW EN 04/2005
Example of remote maintenance via ISDN:
ISDN telephonenetwork
ISDN
System bus (CAN)
Ethernet
System bus (CAN)
EthernetCAN 2180
2180FEW108
For this solution, standard ISDN routers or PC cards are used.
Besides the applications already described, the communication module2180 EthernetCAN also provides for the implementation of the concept”without considering the control“, see ( 4.1-6). If the control has anEthernet connection, a central remote maintenance of control andcontrollers is possible via Ethernet. In contrast to the control access whichrequires the exact knowledgeof the control and special functionblocks, thissolution is independent of the type of control.
Ethernet
System bus (CAN)
Fieldbus
EthernetCAN 2180
2180FEW109
Remote maintenance scenariosTechnical scenariosEthernet connection
44.24.2.3
4.2-16 EDSFEW EN 04/2005
The 9400 device series already offers a direct connection to Ethernet via anoption module. This serves to directly remote-maintain these devices bymeans of standard infrastructural components as ISDN routers (cp. 3.2.3.1).The gateway function integrated in the 9400 serves to access thecomponents connected to the system bus (CAN).
Ethernet
System bus (CAN)
2180FEW110
The S7 controls of Siemens can be equipped with an Ethernet interface viaa communication processor. This interfacemodule provides the integrationintohigher-level systems. TheOPCDriveServer S7 serves toaccess the Lenzecontrollers connectedtoPROFIBUSthroughthecontrol andto connect themindirectly with the Ethernet and the higher-level remote maintenancesystem.
Ethernet
PROFIBUSPROFIBUS
OPC DriveServer
Bus server S7
2180FEW111
9400 Ethernetcommunication module
S7-Ethernet connection (CP)
Remote maintenance scenariosTechnical scenariosEthernet connection
44.2
4.2.3
4.2-17EDSFEW EN 04/2005
The IBHLink of the IBHSoftec company is a simple alternative to the S7communication processor. It is a cable which has an Ethernet connector onone side and anMPI connector on the other side. This is the slower solutionthan 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, ithas twoCANconnectionsonwhich theaxisor further I/OterminalsandCANdevices are located. The integrated gateway function in the ETC control alsoenables the access to the lower-level devices at the CANbus. A condition forthis is the installation of the OPC bus server for the ETC control on the PC.
Ethernet
CAN I/O
CAN Drive
ETC
2180FEW112
S7 via IBHLink
Motion Control ETC
Remote maintenance scenariosTechnical scenariosEthernet connection
44.24.2.3
4.2-18 EDSFEW EN 04/2005
4.2.3.2 Connection via PC (connection via Ethernet technology)
Inorder touse the advantages ( 4.2-13 ff.) of theEthernet, it is required to
ƒ provide devices with an Ethernet interface or
ƒ use special gateways which have an Ethernet connection (as separatedevices or implicitly by a control).
An alternative to this are the PC-based systems. Here, the PC assumes theimplementation of the fieldbus protocol with a software interface suitablefor the Ethernet. In this connection, the OPC specification (OLE for ProcessControl) has developed into the industry standard. If an industry PC with acorresponding fieldbus card is available in a system, the PC can be used asEthernet gateway based on an OPC server:
LenzeoffersOPCservers intheformofpackages.TheOPCDriveServer issuchapackage. It contains, amongother things, abus-specificOPCserver forCANwhich is complemented by the device-specific OPC server (DriveServer).
The OPC protocol which has priority over the DriveServer, is suitable for theEthernet networks. Each computer connected to the Ethernet principallyallows the access to the DriveServer. The access protection concerning theDriveServer is controlled via Windows mechanisms (DCOM).
OPC DriveServer
Bus server - system bus
LAN or remote connection
System bus (CAN)
2180FEW113
Both computers can be directly connected via Ethernet which results in abetter structuring within a large system. Furthermore, it is also possible tocouple the computers via a remote connection (Remote Access Service).Basically, all options described in ( 4.2-13 ff.) apply.
System bus (CAN) ,OPC DriveServer
Remote maintenance scenariosTechnical scenariosEthernet connection
44.2
4.2.3
4.2-19EDSFEW EN 04/2005
In addition to the bus server for the system bus (CAN) the DriveServerpackagecontainsabusserverwhichsupports theserial LECOMprotocol.Theresultingarchitecture fullycorrespondstotheonedescribedbefore,onlythebus system is different.
OPC DriveServer
Bus server LECOM
Ethernet
2180FEW114
LECOM (DriveServer)
Remote maintenance scenariosTechnical scenariosEthernet connection
44.24.2.3
4.2-20 EDSFEW EN 04/2005
If S7 controls are involved in the communication system, the OPCDriveServer in the S7 variant can also be used.
As mentioned before, there are several options of remote maintenance inconnection with S7 controls, as for instance the direct switched connection( 4.2-8) or the access via Ethernet interface modules ( 4.2-13). Alloptionsbasically need theOPCDriveServer S7. The controller andS7 controlare always connected via the PROFIBUS. If the system includes a PC, it is alsopossible to establish a remote maintenance with OPC technology. In thiscase, you are independent of the communication system between the PCand S7.MPI or PROFIBUS can also be used. Noother hardware is used for theEthernet connection, except for the PC.
OPC DriveServer
Bus server S7
MPI or PROFIBUS
PROFIBUS PROFIBUS
2180FEW115
S7 via MPI / PROFIBUS
Remote maintenance scenariosTechnical scenariosEthernet connection
44.2
4.2.3
4.2-21EDSFEW EN 04/2005
Unlike the systembus (CAN), PROFIBUS is a centrally controlled system. Thismeans that basically only the bus master can access the single nodes. Itfollows that the control access is required, see ( 4.1-6).
In addition to the control master (class 1), the PROFIBUS defines anothermaster (class 2) which can be used for diagnostic purposes. Irrespective ofthe control it is possible to establish a connection with the bus via a furtherPROFIBUS interface module for diagnostic purposes.
Conditions for such a solutions are that
ƒ the control accepts a class-2-master (set corresponding parameters, ifrequired)
ƒ the PROFIBUS stations accept the access to a class-2-master. For this,check if the corresponding communication module supports the acyclicDP-V1 services of the PROFIDrive profile V3.1 for parameter setting.
PROFIBUS
2180FEW116
PROFIBUS
Remote maintenance scenariosTechnical scenariosConnection via the Internet
44.24.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 arecountrieswhichcanbeaccessedmoreeasilyvia Internet thanvia telephone.This results in the demand to use the Internet as a remote maintenanceconnection as well.
Basically, this demand is no problem since Ethernet connections can beimagedon the Internet ina transparentway.However, it is problematic thata permanent connection to an open network involves considerable risks. Inaddition to the technical conversion of the datawith regard to the Ethernetrequires measures in terms of access protection to be protected againsthackers or viruses.Thus, the main task is to complement the solutions described in chapter4.2.2 to 4.2.3.2 by the safety requirements and co-ordinate this with therespective IT departments of the plant operators. This task is not the focusof Lenze.
The following subchapters are suggestions of how a remote maintenancecould be realised via the Internet and which elements play a role. Theconcrete structure, however, must be specially adjusted. For this purpose,Lenze can give the names of suitable service providers, who carry out suchadjustment between the IT departments involved, suggest suitableinfrastructural components and commission the networks.
In the following, some terms are explained which play a role in the field ofaccess 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 consultingthe IT service providers involved.
4.2.4.1 Authenticity
Theglobalaccessoptionsvia Internetrequireasophisticatedsafetyconcept.The significance of the data integrity in a company depends on the type ofdata to be transmitted. Customer and development data are much moresensitive thanmere product data sheets for sales purposes. If a high safetystep is required, integrity and data confidentiality must be ensured inaddition to authenticity.
Authenticity means to be assured of the identity of a communicationpartner. The user is identified via the name and password. Moreover, theaccess 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.
Remote maintenance scenariosTechnical scenarios
Connection via the Internet
44.2
4.2.4
4.2-23EDSFEW EN 04/2005
4.2.4.2 Integrity
In order to ensure integrity (i. e. to be assured to have received data in anunmodified form) and communication confidentiality, differentcryptographic methods are used. The approach via a VPN (Virtual PrivatNetwork)uses suchencryption techniques.AVPNenablesprivatedata tobetransmitted safely via a public, unsecure medium such as the Internet. Asecure transmission is achieved by ”Tunnelling“ technology and differentsafety procedures. ”Tunnelling” means the integration of a protocol intoanother. This enables the transport of any protocol via IP. Known tunnellingprotocols are, for example, PPTP (Point-to-Point Tunnelling Protocol) andL2TP(Layer2TunnellingProtocol).ThemechanismsforVPNsafetywhicharedefined in the IP-secstandard,are integrated into theseprotocols. The resultis a safe ”communication tunnel“ between automation site and mobileservice staff.
4.2.4.3 Firewalls
VPN systems are available as dedicated solutions or in connection with afirewall system. As soon as a local network is connected to the Internet, afirewall system should be an integral part of the safety concept. The basictask of a firewall system is to ensure an uninterrupted access of the user ofthe private network (Intranet) to the public network (Internet) and, at thesametime,protect theowndatanetworkfromexternalviolations.Basically,a firewall consists of hardware and software components which areindividually configured according to the requirements of the servicesavailable for the internalusersandthe safety tobeguaranteed. Thisenablesthe firewall topreventnon-authenticatedaccesses to the local networkandthe controlled access to the distributed data bases and network resourceswith a simultaneous logging of the access activities.
Firewallscanalsobereasonablewithinonecompany,e.g. fordecouplingtheproduction area of the office Ethernet.
Remote maintenance scenariosTechnical scenariosConnection via the Internet
44.24.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 telegramswith which targetmay pass. It uses the following mechanisms:
ƒ Authentication
ƒ Package filtering: Decision on the basis of the data contents of thepackages
ƒ 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 maximumsafety. Therefore, it is recommended to use an adaptive network safetystrategy which is adjusted to the individual safety requirements of therespective company.
Tip!A PC can also be a firewall. A PC which undertakes this taskshould then, however, not perform other tasks. It isrecommendable to use enclosed devices.
Remote maintenance scenariosTechnical scenarios
Connection via the Internet
44.2
4.2.4
4.2-25EDSFEW EN 04/2005
4.2.4.5 Architecture example
Basically,there are two different scenarios:
1. Remote maintenance from a standalone computer to a companynetwork
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 withoutVPN
2180FEW117
Fig. 4.2-1 Remote maintenance from a standalone computer to a company network
The PC from which the remote maintenance is to be operated, has anInternet access via DSL, ISDN or other modems. It is recommendable tooperate a VPN on this PC to secure the connection between PC and Internetserviceprovider (ISP).Onthecompanyside,aVPNgatewayisrequiredforthedevices to be remote-maintained. The VPN gateway can both be a separatedevice and a combination of VPN, firewall and router.
Remotemaintenance from astandalone computer to acompany network
Remote maintenance scenariosTechnical scenariosConnection via the Internet
44.24.2.4
4.2-26 EDSFEW EN 04/2005
Site A
InternetEncrypted
Ethernet
Gateway with VPN
Site B
Ethernet
Gateway with VPN2180FEW118
Fig. 4.2-2 Remote maintenance from one 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 maintenancepurposes, has no access to its local network during the maintenance. Thisensures that it cannot be misused as a tunnel into the entire companynetwork. Often the service PCs are separated from the other companynetwork by firewalls. Within the companies, firewalls can e. g. be used forseparating the office andmachine network. The entire scenario depends onthe respective application.
EthernetInternet access
Router
Ethernet
Ethernet
2180FEW119
Remotemaintenance fromone company network toanother
EDSFEW!!!!
Ä!!!!ä
Communication Manual
ModemCAN
EMF2181IB
Communication module
2181 communication module (ModemCAN)Contents
6
6-1EDSFEW 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2181 communication module (ModemCAN)Before you start
Your opinion is important to us
66.1
6.1.1
6.1-1EDSFEW EN 04/2005
6.1 Before you start
Tip!Current documentation and software updates for Lenze productscan be found on the Internet in the ”Downloads” area underhttp://www.Lenze.com
6.1.1 Your opinion is important to us
These Instructions were created to the best of our knowledge and belief togive you the best possible support for handling our product.
If you have suggestions for improvement, please e-mail us to:
Thank you for your support.
Your Lenze documentation team
6.1.2 What is new / what has changed in these Instructions?
Edition date Revised chapters Notes
04 / 2005 - First edition
2181 communication module (ModemCAN)General information
66.2
6.2-1EDSFEW 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 Instructionsfor 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 andstandards.
If the internal modem cannot be used, it is possible to connect an externalmodem using the RS232 interface.
The communication module is used for setting parameters during remotemaintenance or programming and commissioning the usable Lenzedevices.
Validity
Identification
Application range
Features
2181 communication module (ModemCAN)Technical data
General data and operating conditions
66.3
6.3.1
6.3-1EDSFEW EN 04/2005
6.3 Technical data
6.3.1 General data and operating conditions
Range Values
Order designation EMF2181IB
Communication media(system)
CAN (DIN ISO 11898)Lenze diagnostic interface
Communication media(external)
Telephone, analogue, 33.6 kbits/s, (V34)
Number of nodes at the CANbus
Max. 100
Baud rate For communication via the CAN bus– 20 kbits/s– 50 kbits/s– 125 kbits/s– 250 kbits/s– 500 kbits/s– 1000 kbits/sFor communication via diagnostic interface– 230.4 kbit/s
Voltage supply (external) viaseparate power supply
18 - 30 V DC, max. 100mA (in accordance with EN 61131-2)
6.3.2 Climatic conditions
Reference Values
Type of protection IP20
Ambient temperature during operation: 0°C ... +60 °Cp
during transport: - 10°C ... +70 °C
during storage - 10°C ... +60 °C
Climatic conditions Class 3K3 to EN 50178 (without condensation, average relativehumidity 85 %)
Pollution degree EN 50178, pollution degree 2
2181 communication module (ModemCAN)Technical dataRated data
66.36.3.3
6.3-2 EDSFEW EN 04/2005
6.3.3 Rated data
2181FEW001F
Connection Type of insulation (to EN 61800-5-1)
Telephone Functional insulation
Diagnostic interface Functional insulation
CAN bus Functional insulation
Voltage supply No insulation
External modem No insulation
2181 communication module (ModemCAN)Technical data
Dimensions
66.3
6.3.4
6.3-3EDSFEW EN 04/2005
6.3.4 Dimensions
2181FEW001B
a 117mm
b 103mm
b1 99mm
e 22.5 mm
2181 communication module (ModemCAN)Installation
Elements of the communication module
66.4
6.4.1
6.4-1EDSFEW EN 04/2005
6.4 Installation
6.4.1 Elements of the communication module
2181FEW001D
Fig. 6.4-1 Communication module ModemCAN 2181
Pos. Name Description
Telephone connection Socket (RJ11)
Connection at diagnostic interfaceof the 9400 drive controller(in preparation)
Socket (RJ69)
CAN connection Socket (RS232, male)
Connection for voltage supply Terminal strip with spring connection, 4-pole
External modem connection Socket (RS232, male)
PE connection The plugged communication module isautomatically connected to the DIN rail.The DIN rail must be connected with PE!
Pos. Colour State Description
( )YELLOW On TheModemCAN is ready
(M) Blinking Active communication over the telephone,the ModemCAN has ”answered”.
(E)RED See 6.5-7 ERR LED
(R)GREEN RUN LED or diagnostic interface active
(P)GREEN On TheModemCAN is supplied with voltage.
Note!Refer to the instructions on the signals provided by the ERRORLED and RUN LED in the Troubleshooting chapter ( 6.8-1).
Connections
Displays
2181 communication module (ModemCAN)InstallationMechanical installation
66.46.4.2
6.4-2 EDSFEW EN 04/2005
6.4.2 Mechanical installation
2181FEW002B
Fig. 6.4-2 Snap communication module to DIN rail
2181FEW001E
Fig. 6.4-3 Unlock communication module and lift off DIN rail .
Mounting
Dismounting
2181 communication module (ModemCAN)Installation
Electrical installation
66.4
6.4.3
6.4-3EDSFEW EN 04/2005
6.4.3 Electrical installation
6.4.3.1 Communication via CAN
2181FEW008
Fig. 6.4-4 Communication via the CAN bus
Step Activity Connection(see graphic)
Additionalinformation
1. Connect voltage supply to the plug connector 6.4-5
2. Insert SUB-D plug (”EWZ0046”, see Accessories) inModemCAN
6.4-6
3. If it is not possible to use the internal modem:Connect external modem
6.4-8
4. Connect drive controller to CAN bus -
5. Connect ModemCAN 2181 to telephone network 6.4-9
Installation steps
2181 communication module (ModemCAN)InstallationElectrical installation
66.46.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)
Additionalinformation
1. Connect voltage supply to the plug connector 6.4-5
2. Connect diagnostic interface to drive controller 9400(use prefabricated cable)
6.4-10
3. If it is not possible to use the internal modem:Connect external modem
6.4-8
4. Connect drive controller to CAN bus -
5. Connect ModemCAN 2181 to telephone network 6.4-9
Communicating via the diagnostic interface is especially recommended ifthe 2181 communication module is only connected temporarily.
In case of a fixed installation the communication via CAN should bepreferred, see ( 6.4-3).
Installation steps
2181 communication module (ModemCAN)Installation
Electrical installation
66.4
6.4.3
6.4-5EDSFEW EN 04/2005
6.4.3.3 Voltage supply
2181FEW001G
Terminal data
Electrical connection Plug connector with spring connection
Possible connections rigid: 2.5 mm2 (AWG 12)
flexible:
without wire end ferrule2.5 mm2 (AWG 12)with wire end ferrule, without plastic sleeve2.5 mm2 (AWG 12)with wire end ferrule, with plastic sleeve2.5 mm2 (AWG 12)
Bare end 10mm
Stop!In order to avoid damages to the pluggable terminal strips andthe contacts:ƒ The terminal strips must be wired before plugging them in!ƒ Pluggable terminals strips that are not assigned must beplugged on as well.
E82ZAFX013
Terminal data
Handling of pluggableterminal strips
Use of pluggable terminalstrip with spring connection
2181 communication module (ModemCAN)InstallationElectrical installation
66.46.4.3
6.4-6 EDSFEW EN 04/2005
6.4.3.4 CAN bus connection
2181FEW001K
16
59
Pin Plug assignment
16
59 1, 4, 5, 6, 8, 9 Not assigned
16
59
2 CAN-LO
16
59
3 CAN-GND16
59
7 CAN-HI
TheCANbusmustbeterminatedbyresistors(120 Ω)betweenCAN-LOWandCAN-HIGH). The Sub-D plug with integrated terminating resistor (order no.EWZ0046, not included in the scope of supply) corresponds to therecommendation DS 102-1 of CiA.
L
EW
Z0046
OFF
ON
OFF
ON
ON
OFF
OUTIN IN IN
On Off On120 120 120
LE
WZ
0046
LE
WZ
0046
LE
WZ
0046
2181FEW004
Please observe our recommendations for signal cables:
Specification for the transmission cable
Total length ≤ 300m ≤ 1000m
Cable type LIYCY 2 x 2 x 0.5 mm2
(twisted in pairs with shield)CYPIMF 2 x 2 x 0.5 mm2
(twisted in pairs with shield)
Cable resistance ≤ 80 Ω/km ≤ 80 Ω/km
Capacitance per unitlength
≤ 130 nF/km ≤ 60 nF/km
Assignment of the Sub-D plug
Specification of thetransmission cable
2181 communication module (ModemCAN)Installation
Electrical installation
66.4
6.4.3
6.4-7EDSFEW 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 andthe number of participants. Without any repeaters, the segment cablelength corresponds to the total cable length.
Cable cross-section
Participant 0.25 mm2 0.5 mm2 0.75 mm2 1.0 mm2
2 240m 430m 650m 940m
5 230m 420m 640m 920m
10 230m 410m 620m 900m
20 210m 390m 580m 850m
32 200m 360m 550m 800m
63 170m 310m 470m 690m
100 150m 270m 410m 600m
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 given inTab. 6.4-1, repeatersmustbeapplied.Repeatersdividethetotal cable lengthinto segments.
Note!You will find more information on the structure of a CANnetwork in the CAN communication manual.
Bus cable length
2181 communication module (ModemCAN)InstallationElectrical installation
66.46.4.3
6.4-8 EDSFEW EN 04/2005
6.4.3.5 External modem connection
16
59
Name
16
59
Pin V.24 RS232 Signal Signal name Direction
16
59
1 109 CF DCD Data Carrier Detector Output
16
59 2 104 BB RD Received Data Output
16
59
3 103 BA TD Transmitted Data Input
16
59
4 108/2 CD DTR Data Terminal Ready Input
16
59
5 102 AB SG Signal Ground -
16
59
6 107 CC DSR Data Set Ready Output16
59
7 105 CA RTS Request To Send Input16
59
8 106 CB CTS Clear To Send Output
16
59
9 125 CE - Ring Indicator Output
Assignment for the RS232interface
2181 communication module (ModemCAN)Installation
Electrical installation
66.4
6.4.3
6.4-9EDSFEW 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
2181 communication module (ModemCAN)InstallationElectrical installation
66.46.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 diagnosticconnector
2181 communication module (ModemCAN)Commissioning
Before switching on
66.5
6.5.1
6.5-1EDSFEW EN 04/2005
6.5 Commissioning
6.5.1 Before switching on
Stop!Prior to switching on the mains voltage, check the wiring forcompleteness, 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 toincorrectly 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” ( 6.7-3)
ƒ C0351: ”Set baud rate” ( 6.7-4)
Before the 2181 communication module is connected with the telephonenetwork, the country-specific code must be configured, if required.
Note!The description of code C1208 must be observed ( 6.7-16).
Automatic addressassignment and automaticdetection of the baud rate
Configuration ofcountry-specific code
2181 communication module (ModemCAN)CommissioningCommissioning with the system bus configurator
66.56.5.2
6.5-2 EDSFEW EN 04/2005
6.5.2 Commissioning with the system bus configurator
Note!A window-compatible modemmust be installed in the windowssystem 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 bemet to work with the communication module:
ƒ MicrosoftRWindowsR 2000/XP
ƒ IBMR-compatible PC with IntelRPentiumR-266 processor or higher
ƒ 128 MBmain memory with Windows 2000/XP
The following Lenze programs allow for a communication via thecommunication 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 alternativecommunication paths for CAN. In this case, please always selectthe communication path ”OPC”.
System requirements
Available Lenze programs
2181 communication module (ModemCAN)Commissioning
Commissioning with the system bus configurator
66.5
6.5.2
6.5-3EDSFEW EN 04/2005
Note!The driver installation under Windows 2000/XP requiresadministrator rights!
In order to introduce the 2180 communication module to the operatingsystem, it is necessary to install a driver.
The driver is both included in each of the Lenze programsmentionedbeforeand in the system bus configurator as of version 1.2. It is automaticallyloaded during the installation or can be selected manually during theinstallation.
Note!ƒ The driver must always be installed separately if you use thefollowing 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 ”Updatesystem bus configurator Vxx” (xx: version number) in thedownload area of the Lenze homepagehttp://www.Lenze.com
ƒ For this purpose proceed the following steps:– Save the driver of the Lenze homepage to your local harddisk.
– Install the Lenze programs that will communicate via the2180 communication module.
– Install the driver by following the instructions of theinstallation program.
The Lenze system bus configurator for the convenient configuration of theutilised system bus adapters is installed together with the driver for the2180 communicationmodule so that no additional installation is required.
Installing the required driver
Installation of the system busconfigurator
2181 communication module (ModemCAN)CommissioningCommissioning with the system bus configurator
66.56.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, itmust be configured accordingly.
To open the systembus configurator, select the following in the startmenu
Programs Lenze Communication System bus configurator.
In contrast to the other communicationmodules the individual parametersare not included in the index card ”Settings”. Instead, an entry can bemadein the telephone book for each system to be remote-maintained. Thestandard parameters as baud rate, parameter channel, and time-out can befound there as well.
1. Select the communication module from the list in the system busconfigurator.
2. Double-click the corresponding line.
3. If you start the telephone book for the first time, some configurationsand 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 pauseduring dial-up. The corresponding settings are included in thedocumentations of the private branch exchange and PC modem.
8. Select the modem to be used.
9. Close the setting dialogue.
Steps to be taken forconfiguring thecommunication module
2181 communication module (ModemCAN)Commissioning
Commissioning with the system bus configurator
66.5
6.5.2
6.5-5EDSFEW EN 04/2005
Now, the first dial-up of the communicationmodule can bemade from thetelephone book.
1. For this purpose, press the button ”Connect”. Check the indicatedvalues 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 parametersconfigured on the PC are identical with those in the device. If not, anadjustment will be executed.
4. After this, a small status window appears which displays theconnection status and the connection time. Via this window theconnection 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 searchedfor nodes connected.
6. Confirm the safety instruction with ”Yes” or select ”No” to abort thediagnostics.
When the communication module succeeded in communicating with thecorresponding bus nodes, the system bus node addresses of the bus nodesfound are listed in the field ”Device status”.
If the communication module is not able to communicate with the busnodes, an error message is displayed.
The communicationmodule answers with its CAN address or with ”0” if noaddress exists (dependent on C00350). The data telegrams forcommunicating with the communication module itself, however, are notvisible on the CAN bus.
Note!Additional information about the configuration of thecommunication module can be found in the online help of thesystem bus configurator.
If the configuration of a communication module is successful, the Lenzetools can use it for communication.
Only the selection of the bus systemused is performed in the Lenze tools, allsystem bus-specific settings and the selection of the communicationmodule are carried out exclusively via system bus configurator.
Note!While some of the older program versions of the Lenze tools stilloffer setting options for interrupt and I/O address, they aremeaningless in the context of the communication module.
After completing theconfiguration
2181 communication module (ModemCAN)CommissioningFirst switch-on
66.56.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
Pos. Colour State Description
( )YELLOW On TheModemCAN is ready
(M) Blinking Active communication over the telephone,the ModemCAN has ”answered”.
(E)RED See 6.5-7 ERR LED
(R)GREEN RUN LED or diagnostic interface active
(P)GREEN On TheModemCAN is supplied with voltage.
Signalling
2181 communication module (ModemCAN)CommissioningFirst switch-on
66.5
6.5.3
6.5-7EDSFEW 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 activeQ ( )
GREEN BLINKING every 0.2 seconds Z: Pre-Operational, F: None
GREEN BLINKING every 0.2 seconds1 x RED BLINKING 1 s OFF
Z: Pre-Operational, F: Warning Limit reached1 x RED BLINKING, 1 s OFF
GREEN BLINKING every 0.2 seconds2 x RED BLINKING 1 s OFF
Z: Pre-Operational, F: Node Guard Event2 x RED BLINKING, 1 s OFF
Constant GREEN lighting Z: Operational, F: None
Constant GREEN lighting1 x RED BLINKING 1 s OFF
Z: Operational, fault: Warning Limit reached1 x RED BLINKING, 1 s OFF
Constant GREEN lighting2 x RED BLINKING 1 s OFF
Z: Operational, F: Node Guard Event2 x RED BLINKING, 1 s OFF
Constant GREEN lighting3 x RED BLINKING 1 s OFF
Z: Operational, F: Sync Message Error3 x RED BLINKING, 1 s OFF
GREEN BLINKING every second Z: Stopped, F: None
GREEN BLINKING every second1 x RED BLINKING 1 s OFF
Z: Stopped, F: Warning Limit reached1 x RED BLINKING, 1 s OFF
GREEN BLINKING every second2 x RED BLINKING 1 s OFF
Z: Stopped, F: Node Guard Event2 x RED BLINKING, 1 s OFF
Tab. 6.5-1 Signalling acc. to DR303-3
Signalling acc. to DR303-3
2181 communication module (ModemCAN)CommissioningFirst switch-on
66.56.5.3
6.5-8 EDSFEW EN 04/2005
1. The LED is lit. The communication module performs some internalinitialisations.
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 is lit.
The device is now ready and can receive calls.
Signalling sequence afterswitch on
2181 communication module (ModemCAN)Data transfer
Data transfer via CAN
66.6
6.6.1
6.6-1EDSFEW EN 04/2005
6.6 Data transfer
6.6.1 Data transfer via CAN
2181FEW008
Master and drive controller communicate with each other by exchangingdatamessages via the CANbus. The data area in the datamessage containseither network management data, parameter data or process data.
In the drive controller, different communication channels are allocated tothe parameter data and process data.
The communication module ModemCAN 2181 is suitable (apart from thetransferof IEC61131programsandapplicationdata, e.g. curvedata) only forthe transfer of parameter data.
Parameter data
These are e. g.Operating parametersDiagnostics informationMotor 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 (noteC0003).
The structure of the CANmessages is described in the CAN communicationmanual.
2181 communication module (ModemCAN)Data transferData transfer via CAN
66.66.6.1
6.6-2 EDSFEW EN 04/2005
Note!For the value range of the Lenze code, please refer to theoperating instructions for the drive controller (see ’Code list’).
When communicationmodules are used, the properties and the behaviourof a drive controller integrated into the network can be changedby a higherlevel master (e. g. a PLC).
The parameters to be changed are contained in the codes of Lenze drivecontrollers.
The drive controller codes are addressed using the index on access via thecommunication module .
The index for theLenzecodenumber is inthe rangebetween16576(40C0hex)and 24575 (5FFFhex).
Conversion formula:Index [dec] = 24575 - Lenze code number
dec hex
Index = 24575 - Lenze code Indexhex = 5FFFhex - (Lenze code)hexIndex = 24575 - 1 = 24574 Indexhex = 5FFFhex - 1 = 5FFEhex
The communication module has two parameter data channels which areboth activated in the Lenze setting.
Note!In order to establish the compatibility with CANopen, the secondparameter data channel must be switched off via code C1200,see ( 6.7-8).
Access to the drive controllercodes
Indexing of codes using theexampleC0001 (operating mode)
CANopen parameter channels
2181 communication module (ModemCAN)Data transfer
Data transfer via the diagnostics interface
66.6
6.6.2
6.6-3EDSFEW 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 ahot-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 alsopossible toaccess,viathediagnostic interface, lower leveldevicesconnectedtogether on a different bus.
2181 communication module (ModemCAN)Data transferData transfer via modem
66.66.6.3
6.6-4 EDSFEW EN 04/2005
6.6.3 Data transfer via modem
2181FEW005
Data transfer by modem is performed using the PPP protocol that providessecure data transmission.
The system bus configurator serves to automatically establish theautomatic dial-up connection on the PC side (see arrow).
Thebaudrateonthe telephone line isadjustedbybothmodems.Dependingon the quality of the connection, it is reduced automatically, if required,based on 33.6 kbits/s.
2181 communication module (ModemCAN)Lenze codes and CANopen objects
66.7
6.7-1EDSFEW EN 04/2005
6.7 Lenze codes and CANopen objects
The behaviour of the communication module is defined by settingparameters for (Lenze) codes. These codes are exchanged as part of amessage via the CAN bus.
In the following table you will find an overview of codes relevant for thecommunicationmodule and the CANobjects implemented. Please note thereferences to additional information.
Note!Convention for differentiating between the implementedCANopen indices and Lenze codes:ƒ CANopen index: I- + (index)ƒ Lenze code: C + (code number)
Column Content Meaning
Code C0353 Code C0353
Subcode 12
Subcode 1 for the codeSubcode 2 for the code
Index 5E9E Necessary for addressing the code in bus messages.Information as hexadecimal number.Conversion:24575 - Lenze code (C0353) = 24222dec = 5E9Ehex
Lenze Factory setting for the code (termed ”Lenze setting” in thefollowing)
Selection 1 1 % 99
1, 2, 3, 5
For a range:Minimum value smallest increment/unit maximum value
For fixed valueDisplay code (no configuration possible)
Important - Additional, important information on the code (boldprint: code designation in GDC)
How to read the tables forLenze codes
2181 communication module (ModemCAN)Lenze codes and CANopen objects
66.7
6.7-2 EDSFEW EN 04/2005
Code Subcode Index[hex]
NameSee
C0002 - 5FFD Load parameter set 6.7-13
C0099 - 5F9C Display of the software version 6.7-13
C0150 - 5F69 Status word 6.7-13
C0200 - 5F37 Software manufacturer’s product code 6.7-3
C0350 5EA1 CAN node address 6.7-3
C0351 - 5EA0 CAN baud rate 6.7-4
C0358 - 5E99 Reset node 6.7-4
C0359 5E98 CAN status 6.7-5
C0360 12
5E97 CAN telegram counter 6.7-7
C0361 12
5E96 CAN bus load 6.7-7
C1200 5B4F Parameter data channel operatingmode
6.7-8
C1201 5B4E Communication time-out (CAN) 6.7-8
C1202 5B4D Time limit for node search 6.7-8
C1203 5B4C Repeat tests 6.7-9
C1204 5B4B Password protection 6.7-14
C1205 5B4A Call-back telephone number 6.7-14
C1206 5B49 Modem initialisation command 6.7-15
C1207 5B48 Switch over internal/external modem 6.7-15
C1208 5B47 Country code 6.7-16
C1209 5B46 Detection of the baud rate 6.7-9
C1213 5B42 Connection via CAN or diagnosticinterface
6.7-13
C1215 5B40 Time exceeded during automatic baudrate detection
6.7-9
C1223 5B38 User name 6.7-16
C1225 5B36 Baud rate of the external modem 6.7-16
C1226 5B35 Modem reset 6.7-17
C1227 5B34 Delay time for search telegrams 6.7-10
Index [hex] Subindex Name See
I-1000 0 Device type 6.7-11
I-1001 0 Error register 6.7-11
I-1017 - Producer heartbeat time 6.7-11
I-1018 0...4 Identity object 6.7-12
Lenze codes
CANopen objectsimplemented
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
66.7
6.7.1
6.7-3EDSFEW 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 manufacturer’s productcodeData format: VSAccess: R
During initialisation of the module it is determined which device isconnected as a user based on the manufacturer’s product code.
Value displayed for the ModemCAN: 33S2181F_10000.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0350 5EA1 63 0 1 63(127)
CAN node addressData format: I32Access: R/WMax. address for communicationvia
Lenze system bus : 63CANopen: 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 adedicated node address. It can then not be addressed from the CAN bus (noparameter setting, node guarding etc.), but only serves as a dialling-infeature for reading parameters via the CAN bus.
If the communicationmodule shouldhave anaddress, check, after thebaudrate has been detected, whether this address is still free. Then, theimplemented CANopen object 1000 is tried to be read. If another nodealready has this address, another free address is selected automatically.
Note!Node addresses in the range of 64 ... 127 can only be assigned ifthe 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
C0200:Software manufacturer’sproduct code
C0350:General address assignment
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
66.76.7.1
6.7-4 EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0351 - 5EA0 0 01234516
500 kbits/s250 kbits/s125 kbits/s50 kbits/s1000 kbits/s20 kbits/sautom.detection
CAN baud rateData format: I32Access: R/W
The baud rate over the CAN bus can be set using this code.
Changes to the setting are applied after:
ƒ Reconnection to the mains
ƒ 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 thecommunication module and compared with the baud rate configured.
If the two values are different, the baud rate determined is used. The baudrate detected by the communicationmodule can be readusing code C1209.
If there is no data traffic on the CAN bus, the baud rate cannot bedetermined. The subsequent behaviour of the communication moduledepends on the selection configured in code C0351:
ƒ Selection 0 ... 5After a time-out that can be configured using code C1215, the CAN busis 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 ratecan be detected.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0358 - 5E99 0 0
1
No functionCAN reset
Reset nodeCAN bus reset - set up nodal pointData format: I32Access: R/W
After a reset any changes to communication parameters such as baud rateor node address are applied.
Entries with new baud rates or changes to the node address only becomevalid after a node reset.
A node reset can be performed by:
ƒ Reconnection to the mains
ƒ Reset node via the bus system
ƒ Reset node using code C0358
C0351:Set transfer rate
C0358:Reset node
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
66.7
6.7.1
6.7-5EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0359 5E98 01
234
OperationalPre-OperationalWarningBus OffStopped
CAN statusStatus displayData format: I32Access: R
This code displays the current operating status of the CAN controller. Herea 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 withthe following actions:
– A drive is defined as the master using code C0352. When connectingto the mains an automatic state change for the entire drive system isperformed 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. usingthe code C0364 via a terminal given an appropriate configuration(prerequisite: C0352 = 1).
– A network management message from a CANmaster.
ƒ Selection 2: Warning
Error messages have been received if the state is ”Warning”. The CAN nodeis 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 controlelectronics
– An excessively high bus load
– CAN node is not connected to the bus
C0359:CAN status
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
66.76.7.1
6.7-6 EDSFEW EN 04/2005
ƒ Selection 3: Bus Off
The frequency of the erroneous messages has resulted in the CAN nodedecoupling itself from the bus. It is possible to switch to the”Pre-Operational” state with:
– A trip reset
– A reset node
– Reconnection to the mains
ƒ Selection 4: Stopped
Only NMT telegrams can be received.
The state can be changed to ”Pre-Operational” by:
– Reconnection to the mains
– Reset node via the bus system
– Reset node via the code C0358
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
66.7
6.7.1
6.7-7EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0360 12
5E97 0 .... 4294967295 CANTelegram counter (number of alltelegrams that are determined forthis node)
Counter value > 4294967295:Start again at 0/1: all messages sent/2: all messages receivedData format: I32Access: R
All CAN telegrams transmitted and received of this node are counted.
The counters have32bits, i. e.whenavalueof 4294967295 is exceeded, thecounting process starts again at 0.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0361 5E96 0 .... 100% CANBus loadData format: I32Access: R
Using this code the percentage total bus load canbe determined. Erroneousmessages 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 areconnected, these messages are also to be taken into account.
C0360:Telegram counter
C0361:Bus load diagnostics
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
66.76.7.1
6.7-8 EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1200 5B4F 2 0, 1 or 2 Operating mode - parameter datachannelData format: I32Access: R/W
This code indicates which of the two parameter data channels is used tocommunicate with other nodes. The unused parameter data channels canbe switched off, if required.
All Lenze controllers have two parameter data channels with differentaddressing. Theaddress of theparameter channel 2 is 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 SDO 1
1 1...63 SDO1 / SDO2
2 65...127 SDO1 / SDO2
Note!The selection 0 means that the bus is operating in compliancewith CANopen and there is no limitation on the address space.In this case, the parameter data channel SDO2 is inactive.
zl
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1201 5B4E 1500 0 1ms 10000 Data format: I32
The time set defines the time framewithinwhichaCANnodemust respondto a request.
If there is no response of the node, the requestingmodule assumes that thenode is not available.zl
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1202 5B4D 1000 0 1ms 10000 Data format: I32
For node search, the time set is regularly maintained. It must be selectedhigh 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 delaytime for search telegrams increased with code C1227.
C1200:Parameter data channeloperating mode
C1201:Communication time-out(CAN)
C1202:Time limit for node search
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the codes relevant for CAN
66.7
6.7.1
6.7-9EDSFEW EN 04/2005
zl
Code Subcode Index[ ]
Possible settings Important[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 ofthose CAN telegrams which have not reached the receiver.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1209 5B46 0123
500 kbits/s250 kbits/s125 kbits/s50 kbits/s
Detection of the baud rateData format: I32Access: R
3416
50 kbits/s1000 kbits/snothingdetected
Code C1209 can be used to determine which transfer rate was detected onthe CAN bus.
When ”16” is indicated, there is no data traffic on the CAN bus.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1215 5B40 1000 0 1ms 60000 Time exceeded during automaticbaud rate detectionData format: I32Access: R/W
By defining a time-out in code C1215, the baud rate (display with codeC1209) on the CAN bus can be detected.
The baud rate is not checked if the value configured in code C1215 is set tozero.
When the time-out configured in code C1215 elapses, the CAN bus isaccessed (for further information and limitations: see description of codeC0351).
C1203:Repeat tests
C1209:Read bus baud rate
C1215:Time-out (automatic baudrate detection)
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the codes relevant for CAN
66.76.7.1
6.7-10 EDSFEW EN 04/2005
zl
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1227 - 5B34 0 0 1ms 100 Dataformat:I32
Selection Meaning
0 Quickest possible search
1...10 Delay time 1ms
11...19 Delay time 10ms
20...29 Delay time 20ms
... ...
... ...
90...100 Delay time 90ms
Searching the CAN bus during the start of a PC program can lead to faults ifa bus is heavily loaded. In order to prevent this, a delay time between thetransmission telegramscanbe set. This, however, leads to an increase of thetotal search time. If required, C1202 must be adapted accordingly.
C1227:Delay time for searchtelegrams
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the CANopen objects implemented
66.7
6.7.2
6.7-11EDSFEW EN 04/2005
6.7.2 Description of the CANopen objects implemented
TheCANopen index I-1000hexgives thedeviceprofile for thisdevice. It isalsopossible to include additional information here that is defined in the deviceprofile itself. If no specific device profile is used, the content is 0000hex .
Index [hex] Subindex Name Data type Value range Rights
I-1000 0 Device type U32 0 ... (232 - 1) ro
Bit assignment in the telegram data
5th byte 6th byte 7th byte 8th byte
LSBDevice profile number
MSBAdditional information
Reading the error register
Index [hex] Subindex Name Data type Value range Rights
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 thecommunication module
0 0 0 1 0 0 0 1 Communication error
Index [hex] Subindex Name Data type Value range Rights
I-1017 - Producer heartbeattime
U32 U 16 rw
The heartbeat message is sent cyclically by the heartbeat generator(producer) to one or more recipients (consumers).
After configuring theheartbeatproducer time, theheartbeatprotocolstartsat the transition from the NMT state INITIALISATION to the NMT statePREOPERATIONAL (if predefined value > 0).
Note!Unlike ”node / life guarding” monitoring, the heartbeat protocoldoes not contain a “Remote Transmit Request” (RTR).It is therefore not necessary for the recipient to answer after aheartbeat.
I-1000hex:Device type
I-1001hex:Error register
I-1017hex:Producer heartbeat time
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the CANopen objects implemented
66.76.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 thisobject:
Subindex Meaning
0 Highest subindex
1 Vendor ID
2 Product code
3 Revision number
4 Serial number
I-1018hex:Identity object
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the general codes
66.7
6.7.3
6.7-13EDSFEW EN 04/2005
6.7.3 Description of the general codes
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0002 5FFD 0 0: Implemented1: Load factorycalibration
Parameter set managementData format: I32Access: R
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0099 5F9C Display: x.y Software versionData format: FIX32Access: R
The display designates
ƒ x: main version
ƒ y: index
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C0150 5F69 Status wordData format: B16Access: R
The binary interpretation of the displayed decimal value reflects the bitstatuses of the status word:
ƒ Bit 0: Ready for operation
ƒ Bit 1: Dial-up connection is available
ƒ Bit 2: Internal error
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1213 5B42 0 01
CANDiagnosticsinterface
Connection via CAN or diagnosticsinterfaceData format: FIX32Access: R/W
The fieldbus connection is to be entered in code C1213:
C 1213 = 0Connection of ModemCAN 2181 and drive controller via the CAN bus.
C1213 = 1ConnectionoftheModemCAN2181tothediagnostics interfaceonthedrivecontroller 9400.
Note!It is not possible to operate both connections on thecommunication module in parallel.
C0002:Parameter set management
C0099:Software version
C0150:Status word
C1213:Fieldbus connection
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the codes relevant for the modem
66.76.7.4
6.7-14 EDSFEW EN 04/2005
6.7.4 Description of the codes relevant for the modem
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1204 5B4B - Blank: no passwordprotection
Password protectionData format: VSAccess: W
CodeC1204serves toprotect thecommunicationmoduleModemCAN2181against unauthorised access by assigning a password.
Duringdial-up, thepasswordsaved in thePC is comparedwith thepasswordsaved in the communication module:
ƒ Dialling in is continued if both passwords are identical.
ƒ The dial-up will be interrupted immediately or after a short waitingtime when the passwords or user names are not identical (see codeC1223).
Note!ƒ In code C1204 it is possible to enter a new password via theCAN bus at any time or to enter no password by leaving theselection field blank.
ƒ The password is not reset when loading the Lenze setting.
Note!This function is temporarily not available.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1205 5B4A - Data format: VSAccess: 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 no telephonenumberentered inC1205, nocall-back isperformed,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 renewedmainsswitching or modem reset (code C1226).
C1204:Password
C1205:Call-back telephone number
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the codes relevant for the modem
66.7
6.7.4
6.7-15EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze
C1206 5B49 AT&FE1QØ&K3&D2&C1 Data format: VSAccess: R/W
Note!The Lenze setting is sufficient to initialise the modem.If, however, no connection could be established, it is possible toadapt the initialisation command via suitable AT commands.Only change the value of this code if it is really required!A wrong initialisation commandmay make the dial-upimpossible. In this case, the Lenze setting of the modemmust beloaded and the AT commands entered before must be corrected.
Code C1206 provides the internal or external modemwith an initialisationcommand consisting of several AT commands.
Note!Changes of this code will only be effective by renewedmainsswitching or modem reset (code C1226).
Tip!The annex of this manual provides a part of the entirecommands for the communication module ModemCAN 2181.
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1207 5B48 0 0 InternalModem
Switch over internal/externalmodem
f1 Externalmodem
Data format: FIX32Access: R/W
It is possible to switch between an internal and externalmodemusing codeC1207.
This code can only be written via CAN.
Note!Changes of this code will only be effective by renewedmainsswitching or modem reset (code C1226).
C1206:Modem initialisation
C1207:Switch over internal /external modem
2181 communication module (ModemCAN)Lenze codes and CANopen objectsDescription of the codes relevant for the modem
66.76.7.4
6.7-16 EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1208 5B47 253 See6.9-2
Data format: FIX32Access: R/W
Using the code C1208, the code for the country inwhich themodem is usedcan be entered.
The internalmodem is approved for use inmany countries. However, as therequired features vary slightly, the modem must configure itself to therelatedconditions.Forthispurposeit isnecessarytoenter thecorrespondingcountry code. Within Europe the country code is the same.
Note!Changes of this code will only be effective by renewedmainsswitching or modem reset (code C1226).
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
C1223 5B38 Lenze User nameData format: VSAccess: R/W
Code C1223 serves to enter a user name. The code is pre-assigned with theuser name ”Lenze” by the Lenze setting.
Note!The user name is not reset when loading the Lenze setting.
Code Subcode Index[ ]
Possible settings Important[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 modulecommunicateswith externalmodems. Mostmodems are providedwith anautomatic baud rate recognition so that this parameter does not need to bechanged. Here, only in exceptional cases must the baud rate be set, whichtheexternalmodemhasasstandard. If the initialisationwith theconfiguredbaud rate fails, a new one is automatically tried to be used.
Note!Changes of this code will only be effective by renewedmainsswitching or modem reset (code C1226).
C1208:Country code
C1223:User name
C1225:Baud rate of the externalmodem
2181 communication module (ModemCAN)Lenze codes and CANopen objects
Description of the codes relevant for the modem
66.7
6.7.4
6.7-17EDSFEW EN 04/2005
Code Subcode Index[ ]
Possible settings Important[hex] Lenze Selection
p
C1226 5B35 0 0: No function1: Modem reset
Data format: I32Access: R/W
A changeof themodemparameterswill onlybe effectiveby renewedmainsswitching or using the code C1226.
C1226:Modem reset
2181 communication module (ModemCAN)Troubleshooting
Signalling of the CANopen RUN LED and ERROR LED
66.8
6.8.1
6.8-1EDSFEW 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
CAN bus 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 andshows errors on the basis of missing CAN messages (SYNC, GUARD orHEARTBEAT). It is lit red.
No. ERROR LED STATUS Description
1 OFF No error The device is ready for operation.
2 Individuallighting up
Warning limit isreached
At least one of the error counters of the CANcontroller has reached or exceeded the warninglevel (too many error frames).
3 Flicker AutoBaud/LSS The automatic baud rate detection or LSS servicesare running. (ERROR LED and RUN LED flickeralternately).
4 Doublelighting up
Error controlevent
A guard event (NMT slave or NMTmaster) orheartbeat event (heartbeat consumer) hasoccurred.
5 Triple lightingup
Sync error The sync message has not been received withinthe time configured for the timemonitoring ofthe communication cycle..
6 On Bus Off The CAN controller is in the bus-off state.
The CANopen RUN LED displays the CANopen-NMT status. It is lit up green.
No. CAN RUN LED STATUS Description
1 Flicker AutoBaud/LSS The automatic baud rate detection or LSS servicesare running. (ERROR LED and RUN LED flickeralternately). Optional
2 Singlelighting up
STOPPED The device in the STOPPED state.
3 Blinking PRE-OPERATIONAL
The device is in the PREOPERATIONAL state.
4 On OPERATIONAL The device is in the OPERATIONAL state.
CANopen ERROR LED
CANopen RUN LED
2181 communication module (ModemCAN)TroubleshootingSignalling of the CANopen RUN LED and ERROR LED
66.86.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 offfor 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 theLED
A short lighting up (approx. 200 ms) followed by a long off phase(approx. 1000ms).
Double lighting up ofthe LED
LED shortly lights up twice in one sequence (approx. 200 ms),interrupted by an off phase (approx. 200 ms). The sequence iscompleted by a long off phase (approx. 1000ms).
Triple lighting up of theLED
LED shortly lights up thrice in one sequence (approx. 200 ms),interrupted by an off phase (approx. 200 ms). The sequence iscompleted by a long off phase (approx. 1000ms).
Message states and lightingrates
2181 communication module (ModemCAN)Appendix
Modem standards
66.9
6.9.1
6.9-1EDSFEW 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-M or MNP 2-4)
Data compression V.42bisp
MNP5
2181 communication module (ModemCAN)AppendixCountry list
66.96.9.2
6.9-2 EDSFEW EN 04/2005
6.9.2 Country list
The national telephone standards differ somewhat. For this reason thecommunication assembly needs to be configured for use in certaincountries.
The modem used supports the following standards:
ƒ CTR21 (Common Technical Regulation):This approval applies for all EU countries including Norway andSwitzerland. 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 adaptationswhichmust be entered into thedecimal code with code C1208 for this device (see table below).
Thefollowing listsprovides informationonthecountries inwhich thedevicecan be used in relation to telecommunication standards.
Note!If the respective country is not in the list, only an externalmodem that complies with the related national regulations isallowed 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
2181 communication module (ModemCAN)Appendix
Country list
66.9
6.9.2
6.9-3EDSFEW EN 04/2005
Approval
Code
Country ApprovaldechexCountry
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
New Zealand 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
2181 communication module (ModemCAN)AppendixAT commands
66.96.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 asubsequent data connection. This command is affected by the OEMfirmware configuration.
Command Default Defined values Result codes
\N 5 \N0 Selects normal speed buffered mode(disables error-correction mode). (Forces&Q6).
OKOtherwiseERROR
\N1 Serial interface selected: Selects direct modeand is equivalent to &M0, Q0mode ofoperation. (Forces &Q0). Parallel interfaceselected: Same as \N0.
\N2 Selects reliable (error correction) mode. Themodemwill first attempt an LAPM and thenanMNP connection. Failure to make areliable connection results in the modemhanging up.(Forces &Q5, S36=4 and S48=7).
\N3 Selects auto-reliable mode. This operates thesame as \N2 except failure to make a reliableconnection results in the modem falling backto the normal speed buffered mode. (Forces&Q5, S36=7 and S48=7).
\N4 Selects the LAPM error-correction mode.Failure to make an LAPM error-correctionconnection results in the modem hanging up.(Forces &Q5 and S48=0). Note: The K1command can override the \N4 command.
\N5 Selects MNP error-correction mode. Failure tomake anMNP error-correction connectionresults in the modem hanging up. (Forces&Q5, S36=4 and S48=128).
The modem loads the factory default configuration (profile). The factorydefaultsare identified foreachcommandand in theS-parameterparameterdescriptions. A configuration (profile) consists of a subset of S-parameters.
Command Default Defined values Result codes
- - &F0 Restore factory configuration 0. OKERROR if the
&F Restore factory configuration 1.ERROR if themodem isconnected.
Selects which user profile which will be used after a hard reset.
Command Default Defined values Result codes
&Y - &Y0 Themodemwill use profile 0. OKERROR if<value> > 1 orNVRAM is not
&Y1 Themodemwill use profile 1.NVRAM is notinstalled or isnotoperational.
Command: \NOperating mode - errorcorrection
Command: &FRestore factory configuration(profile)
Command: &YDesignate a default resetprofile
2181 communication module (ModemCAN)Appendix
AT commands
66.9
6.9.3
6.9-5EDSFEW EN 04/2005
Saves the current (active) configuration (profile) including S-parameters inone of the two user profiles in NVRAM, as denoted by the parameter value.This commandwill yield an errormessage if theNVRAM is not installed or isnot operational as detectedby theNVRAMtest. The current configuration iscomprised of a list of storable parameters illustrated in the &V commands.These settings are restored to the active configuration upon receiving aZ-command or at power up. (See &Y command).
Command Default Defined values Result codes
&W 0 &W0 Store the current configuration as profile 0. OKOtherwise
&W1 Store the current configuration as profile 1.OtherwiseERROR
Command: &WStore current configuration
2181 communication module (ModemCAN)AppendixAT commands
66.96.9.3
6.9-6 EDSFEW EN 04/2005
6.9.3.2 Interface commands for the DEE modem
Selects the subsetof the result codemessagesusedby themodemto informthe DEE of the results of commands. Blind dialing is enabled or disabled bycountry parameters. If the user wants to enforce dial tone identification, a”W” can be placed in the dial string (see D-commandwhich is not describedin this Manual). The information below is based upon the defaultimplementation 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 isCONNECT without a speed indication.
Command Default Defined values Result codes
X 4 X0 Disables reporting of busy tones unlessforced otherwise by country requirements;send only OK, CONNECT, RING, NO CARRIER,ERROR and NO ANSWER result codes. Blinddialing is enabled/disabled by countryparameters. If busy tone detection isenforced and busy tone is detected, NOCARRIER is reported. If dial tone detection isenforced or selected and dial tone is notdetected, NO CARRIER will be reportedinstead of NO DIAL TONE. The value 000b iswritten to S22 bits 6, 5 and 4, respectively.
OKOtherwiseERROR
X1 Disables reporting of busy tones unlessforced otherwise by country requirements:send only OK, CONNECT, RING, NO CARRIER,ERROR and NO ANSWER and CONNECT XXXX(XXXX = rate). Blind dialing enabled/disabledby country parameters. If busy tone detectionis enforced and busy tone is detected, NOCARRIER is will be reported instead of BUSY. Ifdial tone detection is enforced or selectedand dial tone is not detected, NO CARRIERwill be reported instead of NO DIAL TONE.The value 100b is written to S22 bits 6, 5 and4, respectively.
X3 Enables reporting of busy tones; send onlyOK, CONNECT, RING, NO CARRIER, ERROR, NOANSWER and CONNECT XXXX. Blind dialing isenabled/disabled by country parameters. Ifdial tone detection is enforced and dial toneis not detected, NO CARRIER will be reported.The value 110b is written to S22 bits 6, 5 and4, respectively.
X4 Enables reporting of busy tones; send allmessages. The value 111b is written to S22bits 6, 5 and 4, respectively.
Command: XExtended result codes
2181 communication module (ModemCAN)Appendix
AT commands
66.9
6.9.3
6.9-7EDSFEW EN 04/2005
6.9.3.3 Call control commands
ForcesDTMFdialing until the next P dialmodifier or P command is received.ThemodemsetsanS-parameterbit to indicate thateachsubsequentdialingshould be conducted in tonemode. The DP command (not described in thismanual) overrides this command. Clears S14 bit 5. This command may notbe permitted in some countries. (See P command).
Command Default Defined values Result codes
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 explicitlyspecifies a dialingmode for that particular call (e. g. ATDT...), this commandis overridden so that all future dialing will be tone dialled. (See Tcommand).This commandmay not be permitted in some countries.
Command Default Defined values Result codes
P OK
This command causes the modem to generate the guard tone selected bythis command (DPSKmodulationmodesonly). Theparameter value, if valid,is written to S23 bits 6 and 7. This commandmay not be permitted in somecountries.
Command Default Defined values Result codes
&G 0 &G0 Disables guard tone (default). <value> = 0 to 2
&G1 Disables guard tone. OtherwiseERROR
&G2 Selects 1800 Hz guard tone.ERROR
Determines the make/break ratio used during pulse dialing. The default iscountry-dependent. Theparametervalue, if valid, iswrittentoS28bits3and4.
Command Default Defined values Result codes
&P 0 &P0 Selects 39%-61%make/break ratio at 10pulses per second.
OKOtherwise
&P1 Selects 33%-67%make/break ratio at 10pulses per second.
ERROR
&P2 Selects 39%-61%make/break ratio at 20pulses per second.
&P3 Selects 33%-67%make/break ratio at 20pulses per second.
Command: TSet tone dial default
Command: PSet pulse dial default
Command: &GSelect guard tone
Command: &PSelect pulse dial make/breakratio
2181 communication module (ModemCAN)AppendixAT commands
66.96.9.3
6.9-8 EDSFEW EN 04/2005
6.9.3.4 Modulation control commands
This extended-format compound parameter controls the manner ofoperation of the modulation capabilities in the modem. It accepts sixsubparameters. 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> arelisted 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.92downstream
V92 56000, 54667, 53333, 52000, 50667, 49333, 48000, 46667,45333, 44000, 42667, 41333, 40000, 38667, 37333, 36000,34667, 33333, 32000, 30667, 29333, 28000
V.92upstream
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: +MSModulation selection
2181 communication module (ModemCAN)Appendix
AT commands
66.9
6.9.3
6.9-9EDSFEW EN 04/2005
Command Default Defined values Result codes
+MS <carrier>A string that specifies the preferred modem carrierto use in originating or answering a connection.<carrier> values are strings of up to eightcharacters, consisting only of numeric digits andupper case letters. <carrier> values for ITU standardmodulations take the form: <letter><1-4digits><other letters as needed>. Defined values arelisted in Tab. 6.9-1.
OK - ValidsubparameterstringOtherwiseERROR
<automode>A numeric value which enables or disablesautomatic modulation negotiation (ITU-T V.32bisAnnex 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>) rateat which the modemmay establish a receiveconnection. May be used to condition distinct limitsfor the receive direction as distinct from thetransmit direction. Values for this subparameter aredecimal encoded, in units of bit/s. The possiblevalues for each modulation are listed in Tab. 6.9-1.Actual values will be limited to possible valuescorresponding 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 selectedcarrier).
<min_tx_rate> and <max_tx_rate>Numeric values which specify the lowest(<min_rx_rate>) and highest (<max_rx_rate>) rateat which the modemmay establish a transmitconnection. Non-zero values for this subparameterare decimal encoded, in units of bit/s. The possiblevalues for each modulation are listed in Tab. 6.9-1.Actual values are limited to possible valuescorresponding 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 selectedcarrier).
Report commands
+MS? Reports current ratesResponse:+MS:<carrier>,<automode>,<min_tx_rate>, <max_tx_rate>,<min_rx_rate>,<max_rx_rate> Note:The current active settings are reportedunder control of the +MR parameters.Example:+MS: K56, 1,300,33600,300,56000 for default values.This example allowsmaximum system flexibility to determine optimal receiveand transmit rates during operation.
+MS=? Reports supported range of parameter valuesResponse:+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)
2181 communication module (ModemCAN)AppendixAT commands
66.96.9.3
6.9-10 EDSFEW EN 04/2005
Whenthemodemisconfiguredtoalloweitheroption, themodemwillselectBell orCCITTmodulationsfora linespeedconnectionof300or1200bps.Anyother line speedwill useaCCITTmodulation standard. Theparametervalue,if valid, is written to S27 bit 6.
Command Default Defined values Result codes
B 0 B0 Selects CCITT operation at 300 or 1200 bpsduring call establishment and a subsequentconnection (default).
OKOtherwiseERROR
B1 Selects BELL operation at 300 or 1200 bpsduring call establishment and a subsequentconnection.
Command: BCCITT or Bell
2181 communication module (ModemCAN)Appendix
AT commands
66.9
6.9.3
6.9-11EDSFEW EN 04/2005
6.9.3.5 Data compression commands
Enables or disables data compression negotiation. The modem can onlyperform data compression on an error-corrected link. The parameter value,if valid, is written to S41 bits 0 and 1.
Command Default Defined values Result codes
%C %C0 Disables data compression. Resets S46 bit 1. OK
%C1 Enables MNP 5 data compressionnegotiation. Resets S46 bit 1.
ERROR
%C2 Enables V. 42bis data compression. Sets S46bit 1.
%C3 Enables both V.42bis and MNP 5 datacompression. Sets S46 bit 1 (default).
Command: %CEnable/disable datacompression
2181 communication module (ModemCAN)AppendixAT commands
66.96.9.3
6.9-12 EDSFEW EN 04/2005
6.9.3.6 S-registers
Certainmodemvalues,orparameters, arestored inmemory locationscalledS-registers. Use the S-command (not described in thismanual) to read or toalter the contents of S-registers (see previous section). *Register value maybe 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 modem answers.ATS0=0 disables the auto-answer completely. *
S3 decimal 0 - 127 13 (^M) Carriage return character:Sets the command line and result code terminatorcharacter. Pertains to asynchronous operation only.
S4 decimal 0 - 127 10 (^J) Line feed character:Sets the character recognised as a line feed. Pertains toasynchronous operation only. The line feed controlcharacter is output after the carriage return controlcharacter 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-hookwhen blind dialing. This operation, however, may beaffected by some ATX options according to countryrestrictions. The ”Wait for dial tone” call progressfeature (W dial modifier in the dial string) willoverride the value in register S6 (when configured forUS).
2. Sets the length of time, in seconds, that the modemwill wait for dial tone when encountering a ”W” dialmodifier before returning NO DIAL TONE result code.(W class). Default is country-dependent. The modemalways pauses for a minimum of 2 seconds, even ifthe value of S6 is less than 2 seconds.
S7 seconds 1 - 255* 50 Wait time for carrier, silence, or dial tone:1. Sets the length of time, in seconds, that the modem
will wait for carrier before hanging up. The timer isstarted when the modem finishes dialing (originate),or 2 seconds after going off-hook (answer). Inoriginate mode, the timer is reset upon detection ofanswer tone if allowed by country restrictions.
2. Sets the length of time, in seconds, that modemwillwait for silence when encountering the@ dialmodifier before continuing with the next dial stringparameter.
3. Sets the length of time, in seconds, that the modemwill wait for dial tone when encountering a ”W” dialmodifier before continuing with the next dial stringparameter (US model). The default iscountry-dependent. *
S8 seconds 2 - 255 2 Pause time for dial delay:Sets the time, in seconds, that the modemmust pausewhen the ”,” dial modifier is encountered in the dialstring. *
2181 communication module (ModemCAN)Appendix
AT commands
66.9
6.9.3
6.9-13EDSFEW EN 04/2005
DescriptionDefaultRangeUnitRegister
S10 0.1 s 1 - 255 14 Lost carrier to hang up delay:Sets the length of time, in tenths of a second, that themodemwaits before hanging up after a loss of carrier.This allows for a temporary carrier loss without causingthe modem to disconnect. When register S10 is set to255, the modem functions as if a carrier is alwayspresent. *The actual interval the modemwaits beforedisconnecting is the value in register S10 minus thevalue in register S9. Therefore, the S10 value must begreater than the S9 value or else the modem disconnectsbefore it recognises the carrier..Note: For call waiting detection, if the modem is set toUS country code and S10 >=16, then the modemwilldetect 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.
2181 communication module (ModemCAN)Index
66.10
6.10-1EDSFEW EN 04/2005
6.10 Index
AAmbient temperature, 6.3-1
Appendix, 6.9-1
Application range, 6.2-1
Automatic baud rate detection, 6.7-9
BBaud rate of the external modem, 6.7-16
Bus cable length, 6.4-7
Bus load diagnostics, 6.7-7
CC0002, Parameter set management, 6.7-13
C0099, Software version, 6.7-13
C0150, status word, 6.7-13
C0200, Software manufacturer’s 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, CAN status, 6.7-5
C0360, telegram counter, 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, Modem initialisation, 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, modem reset, 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
CAN status, 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
Code numbers, Access via the communication module,6.6-2
Code numbers / index, Conversion, 6.6-2
Commissioning, 6.5-1
- Before you start, 6.1-1
Commissioning with the system bus 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
DData 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
EElectrical installation, 6.4-3
Elements of the communication module, 6.4-1
Error register, 6.7-11
2181 communication module (ModemCAN)Index
66.10
6.10-2 EDSFEW EN 04/2005
Examples, Indexing of Lenze codes, 6.6-2
FFeatures, 6.2-1
Fieldbus connection, 6.7-13
First switch-on, 6.5-6
GGeneral data, 6.3-1
HHardware version, Type code, 6.2-1
II-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 system bus configurator, 6.5-3
LLenze codes, 6.7-1, 6.7-2
MMechanical installation , 6.4-2
Modem initialisation, 6.7-15
Modem reset, 6.7-17
NNode address, 6.7-3
OOperating conditions, 6.3-1
Overall cable length, 6.4-7
PParameter 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
RRated data, 6.3-2
Read bus baud rate, 6.7-9
Repeat tests, 6.7-9
Reset node, 6.7-4
SSegment cable length, 6.4-7
Signalling, 6.5-6
Signalling acc. to DR303-3, 6.5-7
Software manufacturer’s 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
System requirements, 6.5-2
TTechnical data, 6.3-1
Telegram counter, 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
UUser name, 6.7-16
2181 communication module (ModemCAN)Index
66.10
6.10-3EDSFEW EN 04/2005
VValidity of the Instructions, 6.2-1
Voltage supply, 6.4-5
AppendixContent
7
7-1EDSFEW EN 04/2005
7 Appendix
This part of the Communication Manual includes additionalinformation on Lenze products which can be used for remotemaintenance.
Content
ƒ Software Manual «DriveServer»
ƒ Software Manual «Busserver S7»
Appendix7
7-2 EDSFEW EN 04/2005
AAmbient 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
BBaud 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
CC0002, 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 manufacturer’s 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, telegram counter, 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, Modem initialisation, 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, modem reset, 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
Code numbers, Access via the communication module,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 system bus 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
DData transfer, 5.6-1, 6.6-1
Appendix 7
7-3EDSFEW 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 Ethernetinterface, 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
EElectrical 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
FFeatures, 5.2-1, 6.2-1
Fieldbus connection, 6.7-13
First switch-on, 5.5-11, 6.5-6
GGateway, 5.7-17
General data, 5.3-1, 6.3-1
Guide, 2.1-1
HHardware version, Type code, 5.2-1, 6.2-1
II-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 system bus configurator, 5.5-2, 6.5-3
IP address, 5.7-15
LLabelling, 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
MMAC-ID, 5.7-16
Manufacturer, 1.3-4
Mechanical installation , 5.4-2, 6.4-2
Modem initialisation, 6.7-15
Modem reset, 6.7-17
MPCs, 5.7-4
NNode address, 5.7-5, 6.7-3
Notes, definition, 3.3-1
OOperating conditions, 5.3-1, 6.3-1
Operator, 3.1-1
Overall cable length, 5.4-6, 6.4-7
PParameter 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
Appendix7
7-4 EDSFEW EN 04/2005
RRated 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
SSafety 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 manufacturer’s 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
System requirements, 5.5-1, 6.5-2
TTechnical data, 5.3-1, 6.3-1
Telegram counter, 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
UUser name, 6.7-16
VValidity of the Instructions, 5.2-1, 6.2-1
Voltage supply, 5.4-4, 6.4-5
Preface, 1.1-1
WWarranty, 1.3-5
Waste disposal, 1.3-5
DriveServer
Software Manual
L
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: [email protected]
Copyright information
All texts, photos and graphics contained in this documentation are subject tocopyright protection. No part of this documentation may be copied or madeavailable to third parties without the explicit written approval of Lenze DriveSystems GmbH.
Liability
All information given in this documentation has been carefully selected andtested for compliance with the hardware and software described.Nevertheless, discrepancies cannot be ruled out. We do not accept anyresponsibility or liability for any damage that may occur. Required correctionwill be included in updates of this documentation.
Trademarks
Microsoft, Windows and Windows NT are either registered trademarks ortrademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of AdobeSystems Incorporated in the U.S.A. and/or other countries.
All other product names contained in this documentation are trademarks ofthe corresponding owners.
DriveServerContents
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
L 2.0 EN 3
DriveServerContents
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
4 2.0 EN L
DriveServerAbout this ManualConventions 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 openautomation 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 ofinformation:
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 ofmenu commands
If several commands must be used in sequence to carry out a function, then the individual commands are separated by an arrow: Select File Open 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 Courier IF var1 < var2 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 5
DriveServerAbout this ManualDefinition of notes used
1.2 Definition of notes used
This documentation uses the following signal words and symbols to indicate danger andimportant 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 voltageIndicates 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 dangerIndicates an impending danger that may lead to death or severe personal injury if the corresponding measures are not taken.
Stop! Danger of material damageIndicates a potential danger that may lead to material damage if the corresponding measures are not taken.
Pictograph Signal word Meaning
Note! Important note for trouble-free operation
Tip! Useful tip for easy handling
6 2.0 EN L
DriveServerSystem requirements
2 System requirements
The following minimum requirements on hardware and software must be met to use theDriveServer:
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.
L 2.0 EN 7
DriveServerSystem requirementsConnection to the target system
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 targetsystems 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 Requiredhardware components
Requiredsoftware components
System bus (CANopen)
Parallel interface
(LPT port)
63 PC system bus adapter 2173incl. 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(UniversalSerial Bus)
63 PC system bus adapter 2177incl. 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 ( 35)
52(optical
fibre)
• Fieldbus module EMF 2102IB V003 • Optical fibre adapter (EMF2125IB) • Power supply for adapter (EJ0013) • Optical fibre cable (EWZ0007)
8 2.0 EN L
DriveServerSystem requirements
Connection to the target system
2.1.1 Direct fieldbus connection
Since the system bus is not master/slave oriented, new participants can be added to thefieldbus system without special recognition of the central master.
All nodes can communicate with each other. It is thus possible to connect a PC directly tothe corresponding bus through a system bus interface module. All devices connected canbe addressed.
2.1.2 Fieldbus connection via PLC
If the system consists of a master and several slaves, it is often difficult to connect afieldbus 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 andthen address the drives. We offer a similar solution for the PROFIBUS-DP which uses aSiemens Simatic S7 PLC as master.
More information on this solution can be found in the appendix.Lenze bus server S7 ( 35)
PC PLC
PC
PLC
L 2.0 EN 9
DriveServerSoftware installation
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!
10 2.0 EN L
DriveServerSoftware installationComponent selection
3.1 Component selection
The DriveServer installation program enables you to select the components you want toinstall 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 ( 35)
Please observe the instructions for the installation/commissioning of the bus server hardware/software!
L 2.0 EN 11
DriveServerIntroductionStructure of the DriveServer system
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. Thedialog box is called "Printer features". Although the interface is standardised, theparameters can be set for a specific printer.
The DriveServer also provides a standardised interface to enable access to the drives viadifferent fieldbus systems.
4.1 Structure of the DriveServer system
The following figure shows the basic components of the DriveServer system:
DrivesIn the centre you can see the drives which are addressed by several PC programs, for instance visualisation and parameter setting programs.
FieldbusesThe drives are connected through different fieldbuses, which require different drivers.
Bus serversDrivers 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.
DriveServerThe 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 toolsOPC 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)
12 2.0 EN L
DriveServerIntroduction
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 overcomecomputer 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 thesetwo 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 Windowstechnologies OLE, COM and DCOM which enables data exchange between differentautomation units and PC programs without having any problems with drivers andinterfaces.
Sometimes this tool is also called "Software plug", because programs of differentmanufacturers can be easily connected for communication. Especially manufactures ofvisualisation systems use OPC since it is then possible to do without special drivers fordifferent units.
OPC was created in 1996 in the United States and since then has been spread in theautomation industry. The user group OPC Foundation comprises morethan 150 companies, among them is Lenze.
Basic structure
The basic structure of OPC is a client/server system. An OPC server provides data which areread 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 theOPC client are also possible.
Several OPC clients can access one or several OPC servers (n:n connection) at the same time.
L 2.0 EN 13
DriveServerIntroductionOLE for Process Control
Items/Groups
Usually data is exchanged via so-called OPC items which are represented by processvariables 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 thebrowse function. The Browse function helps the OPC client to find all OPC items (alsoparameters) 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 alsopossible 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.
14 2.0 EN L
DriveServerConfiguration
DCOM
5 Configuration
One of the main objectives of the DriveServer is to reduce the configuration of the systemto a minimum (Plug and Drive). Unfortunately, it is not possible to completely do withouta 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 localnetwork. To protect the PC from unauthorised access, the safety standards do not allowOPC access. Before commissioning the DriveServer, these settings must be checked andchanged, 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.
L 2.0 EN 15
DriveServerConfigurationDCOM
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 root Component services Computerto go to the object My computer.
3. Highlight the object My computer and select Action Properties 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 File Exit to exit the Microsoft Management Console.
Windows NT/2000
How to configure DCOM under Windows NT/2000...
1. Go to the Start menu and select Run...
2. Enter "dcomcnfg" in the input field and click OK to open the dialog box DCOM properties.
3. Select the tab Standard properties.
4. Activate DCOM on this computer.
5. Go to the Standard authentication level and set "No".
6. Go to the Standard idenfication level and set "Anonymous".
7. Select the tab Standard safety.
16 2.0 EN L
DriveServerConfiguration
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...
1. Go to the Start menu and select Run...
2. Enter "dcomcnfg" in the input field and click OK to open the dialog box DCOM properties.
3. Select the tab Standard properties.
4. Activate DCOM on this computer.
5. Go to the Standard authentication level and set "No".
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.
9. Click OK to save the settings and close the dialog box.
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.
L 2.0 EN 17
DriveServerConfigurationDCOM
5.1.2 More settings for the OPC server
Furthermore, it is necessary to enter the users who are authorised to use all serverapplications.
Windows XP
How to configure the server applications 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 root Component services Computerto 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 Action 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, activate the option box System account (services only) instead.
8. Click the OK button to save the settings.
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 File Exit to exit the Microsoft Management Console.
18 2.0 EN L
DriveServerConfiguration
DCOM
Windows 98/Me, Windows NT/2000
How to configure the server applications under Windows 98/Me, Windows NT or Windows 2000...
1. Go to the Start menu and select Run...
2. Enter "dcomcnfg" in the input field and click OK to open the dialog box DCOM 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.
8. Click the OK button to save the settings.
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. Click OK to save the settings and close the dialog box.
L 2.0 EN 19
DriveServerConfigurationLECOM bus server
5.2 LECOM bus server
The LECOM bus server is configured with the program “LECOM configurator" and consistsof the selection and configuration of the COM interface and the detection of the connectedLECOM unit.
How to configure the LECOM bus server
1. Go to the Start menu and select Programs Lenze DriveServer LECOM 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 File New.
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 elementincludes 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.
20 2.0 EN L
DriveServerConfiguration
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 theconfiguration.
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 ( 22)
L 2.0 EN 21
DriveServerConfigurationLECOM bus server
5.2.3 Detection of the LECOM drives connected
In this second configuration step the LECOM drives connected to the PC are to be detectedby 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 File Save to save the current configuration.
3. Select File Exit to exit the LECOM configurator.
22 2.0 EN L
DriveServerConfiguration
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 theselected interface module.
Go to Start menu and selectPrograms Lenze Communication Systembus 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.
L 2.0 EN 23
DriveServerConfigurationDriveServer
5.4 DriveServer
Since all fieldbus specific settings are saved directly in the corresponding bus server, theDriveServer 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 Programs Lenze DriveServer DriveServer 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.
OnlineThis element includes a list of all bus servers and drives assigned to DriveServer.
OfflineWhereas 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 serverEvery fieldbus system requires its own bus server which then ensures communication between all drives connected.
DriveA drive is connected to a bus server or configured as “Offline drive" (see “Offline").
24 2.0 EN L
DriveServerConfiguration
DriveServer
Tip!
If a plus sign appears in front of the element in the tree structure, this elementincludes 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.
GroupA 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.
ParametersParameters represent the lowest level of the name.
Icon Element/meaning
L 2.0 EN 25
DriveServerConfigurationDriveServer
5.4.2 DriveServer selection
Since a network environment can comprise several DriveServers (OPC servers), theDriveServer to be configured is to be selected first.
How to select the DriveServer to be configured...
1. Select File Choose 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 File Connect 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 Configuration Bus server to open the dialog box Bus server configuration.
26 2.0 EN L
DriveServerConfiguration
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.
L 2.0 EN 27
DriveServerConfigurationDriveServer
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 File Disconnect to disconnect a bus server from the DriveServer selected.
7. Select File Exit to exit the DriveServer configurator.
The configuration is completed and the DriveServer can be started.
Operation ( 29)
28 2.0 EN L
DriveServerOperation
Starting the DriveServer
6 Operation
The DriveServer enables communication via several media. As OPC server it operates in thebackground and does therefore not feature its own user interface. This interface isprovided 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 nextparagraph 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, theDriveServer starts all bus servers and identifies the drives by means of the addresses sentfrom the bus servers.
Identification means that the DriveServer checks every address for Lenze controllers. If aLenze controller is indicated in the address, the DriveServer detects the parameters of thecorresponding controller. Based on this information, the name area for the DriveServersystem is created, which lists all drives with its parameters in form of a tree. OPC clients canaccess the tree by means of the OPC browse function via two ways:
HierarchicalThe name area corresponds to the tree structure created by the DriveServer.
FlatThe name area consists of only one level which includes all elements.
The following illustration shows a part of the (hierarchical) tree structure for a DriveServersystem with three fieldbus systems connected - PROFIBUS-DP, CANopen and LECOM:
L 2.0 EN 29
DriveServerOperationAccess via OPC clients
6.2 Access via OPC clients
The DriveServer can be accessed by the following software components which serve asOPC clients and have been optimised for Lenze controllers:
The DriveServer configurator which has already been described in the previous chapter. DriveServer ( 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 theDriveServer.
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 theDriveServer system via the DriveServer configurator.
How to access the name area of the DriveServer system...
1. Go to Start menu and select Programs Lenze DriveServer DriveServer 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!
30 2.0 EN L
DriveServerOperation
Access via OPC clients
The following figure shows a part of a name area for a system consisting of a “9300 Servoinverter" 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 theDriveServer 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).
L 2.0 EN 31
DriveServerDriveServer architectures (examples)Access via a LAN (Local Area Network)
7 DriveServer architectures (examples)
In the following subchapters you will find a short description of architectures implementedwith the DriveServer. Since there are so many configurations possible, the followingexamples can only show some typical DriveServer architectures:
Access via a LAN (Local Area Network)
Transparent access using a PLC ( 33)
Access to different fieldbus systems via a LAN ( 34)
7.1 Access via a LAN (Local Area Network)
The following figure shows a system architecture which allows access to a drive networkin 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).
32 2.0 EN L
DriveServerDriveServer architectures (examples)
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 tohave a direct connection to the fieldbus.
The following figure shows a system architecture with a Simatic S7 control made bySiemens 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.
L 2.0 EN 33
DriveServerDriveServer architectures (examples)Access to different fieldbus systems via a LAN
7.3 Access to different fieldbus systems via a LAN
Since the DriveServer can access different fieldbus systems at the same time it is possibleto 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.
34 2.0 EN L
L 2.0 EN 35
DriveServerAppendix
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 specificationwhich 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 forthe connection to the PC. It must be provided with an automatic change of direction sincedue 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 GmbHHumboldstraße 3670771 Leinfelden/Echterdingen
DriveServerAnhangGlossary
8.2 Glossary
B
Bus server Fieldbus-specific OPC server according to the DRIVECOM specification.
OPCDRIVECOM
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.
Internet: http://www.can-cia.org
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).
36 2.0 EN L
DriveServerAnhang
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.
COMDCOM
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.
L 2.0 EN 37
DriveServerIndex
38 2.0 EN L
9 Index
AApplication notes 6
BBrowse function 14
Bus server for the system bus 23
Bus server S7 35
Bus servers 12
CCOM 14
COM interface 21
Connection to the target system 8
Conventions used 5
Copyright 2
Copyright information 2
DDCOM 13, 14, 15
Direct fieldbus connection 9
drives 12
DriveServer configuration tool 24, 30
EE-mail to Lenze 39
FFeedback to Lenze 39
Fieldbus connection via PLC 9
Fieldbuses 12
GGroups 14
Hhardware components 8
IImprint 2
Installation 10
Items 14
LLayout of the safety information 6
LECOM 8, 13
LECOM bus server 20
LECOM configuration tool 20
Liability 2
Local Area Network 32
Nname 30
OOffline 24
OLE for Process Control 13
Online 24
OPC interface 31
OPC server selection 24
PParameters 25
Plug and Drive 15
PROFIBUS-DP 35
RRS232/RS485 interface converter 35
SSafety 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
TTrademarks 2
Transparent access 33
UUser interface 7
L 39
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:
Thank you for your support.
Your Lenze documentation team
Bus server S7
Software Manual
L
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: [email protected]
Copyright information
All texts, photos and graphics contained in this documentation are subject tocopyright protection. No part of this documentation may be copied or madeavailable to third parties without the explicit written approval of Lenze DriveSystems GmbH.
Liability
All information given in this documentation has been carefully selected andtested for compliance with the hardware and software described.Nevertheless, discrepancies cannot be ruled out. We do not accept anyresponsibility or liability for any damage that may occur. Required correctionwill be included in updates of this documentation.
Trademarks
Microsoft, Windows and Windows NT are either registered trademarks ortrademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of AdobeSystems Incorporated in the U.S.A. and/or other countries.
All other product names contained in this documentation are trademarks ofthe corresponding owners.
Bus server S7Contents
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
L 2.0 EN 3
Bus server S7Contents
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
4 2.0 EN L
Bus server S7Contents
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
L 2.0 EN 5
Bus server S7About this ManualConventions used
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 specificationwhich 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 ofinformation:
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 ofmenu commands
If several commands must be used in sequence to carry out a function, then the individual commands are separated by an arrow: Select File Open 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 Courier IF var1 < var2 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.
6 2.0 EN L
Bus server S7About this Manual
Definition of notes used
1.2 Definition of notes used
This documentation uses the following signal words and symbols to indicate danger andimportant 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 voltageIndicates 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 dangerIndicates an impending danger that may lead to death or severe personal injury if the corresponding measures are not taken.
Stop! Danger of material damageIndicates a potential danger that may lead to material damage if the corresponding measures are not taken.
Pictograph Signal word Meaning
Note! Important note for trouble-free operation
Tip! Useful tip for easy handling
L 2.0 EN 7
Bus server S7System requirementsConnection to the target system
2 System requirements
The following minimum requirements on hardware and software must be met in order tooperate 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 operatingsystem!
• 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 tocommunicate 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 ( 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!
8 2.0 EN L
Bus server S7System 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
Sie
me
ns
Co
mm
un
ica
tio
n
driv
er
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
L 2.0 EN 9
Bus server S7System requirementsSupported protocols
2.2.1 IBHLink
2.2.2 COMxMPI
Use "MPI Simatic" as protocol if the Siemens communication driver (V5.0 or higher) isinstalled 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)
PC interface Transmission medium PLC interface Additional software required
COMx RS-232 PC adapterRS-232/485 MPI
-
PC interface Transmission medium PLC interface Additional software required
USB USB PC adapterUSB MPI
Siemens communication driver(V5.0 or higher)
COMx RS-232 PC adapterRS-232/485 MPI
Siemens CP5611(PCI card)
MPI MPI
Siemens CP5511(PCMCIA card)
Modem Teleservice Siemens teleservice adapter MPI
Siemens communication driver(V5.0 or higher) andSiemens teleservice(V5.0 or higher)
Ethernet Ethernet IBHLink adapter cable Ethernet MPI
Siemens communication driver(V5.0 or higher) andIBHNet (V1.1 or higher)
PC interface Transmission medium PLC interface Additional software required
COMx RS-232 PC adapter RS-232/485 PROFIBUS-CP
Siemens communication driver(V5.0 or higher)
USB USB PC adapter USBPROFIBUS-CP
Siemens CP5611(PCI card)
PROFIBUS PROFIBUS-CP
Siemens CP5511(PCMCIA card)
10 2.0 EN L
Bus server S7System requirements
Supported protocols
2.2.5 SOFTNET TCP/H1
Under normal circumstances, the TCP protocol is used. When using older CPs it mayhappen that only the Siemens H1 protocol is supported. This is why the bus server S7 alsosupports 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 simultaneousaccess with Lenze and Siemens software is required.
PC interface Transmission medium PLC interface Additional software required
Ethernet Ethernet TCP/H1 Ethernet-CP Siemens SOFTNET/SIMATICNET(V3.0 or higher)
PC interface Transmission medium PLC interface Additional software required
Ethernet Ethernet TCP Ethernet-CP -
L 2.0 EN 11
Bus server S7System requirementsSupported PLC hardware
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 functionblock instance is to be activated for each drive to be addressed. This means that one datablock 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.
12 2.0 EN L
Bus server S7Software installation
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.
L 2.0 EN 13
Bus server S7Software installationComponent selection
3.1 Component selection
From the installation program of the DriveServer you can select the components you wantto 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®
14 2.0 EN L
Bus server S7Configuration
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, thecorresponding interface module must be configured first so that the bus server canestablish a communication with the PLC.
For all other protocols the required communication parameters are directly adjusted in thebus server configurator!
How to configure the PG/PC interface...
1. Go to the Start menu and select Settings System 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.
L 2.0 EN 15
Bus server S7ConfigurationBus server configuration
4.2 Bus server configuration
The bus server is configured via the "S7 configurator" program. Upon configuration, thePLC 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 Programs Lenze DriveServer S7 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 File New.
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".
16 2.0 EN L
Bus server S7Configuration
Bus server configuration
Tip!
If a plus sign appears in front of a configuration entry, this configuration entryhas 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 ( 62)
4.2.2 Automatic PLC detection
First the PLCs connected must be specified. For this purpose the scan function of the S7configurator 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 ( 19)
Tip!
The scan function scans the MPI network for connected PLCs and for the drivesconfigured 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.
L 2.0 EN 17
Bus server S7ConfigurationBus server configuration
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 asconfiguration entries.
Tip!
The S7 configurator automatically creates several OPC items for every drive. It isthus 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.
Scan at the servers start
If the Scan at the servers start control field is activated, the PLC and the drives configuredin 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.
18 2.0 EN L
Bus server S7Configuration
Bus server configuration
4.2.3 Manual addition of PLCs
For the protocols "SOFTNET TCP/H1" and "TCP direct" and alternatively to the scan functionyou 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.
L 2.0 EN 19
Bus server S7ConfigurationBus server configuration
4.2.4 PLC parameters
The following table contains all parameters relevant for the PLC configuration. Whichparameters 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 ( 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 address1) 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 ( 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 ( 23)
PC-MPI address1) 2) MPI- or PROFIBUS address of the PC
Baud rate2) Transmission speed on the MPI bus between PC and PLC.
Max. MPI address2) Highest node address on the MPI bus.
Single master2) 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 ( 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 number1) 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.
20 2.0 EN L
Bus server S7Configuration
Bus server configuration
4.2.5 Automatic drive detection
If the PLC is connected to the PC and the PLC program has already been transferred to thePLC, the drives configured in the PLC program can be automatically detected if this had notyet 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 isthus 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.
Scan during server start
If the Scan at the servers start control field is activated, the drives configured in the PLCprogram 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.
L 2.0 EN 21
Bus server S7ConfigurationBus server configuration
4.2.6 Manual addition of drives
As an alternative to using the scan function you can also add drives to the configurationmanually.
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.
22 2.0 EN L
Bus server S7Configuration
Bus server configuration
4.2.8 Configuration of subsystems
If the PLC which is connected to the PC is provided with a "routing function", it is alsopossible to access controllers which are not connected to the PROFIBUS of this (master) PLCbut 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 configurationsteps are required:
1. Manual addition of the master PLC to the configuration. Manual addition of PLCs (
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 bymeans of the scan function on which addresses the controllers in the PLC program of thesubsystem have been configured.
L 2.0 EN 23
Bus server S7ConfigurationBus server configuration
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 thePROFIBUS of the subsystem, two PLCs must be configured in the Lenze S7configurator.
• 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.
24 2.0 EN L
Bus server S7Configuration
Bus server configuration
4.2.9 Manual removal of configuration entries
Configuration entries (PLCs, devices, OPC items, etc.) can be removed from the tree viewany 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 File Save to save the current configuration.
Tip!
Select File Save as... to save the current configuration with a different name.
4.2.11 Exit the S7 configurator
Select File Exit to exit the S7 configurator.
Note!
If there are changes not saved yet, it is queried if these changes are to be saved.
L 2.0 EN 25
Bus server S7Creating a STEP7 projectOverview of the STEP7 blocks
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 namesinstead of the corresponding block numbers in the STEP7 project, you first have to createthem in the symbol table.
In the following subchapter, the program structure will be explained in detail.
Symbolicblock 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
PAPE
DB S7PAR
S7
PAPE
Parameter data channel
Process data channel
Drive 1
OPC via
S7 protocol
FCparameter
FCprocessdata
26 2.0 EN L
Bus server S7Creating a STEP7 project
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
OB1DB S7PAR
FCprocess data
FB DRIVEparameter
d 2rive
FB DRIVEparameter
drive 1
FB DRIVEparameter
d nrive
FC
process data
FB DRIVE
parameter
FB DRIVE
parameter
FB DRIVE
parameter
FC
parameterFC
parameter
L 2.0 EN 27
Bus server S7Creating a STEP7 projectFiles provided
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. Thefollowing 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 asstandard in the directory: "C:\Programs\Lenze\DriveServer\S7".
How to integrate the library into the STEP7 environment...
1. Select File Dearchive 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 Symbolicblock 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.
28 2.0 EN L
Bus server S7Creating a STEP7 project
Files provided
5.3.2 STEP7 example programs
The scope of supply of the bus server S7 includes the following example programs whichonly differ in the hardware configuration.
After the "DriveServer with bus server S7" software is installed, the example programs aresaved as standard in the directory: "C:\Programs\Lenze\DriveServer\S7".
Tip!
If you want to use one of the example programs, adapt the hardware configurationto your system environment.
Detailed information on creating a STEP7 program:Creating a STEP7 program ( 33)
How to integrate an example program into the STEP7 environment...
1. Select File Dearchive 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 filesof 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 homepagehttp://www.Lenze.de in the Service Downloads PROFIBUS 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
L 2.0 EN 29
Bus server S7Creating a STEP7 projectCreation of new projects
5.4 Creation of new projects
Tip!
The following steps are described exemplarily with STEP7 in version 5.0. In otherSTEP7 versions the single dialogs may vary slightly.
Select File Assistant '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 structuresimilar to the one shown below:
The next step is to configure the MPI and the PROFIBUS interface for the project. Moredetails 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.
30 2.0 EN L
Bus server S7Creating a STEP7 projectHardware 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. Click OK to save the settings and close the dialog box.
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 Insert DP 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 View Catalog 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-DP Further field devices Drives 2131), 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 Extras Update 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)".
L 2.0 EN 31
Bus server S7Creating a STEP7 projectHardware configuration
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 maybe configured with the Hardware Manager e.g. communication processors for PROFIBUS orEthernet.
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.
32 2.0 EN L
Bus server S7Creating a STEP7 project
Creating a STEP7 program
5.6 Creating a STEP7 program
To implement the Lenze function blocks, several options are possible. For a simple test, theblocks 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 connectedto 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 thehardware configuration must be adapted to your system environment.
STEP7 example programs ( 29)
If you want to create a program on your own, you simply have to integrate the suppliedblocks 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 ( 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.
L 2.0 EN 33
Bus server S7Creating a STEP7 projectCreating a STEP7 program
How to create an own program...
1. Create a new project with the "OB1" block.
2. Select File Open.
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 HardwareManager and once in the calling program. It must be ensured that both datacorrespond to each other!
CALL "Lenze-DriveServer_FB", DB100 FB90
Tag :=PB_Address :=B#16#9EA_Address :=1000DriveServer_DB :="Lenze-DriveServer_FB" DB80DrivePar_DB :="S7-Parameter" DB81TimerNr :=T1TimeOut :=Busy :=MB100
BE
34 2.0 EN L
Bus server S7Creating a STEP7 project
Creating a STEP7 program
Provided that a drive is available at PROFIBUS address 9, the system can be operated withthis program.
Load the program into the PLC and try to detect the drive automatically using the S7 configurator. Automatic PLC detection ( 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 theselanguages.
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 connectedto the PROFIBUS master of the CPU card but also controllers with are connected to anexternal PROFIBUS communication processor (CP).
For this, please use the block "FB DRIVE" instead of the block "FB DRIVE CP" in the STEP7 program.
L 2.0 EN 35
Bus server S7Creating a STEP7 projectCreating a STEP7 program
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-DriveServer_FB", DB100 FB91
Tag :=PB_Address :=B#16#9First_DriveDW :=0DriveSend_DB :="Lenze-DriveServer_Send" DB30DriveRecv_DB :="Lenze-DriveServer_Recv" DB31DriveServer_DB :="Lenze-DriveServer_FB" DB80DrivePar_DB :="S7-Parameter" DB81TimerNr :=T1TimeOut :=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.
36 2.0 EN L
Bus server S7Creating a STEP7 project
Creating a STEP7 program
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 processand parameter data from the PLC:
Tip!
The aforementioned example program "Ldsexmpl.arj" contains both OPC and PLCaccesses, and can be used as basis for your own program developments.
Block number Symbolicblock name
Function
FC90 FC parameter Function used to write parameter data jobs in DB S7PAR.FC90 (FC parameter) ( 45)
FC91 FC process data Function for process data access (3 process data words)FC91 (FC process data three words) ( 47)
FC92 FC process data Function for process data access (2 process data words)FC92 (FC process data, two words) ( 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) ( 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) ( 49)
L 2.0 EN 37
Bus server S7Creating a STEP7 projectTesting the STEP7 program
5.7 Testing the STEP7 program
When the program has been completed, it can be loaded into the PLC and tested. The S7configurator 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 theDriveServer:
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 thefollowing 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.
38 2.0 EN L
Bus server S7Creating a STEP7 project
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 noparameter communication takes place. Since several parameters are checked when"FB DRIVE" is called, programming errors can be detected and the corresponding errormessages can be indicated. However, the checking costs computing time.
To save computing time, you can operate the "FB DRIVE" in expert mode. This reduces therequired 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 thecorresponding instance data block.
If so, go to the IL editor and create a new STEP7 instance data block. Then you canuse 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.
L 2.0 EN 39
Bus server S7Creating a STEP7 projectAccessing PLC data
5.9 Accessing PLC data
With the bus server S7, you can access both the parameters of the controllers and the PLCdata. 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 theindividual OPC items must be configured.
See also: 'Block' tab ( 66)
'Item' tab (for block) ( 68)
40 2.0 EN L
Bus server S7Appendix
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 ( 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
L 2.0 EN 41
Bus server S7AppendixTransmission times
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
42 2.0 EN L
Bus server S7Appendix
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.
L 2.0 EN 43
Bus server S7AppendixCommunication function parameters
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
Parameters Data type Possible values/meaning
PB_Address IN: BYTE 0 ... 31 PROFIBUS address of the drive (hexadecimal) • Address 1 = "1", address 15 = "F"
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 PROFIBUS communication processor (CP)
44 2.0 EN L
Bus server S7Appendix
Communication function parameters
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
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
Parameters Data type Possible values/meaning
Parameters Data type Possible values/meaning
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) • Address 1 = "1", address 15 = "F"
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
0x40 Count parameter is outside the range 0 ... 31
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.
0x82 PB_Address parameter is incorrect (permitted values: 1 ... 123)
0x83 Peripheral error, for details see R_Value parameter
0x84 Job could not be processed within the time set via the TimeOut parameter.
L 2.0 EN 45
Bus server S7AppendixCommunication function parameters
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.
Parameters Data type Possible values/meaning
46 2.0 EN L
Bus server S7Appendix
Communication function parameters
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)
Function for process data access
The function FC92 can be used for both consistent and inconsistent process data transfer.
Parameters Data type Possible values/meaning
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 FALSE TRUE TRIP reset executed
Setpoint1 IN: INT Process setpoint (AIF-IN:W1)
Setpoint2 IN: INT Process setpoint (AIF-IN:W2)
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)
ActualValue2 OUT: INT Actual process value (AIF-OUT:W2)
StatusWord OUT: WORD Status word according to DRIVECOM specification
Parameters Data type Possible values/meaning
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 FALSE TRUE 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
L 2.0 EN 47
Bus server S7AppendixCommunication function parameters
6.3.6 FC93 (FC process data, three words, CP)
Function for process data access
Consistent process data transfer is a prerequisite for using this function!
Parameters Data type Possible values/meaning
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 PROFIBUS communication processor (CP)
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 FALSE TRUE TRIP reset executed
Setpoint1 IN: INT Process setpoint (AIF-IN:W1)
Setpoint2 IN: INT Process setpoint (AIF-IN:W2)
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)
ActualValue2 OUT: INT Actual process value (AIF-OUT:W2)
StatusWord OUT: WORD Status word according to DRIVECOM specification
48 2.0 EN L
Bus server S7Appendix
Communication function parameters
6.3.7 FC94 (FC process data, two words, CP)
Function for process data access
The "FC94" function can be used for both consistent and inconsistent process data transfer.
Parameters Data type Possible values/meaning
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 PROFIBUS communication processor (CP)
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 FALSE TRUE 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
L 2.0 EN 49
Bus server S7AppendixRemote maintenance via modem
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 standardmodem. The programming unit also equipped with a modem is now able to communicatewith the PLC via a standard telephone line.
Instead of using the programming device to carry out the remote maintenance, you canalso 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 requiredfor 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
50 2.0 EN L
Bus server S7Appendix
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 programfor 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)
L 2.0 EN 51
Bus server S7AppendixS7-400 example project
6.5.3 Symbolic variable names
Symbolic names are used in the “LenzeDriveServer" example project. These names aresaved 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 • Bit0 ... Bit4 are hidden and cannot be described.
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.
52 2.0 EN L
Bus server S7Appendix
S7-400 example project
We recommend the use of symbolic variable names for clarity. However, they are notcompulsory.
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) ( 47)
FC91 (FC process data three words) ( 47)
CALL FC 92 // FC92, 2 PZDEA_Address :=1008 //I-address, decimalEnable :="Enable" //BOOLQSP :="QSP" //BOOLReset :="Reset" //BOOLSetpoint1 :="Setpoint1" //INT, decimalControlWord :="ControlWord" //WORD, control wordRDY :="RDY" //OUT, BOOLTRIP :="TRIP" //OUT, BOOLActualValue1 :="ActualValue1" //OUT, INTStatusWord :="StatusWord" //OUT, status word
Tip!
When three process data words are to be transmitted, the "FC91" block must be used.
L 2.0 EN 53
Bus server S7AppendixS7-400 example project
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) ( 44)
L "StatusWord" // disconnectedL 0 // controller==I // areSPB NEXT // skipped.
CALL FB 90 , DB100 Tag := // STRING PB_Address :=B#16#9 // BYTE, B#16#x EA_Address :=1000 // E address decimal DriveServer_DB :="DB-OPC server" // DBx; z.B. DB80 DrivePar_DB :="S7 parameter" // DBx; z.B. DB81 TimerNr :="TimeOutTimer_OPC" // TIMER TimeOut :=S5T#1S // TIME Busy :="BUSY" // OUT, BYTE
NEXT: NOP 0
54 2.0 EN L
Bus server S7Appendix
S7-400 example project
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) ( 45)
UN "TriggerRead"= "TriggerRead"CALL FC 90 // data typesDrivePar_DB :="S7 parameter" // DB81Count :=0 // decimal: 0-31PB_Address :="PB address" // B#16#9R_W :=TRUE // FALSE or TRUECode :="Code" // W#16#C, code 12SubCode :="Subcode" // B#16#0, subcode 0W_Value :="Value" // DINT or L#xxxStatus :="ReadStatus" // OUT, BYTE, status byteR_Value :="ReadValue" // OUT, DINT, valueTrigger :="TriggerRead" // INOUT, BOOL
L 2.0 EN 55
Bus server S7AppendixS7-400 example project
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.
See also: FC90 (FC parameter) ( 45)
UN "TriggerWrite"= "TriggerWrite"CALL FC 90 // data typesDrivePar_DB :="S7 parameter" // DB81Count :=1 // decimal: 0-31PB_Address :="PB address" // B#16#9R_W :=FALSE // FALSE or TRUECode :="Code" // W#16#C, code 12SubCode :="Subcode" // B#16#0, subcode 0W_Value :="WriteValue" // DINT or L#xxxStatus :="WriteStatus" // OUT, BYTE, status byteR_Value :="WriteResult" // OUT, DINT, valueTrigger :="TriggerWrite" // INOUT, BOOL
56 2.0 EN L
Bus server S7Appendix
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 thesubdirectory "\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
L 2.0 EN 57
Bus server S7AppendixExample project S7-300 with PROFIBUS-CP
6.6.3 Symbolic variable names
The symbolic variable names used are the same as in the "S7-400" example projectdescribed before. Symbolic variable names ( 52)
We recommend the use of symbolic variable names for clarity. However, they are notcompulsory.
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 requiredfor the data exchange with the communication processor.
The CPLADDR parameter requires the I/O address of the PROFIBUS-CP, which is listed in theslot 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 exchangebetween 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 1CPLADDR :=W#16#100SEND :=P#DB30.DBX 0.0 WORD 15 DONE :=M1.0ERROR :=M1.1STATUS :=MW2
CALL FC 2CPLADDR :=W#16#100RECV :=P#DB31.DBX 0.0 WORD 15 NDR :=M1.2ERROR :=M1.3STATUS :=MW3DPSTATUS :=MB12
Slot I-address O-address
58 2.0 EN L
Bus server S7Appendix
Example project S7-300 with PROFIBUS-CP
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 94FirstDriveDW :=8DriveSend_DB :="DriveSend_DB"DriveRecv_DB :="DriveRecv_DB"Enable :="Enable"QSP :="QSP"Reset :="Reset"Setpoint1 :="Setpoint1"ControlWord :="ControlWord"RDY :="RDY"TRIP :="TRIP"ActualValue1 :="ActualValue1"StatusWord :="StatusWord"
L 2.0 EN 59
Bus server S7AppendixExample project S7-300 with PROFIBUS-CP
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 beused.
See also: FC94 (FC process data, two words, CP) ( 49)
FC93 (FC process data, three words, CP) ( 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 thePLC. The change-over between both protocols takes place automatically. Thus, the blockoperates 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 "StatusWord"L 0==ISPB NEXT
CALL FB 91 , DB100 Tag := PB_Address :=B#16#9 FirstDriveDW :=0 DriveSend_DB :="DriveSend_DB" DriveRecv_DB :="DriveRecv_DB" DriveServer_DB :="DB-OPC-Server" DrivePar_DB :="S7 parameter" TimerNr :="TimeOutTimer_OPC" TimeOut :=S5T#1S Busy :="BUSY"
NEXT: NOP 0
60 2.0 EN L
Bus server S7Appendix
Example project S7-300 with PROFIBUS-CP
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) ( 44)
6.6.7 Reading/writing a parameter
The functions for reading and writing a parameter are called regardless whether the deviceconnected to the PROFIBUS of the CPU or an external communication processor. In bothcases the "FC90" function is used.
See also: FC90 (FC parameter) ( 45)
Reading a parameter ( 55)
Writing a parameter ( 56)
L 2.0 EN 61
Bus server S7AppendixS7 configurator - settings
6.7 S7 configurator - settings
When you select a configuration entry in the tree view of the S7 configurator, a tab isdisplayed in the right window area on which the parameters of the correspondingconfiguration entry can be changed.
6.7.1 'Common settings' tab
The Common settings tab is displayed if the topmost configuration entry "S7" has beenselected from the tree view/list view.
Scan for control systems connected
Tip!
The parameters relevant for the PLC configuration depend on the protocolselected. PLC parameters ( 20)
For the protocols "MPI Simatic", "PROFIBUS-DP" and "COMx MPI", the PLCs connected canbe automatically detected via the Scan button. Automatic PLC detection ( 17)
If the Scan at the servers start control field is activated, the PLC and the drives configuredin 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.
For the protocols "SOFTNET TCP/H1" and "TCP direct" and alternatively to the scan functionyou can also add the PLCs connected manually to the configuration. Manual addition ofPLCs ( 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.
62 2.0 EN L
Bus server S7Appendix
S7 configurator - settings
Create LOG file
When the Create LOG file control field is activated, the S7 bus server logs selectable eventsin 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 viewfor 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
must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
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.
L 2.0 EN 63
Bus server S7AppendixS7 configurator - settings
Search for Lenze devices
If the PLC is connected to the PC and the PLC program has already been transferred to thePLC, the drives configured in the PLC program can be automatically detected via the Scanbutton if this had not yet been done by the automatic detection of the PLC. Automaticdrive detection ( 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
must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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 ( 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
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.
64 2.0 EN L
Bus server S7Appendix
S7 configurator - settings
6.7.3 'Device' tab
The Device tab is displayed if the configuration entry is selected from the tree view/listview for a device.
Button Function
Add Click this button to add a device to the configuration. • A dialog box is shown in which the name of the device to be added is defined.
After confirming with OK the S7 PLC tab is displayed for the device added. • 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.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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. • 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 selected device. • A query appears if you really want to delete the configuration entry. By clicking
the No button, you can abort the function.
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
name must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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.). • 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
must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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.
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.
L 2.0 EN 65
Bus server S7AppendixS7 configurator - settings
6.7.4 'Block' tab
The Block tab is displayed if the configuration entry is selected from the tree view/list viewfor 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. • A dialog box is shown in which the name of the block to be added is defined. After
confirming with OK the S7 PLC tab is displayed for the block added. • The name for the block must already be assigned for another block, and the name
must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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. • A query appears if you really want to delete the configuration entry. By clicking
the No button, you can abort the function.
Rename Click this button to rename the block selected. • After this, enter the new name into the dialog box New name and confirm this
entry with OK.
Add item Click this button to manually add an item to the block 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 block selected. • The name for the item must not already be assigned for another item, and the
name must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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. • 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. • 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.
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.
66 2.0 EN L
Bus server S7Appendix
S7 configurator - settings
Static config. If the Static configuration control field is activated and if several write requests areavailable in a transaction at the same time, these are not executed successively but in onestep. 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 viewfor an item.
Bit mask When the Masking in bits is activated, a mask can be defined within the range for theincoming 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
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 an item to the configuration. • A dialog box is shown in which the name of the item to be added is defined. After
confirming with OK the S7 PLC tab is displayed for the item added. • The name for the item must not already be assigned for another item, and the
name must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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. • A query appears if you really want to delete the configuration entry. By clicking
the No button, you can abort the function.
Rename Click this button to rename the item selected. • After this, enter the new name into the dialog box New name and confirm this
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".
L 2.0 EN 67
Bus server S7AppendixS7 configurator - settings
Example:
Scaling When the Scaling control field is activated, scaling is executed with the value of theselected 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 itemcan 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 viewfor an item.
Tip!
The items assigned to a device serve to access the drive parameters, whereas itemsassigned 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 00 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.
Parameter/option Meaning/function
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.
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.
68 2.0 EN L
Bus server S7Appendix
S7 configurator - settings
Scaling When the Scaling control field is activated, scaling is executed with the value of theselected 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 itemcan be specified in the Limits from/to input fields.
Further settings
Button Function
Add Click this button to add an item to the configuration. • A dialog box is shown in which the name of the item to be added is defined. After
confirming with OK the S7 PLC tab is displayed for the item added. • The name for the item must not already be assigned for another item, and the
name must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) [ ] @ , < > ! % & | = # .
• 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. • A query appears if you really want to delete the configuration entry. By clicking
the No button, you can abort the function.
Rename Click this button to rename the item selected. • After this, enter the new name into the dialog box New name and confirm this
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.
Parameter/option Meaning/function
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.
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.
L 2.0 EN 69
Bus server S7AppendixFAQ - Frequently asked questions
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 ( 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 ( 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.
70 2.0 EN L
Bus server S7Appendix
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 "Can’t 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 Extras Settings.
Question Answer
L 2.0 EN 71
Bus server S7Index
72 2.0 EN L
7 Index
AAccess via OPC 33
Application notes 7
Automatic PLC detection 17
BBaud rate 20
CCOMxMPI 10
Conventions used 6
Copyright 2
Copyright information 2
CPU slot number 20
DDB OPC 26, 28
DB S7PAR 26, 28
Device description files 29
DP address of the device 22
DriveServer name area 38
EE-mail to Lenze 73
Ethernet 8
Expert mode 39
FFB DRIVE 26, 28, 44
FB DRIVE CP 28, 44
FC parameter 28
FC process data 28
Feedback to Lenze 73
Files provided 28
IIBHLink 10
Imprint 2
Installation 13
Interface module 8
JJOb list DB number 20
LLayout of the safety information 7
Liability 2
MManual addition of PLCs 19
Max. MPI address 20
Mounting rack number 20
MPI 8
MPI interface 31
MPI Simatic 10
PPC-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
RRAM requirements 12
Response time 20
Routing function 23
SS7 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
TTCP direct 11
Time-out 22
Trademarks 2
Transmission times 42
UUser interface 8
L 73
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:
Thank you for your support.
Your Lenze documentation team