SIMODRIVE 611 Universal Guide
SIMODRIVE 611 Universal Guide
Function Block FB 83
for SIMODRIVE 611 universal ↔ S7-CPU
General Information 1
Traversing Task 5
Function Block FB 83 Processing
SIMODRIVE 611 universal
↔ S7-CPU Configuring the 6
SIMODRIVE 611 universal
in the S7 Station
Errors 7
Valid for
Contents
1. General Information
This block supports data transfer between a SIMODRIVE 611 universal and an S7-CPU via Profibus.
The data interfaces are individually defined in a data block by having a structure with pre-configured
UDTs.
The principal communications structure of a SIMODRIVE 611 universal with a Class 1 DP master is
illustrated in Fig. 1. In this case, the process data (PZD) and the task data (PKW) are consistently
transferred over the complete length of the PZD or PKW area. The control and return signals are
defined in more detail in the User Interface Assignment.
PP O SFC 15 20 Byte
DB T yp 5
SFC 14 20 B yte
S7-CPU 611U
Task data (PKW)
PP O SFC 15 8 Byte
DB T yp 5
S FC 14 8 Byte
PKW interface
The telegram structure of the PKW interface is illustrated in Fig. 2 (also refer to the description of
functions, SIMODRIVE 611 universal).
PKW interface
DB axis 1
UDT Obligatory
task data
UDT positioning
UDT positioning operation or
operation UDT nset must be available
UDT nset
In the first S7-CPU cycle, the FB83 checks which data areas the user defined (Fig. 4). This is
specified in the internal data. The S7-CPU must be re-started if the structure of an axis-specific DB is
changed.
Important! The FB_611 universal block must be called during the first PLC cycle. It this is not done,
the UDT autoscan is not run, as this scan was realized with SFC6.
I n st a n c e D B
In te r n a l d a ta U D T d a ta
The structure of the obligatory UDT is illustrated in Fig. 5. The precise assignment of the UDT is
provided in the User Interface Assignment.
For operation with n axes, only n+1 DBs are required if the internal data is saved in a multi-instance
DB; refer to Fig. 6.
DB axis 1
Two Any Pointers must be transferred for each axis in order to transfer process data. The process
data should be preferably in a DB (Any Pointer, for example: p#db71.dbx 166.0 byte 20). If the
process data are to be saved in a DB, UDTs 30010 for positioning or UDT 30009 for closed-loop
speed controlled operation can be used (this is recommended as the individual bits of the process
data are symbolized in the UDT).
FB_611 universal
NR_ACHS_DB INT
LADDR INT
WR_PZD ANY
RD_PZD ANY
enable _SFC_PZD BOOL
FUNCTION_BLOCK FB 100
TITLE =
VERSION : 0.1
VAR
a1 : FB 83;
END_VAR
BEGIN
NETWORK
TITLE =
CALL #a1 (
NR_ACHS_DB := 71,
LADDR := 256,
WR_PZD := P#DB71.DBX 166.0 BYTE 20,
RD_PZD := P#DB71.DBX 206.0 BYTE 20,
enable_SFC_PZD := TRUE);
END_FUNCTION_BLOCK
The data consistency over the complete length is defined in parameter enable_SFC_PZD. For a
consistent data transfer over the word, the parameter set should be set to false. If consistent data
transfer over the complete length is present, the parameter should be set to true. The PKW data are
always consistently transferred over the complete length independent of enable_SFC_PZD. Only the
PZD area can be changed over. Refer to Configuring SIMODRIVE 611 universal in the S7 station
when checking the data consistency.
False:
The PZD area is consistent over the unit. Process
data is transferred via load/transfer commands.
There are two procedures: Either you open project 611U_39 and change the project for the
application, or you already have a functioning project and you only insert the interface.
1. Open the block folder and edit data blocks 71 and 72. Remove the UDTs which are not required.
Remove axis data blocks which are not required (if only one axis is required).
1. Insert the FB 83 and the required UDTs into the existing S7 project.
UDT30000 = basis UDT
UDT30001 = edit 64 traversing blocks
UDT30002 = read-out faults
UDT30009 = closed-loop speed controlled operation
UDT30010 = positioning operation
2. Create a data block for each axis which contains the required UDTs.
The UDT 30000 must always be included in the axis data block and be called at the first position.
Refer to the examples for positioning and closed-loop speed controlled operation.
Positioning operation
Address Name Type Initial value Comments
0.0 STRUCT
+0.0 al UDT30000 Basis UDT
+156.0 p UDT30010 Positioning operation UDT
+246.0 v UDT30001 Traversing block UDT
+1538.0 s UDT30002 Fault UDT
=2318.0 END_STRUCT
Example:
Call the interface FBs (FB 83) in this function block (call block).
FB 83 must be called once for each axis.
Set the call for the call block at the position it will be used.
Example: call FB 40, DB40 è whereby DB40 is the new multi-instance DB of the interface
Set-up error OBs if required (OB 81, 82, 86, 87, 121, 122).
Open the new data block and assign the FB83 as instance data block.
If changes are made at the data block with reference to the UDT arrangement, then a new start must
be made, otherwise autoscan does not register the changes.
Never change UDT headers.
Important! Do not change UDTs. If UDTs are changed, then read and write length errors can occur.
Error
DBW 12 ErrorNumbr611U
chain_task
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
DBW 54 chain_PNU_1
DBW 56 chain_IND_1
DBD 58 chain_Data_1
DBW 62 chain_PNU_2
DBW 64 chain_IND_2
DBD 66 chain_Data_2
DBW 70 chain_PNU_3
DBW 72 chain_IND_3
DBD 74 chain_Data_3
DBW 78 chain_PNU_4
DBW 80 chain_IND_4
DBD 82 chain_Data_4
DBW 86 chain_PNU_5
DBW 88 chain_IND_5
DBD 90 chain_Data_5
DBW 94 chain_PNU_6
DBW 96 chain_IND_6
DBD 98 chain_Data_6
DBW 102 chain_PNU_7
DBW 104 chain_IND_7
DBD 106 chain_Data_7
DBW 110 chain_PNU_8
DBW 112 chain_IND_8
DBD 114 chain_Data_8
DBW 118 chain_PNU_9
DBW 120 chain_IND_9
DBD 122 chain_Data_9
DBW 126 chain_PNU_10
DBW 128 chain_IND_10
DBD 130 chain_Data_10
4.2. Description
Address Symbol. Name Description
DBW 0 UDT Nummer Number of the UDTs from here. Initial value:
30000
DBW 2 UDT Länge Length of the UDTs from here in bytes.
Initial value: 156
DBW 4 Kontrollnummer Initial value: 30000
DBW 12 ErrorNumbr611U Error number of 611 univ. is saved here.
DBX 14.0 RD Reading data
DBX 14.1 WR Writing data
DBX 14.2 Done Feedback, task completed
DBX14.3 Busy Task is being processed.
DBX 14.7 Error Task cancelled with error.
DBW 16 tasksi Task number, this can be a parameter number
or special task number.
DBW 18 ind Sub-parameter number. Refer to the description
of functions, SIMODRIVE 611 universal,
Section, Parameter lists.
DBD 20 Data Value which is to be written or value read-out
after a read task.
DBW 24 ErrorNumbr Error number of an error which occurred when
executing the task. -1 means no error. Refer to
Section 8
DBX 34.0 RD Reading parameter.
DBX 34.2 Done Feedback, task completed
DBX 34.3 Busy Task is being processed.
DBX 34.7 Error Task cancelled with error.
DBW 36 taskpe Special task number
DBW 38 Ind Sub-parameter number. Refer to the description
of functions, SIMODRIVE 611 universal, Section
Parameter lists.
DBD 40 Data Reserved
DBW 44 ErrorNumbr Error number for task execution. –1 means no
error.
DBW 54, 62 ..., 126 chain_PNU_1-10 Parameter number for permanently reading-out
a piece of data
DBW 56, 64 ..., 128 chain_IND_1-10 Sub-parameter number associated to the
parameter number.
DBD 58, 66, ..., 130 chain_Data_1-10 Parameter value transferred from the 611 univ.
DBX 134.0 Satznum Preselection, which parameters are to be
transferred (134.1 to 134.7)
DBX 134.1 pos Select, position
DBX 134.2 gesch Select, velocity
DBX 134.3 beschover Select, acceleration
DBX 134.4 verzover Select, deceleration
DBX 134.5 bef Select, command
DBX 134.6 befpara Select, command parameter
DBX 134.7 mod Select, mode
DBW 136 Satznummer Value, block number
DBW 138 Position Value, position
DBW 140 Geschw Value, velocity
DBW 142 Beschl_over Value, acceleration override
DBW 144 Verzoeg_over Value, deceleration override
DBW 146 Befehl Value, command
DBW 148 Befehlsparameter Value, command parameter
DBW 150 Modus Value, mode
ã Siemens AG 2001 All Rights Reserved
Function Block FB 83 Version 03 Description Page 15 of 22
Edition 02.2001
Important: The task may only be initiated if all of the task data are available.
Using the single task interface, tasks can be initiated which are only executed once. The status bit is
set to busy while the task is running. If the task has been completed, busy is reset and the Done bit is
set. If an incorrect parameter number (tasksi), an incorrect sub-parameter number (IND) or an
incorrect piece of data was entered, the error bit is set and in the error compartment, an error number
is specified which is described in the description of functions SIMODRIVE 611 universal in Section 5,
Error evaluation (also refer to Section 8).
1 2 1 3 1 1 2
WR/RD
Busy
Done
Error
4 5
Using the permanent task interface, tasks are initiated which are continually read-out (e.g. position
actual value during axis motion). If an incorrect parameter number (taskpe), or an incorrect sub-
parameter number (IND) was entered, the error bit is set and in the error compartment, an error
number is specified which is described in the Description of Functions SIMODRIVE 611 universal in
Section 5, Error evaluation (also refer to Section 8).
Task management
Using the 611 universal task interface single, two types of tasks can be started:
• All of the parameters from SIMODRIVE 611 universal
(refer to the parameter list in the attachment to the Description of Functions
SIMODRIVE 611 universal)
• Special tasks
Values: Fault cases and the number of faults are saved in the
associated data block in UDT 30002.
Values: Read = values are saved in the assoc. data block UDT 30001
Write = values are transferred from the data block to the
SIMODRIVE 611universal
Values: chain_Data_xy
Values are in the particular data compartments of the
parameter numbers.
When selecting a second 2-axis module with PPO type 5, your hardware configuration looks like this.
The I/O addresses 256 to 283 are assigned to drive A. I/O addresses 284 to 311 are associated with
drive B. Addresses 256 to 263 and 284 to 291 are the PKW (parameter ID value) data (task data
telegram, 4-words long). The PZD (process data, 10-words long) are transferred to Profibus at I/O
addresses 264 to 283 and 292 to 311.
CAUTION!
The address areas may not be separated. PKW and PZD must merge seamlessly with one another
without any gaps.
SIEMENS AG Corrections
for document:
A&D MC BMS SIMODRIVE 611 universal
Postfach 3180
Function Block FB 83
D-91050 Erlangen for SIMODRIVE 611 universal
↔ S7-CPU
Description
From
Name
Edition: 02.2001
______________________________________________________________________________________________________
Company address/Dept.
Should you come across any printing
Street
_______________________________________________________________________________________________________ errors when reading this publication,
please notify us on this sheet.
Postal code: City:
_______________________________________________________________________________________________________
Suggestions for improvement are also
Telephone: / welcome.
_______________________________________________________________________________________________________
Telefax: /