2 accessing several drives via opc, 3 accessing drives connected to profibus cps, Accessing several drives via opc – Lenze Drive Server Bus server S7 getting started User Manual

Page 32: Accessing drives connected to profibus cps, Busserver s7

Advertising
background image

Busserver S7

L

93

Busserver S7 DE/EN 1.0

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 function block

FB DRIVE (FB90) 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 drives connected to PROFIBUS CPs

If an S7-300 is used, you can address drive controllers which are directly connected to the PROFIBUS

master of the CPU card and drive controllers which are connected with an external PROFIBUS

communication processor (CP).
For this, please use the block

FB DRIVE CP instead of the block FB DRIVE in the STEP7 program.

Example of a transfer parameter list:

CALL

”Lenze-DriveServer_FB”, DB100

FB91

Tag

:=

PB_Address

:=B#16#9

First_DriveDW

:=0

DriveSend_DB

:=”Lenze-DriveServer_Send”

DB30

DriveRecv_DB

:=”Lenze-DriveServer_Recv”

DB31

DriveServer_DB

:=”Lenze-DriveServer_FB”

DB80

DrivePar_DB

:=”S7-Parameter”

DB81

TimerNr

:=T1

TimeOut

:=

Busy

:=MB100

BE

The following transfer parameters are used in addition to the parameters listed in chapter 5.6.1

on page 91.

The parameter FirstDriveDW defines the byte position of the first data word of the connected

drive controller.

For each drive controller, 8 data words are reserved in the data blocks

DriveSend_DB and /

or

DriveRecv_DB. The first 4 data words are needed for parameter access and the last 4

data words for process data access.

The drive controllers must have successive I/O addresses.

DriveSend_DB is the send block for communication with the 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 delivery package includes

DB30 with UDT93 (4 process data words).

DriveRecv_DB is the receive block for communication with the 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 delivery package includes

DB31 with UDT93 (4 process data words).

Show/Hide Bookmarks

Advertising