This Manual contains notices which you should observe to ensure your own personal
safety, as well as to protect the product and connected equipment. These notices are
highlighted in the Manual by a warning triangle and are marked as follows according to
the level of danger:
indicates an imminently hazardous situation which, if not avoided, will result in death or
serious injury.
indicates a potentially hazardous situation which, if not avoided, could result in death or
serious injury.
used with the safety alert symbol indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury.
used without safety alert symbol indicates a potentially hazardous situation which, if not
avoided, may result in property damage.
NOTICE
Correct usage
Trademarks
used without the safety alert symbol indicates a potential situation which, if not avoided,
may result in an undesireable result or state.
Note the following:
This device and its components may only be used for the applications described in the
catalog or the technical description, and only in connection with devices or components
from other manufacturers which have been approved or recommended by Siemens.
SIMATIC and SIMADYN D are registered trademarks of Siemens AG.
Third parties using for their own purposes any other names in this document which refer
to trademarks might infringe upon the rights of the trademark owners.
Copyright SIEMENS AG 2004 All rights reserved
The reproduction, transmission or use of this document or its
contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights
created by patent grant or registration of a utility model or design,
are reserved.
Siemens AG
A&D
Frauenauracher Straße 80
91056 Erlangen
Disclaimer of liability
We have checked the contents of this manual for agreement with
the hardware and software described. Since deviations cannot be
precluded entirely, we cannot guarantee full agreement.
However, the data in this manual are reviewed regularly and any
necessary corrections included in subsequent editions.
Suggestions for improvement are welcomed.
Siemens AG 2004
Technical data subject to change.
Siemens Aktiengesellschaft
Page 3
Editions
FM 458-1 DP
Manual
Function Blocks
Edition 12.2004
NOTE
Overview
(chapter editions)
Please note that the current edition of this documentation contains
different editions of the individual chapters. The following overview tells
you when a chapter was revised the last time.
This Manual explains the principle use and functions of the STEP 7
automation software with the main focus on the appropriate technological
and drive control components T400, FM 458-1 DP, SIMADYN D,
SIMATIC TDC or D7-SYS.
TDC: Technology and Drives Control
This Manual addresses programmers and commissioning engineers.
General knowhow regarding automation technology is required in order to
understand the contents of the Manual
This Manual is valid for SIMATIC D7-SYS Version 6.2.
If you have questions relating to the use of the products described in the
Manual, which cannot be answered here, then please contact your local
Siemens office. You can also call the Hotline:
• Tel.: +49 (180) 5050-222
• Fax: +49 (180) 5050-223
• e-mail: adsupport@siemens.com
Appropriate training courses are available in order to make it easier to get
to know the SIMADYN D automation system. Please contact the central
Training Center in D-Erlangen (I&S IS INA TC):
• Tel.: +49 (9131) 7-27689, -27972
• Fax: +49 (9131) 7-28172
• Internet: www.siemens.de/sibrain
• Intranet: http://info-tc.erlm.siemens.de/
NOTE
This user part of the Manual does not include any detailed
information/instructions with individual descriptions, but is only intended
to provide a basic procedure. More detailed information on the dialog
boxes in the software and how they are handled is provided in the
appropriate online help.
Function Blocks - FM 458-1 DP iii
Edition 12.2004
Page 5
Foreword
Information
overview
This manual is part of the overall documentation for the technological and
drive control components T400, FM 458, SIMADYN D, SIMATIC TDC
and SIMATIC D7-SYS:
Title Content
System and
communications
configuring D7-SYS
STEP 7 option packages
for D7-SYS
Hardware The complete hardware spectrum is described as reference in this Manuals.
Function blocks
The first project in a few steps
This Section provides an extremely simple entry into the methodology when
assembling and programming the SIMATIC TDC/SIMADYN D control
system. It is especially conceived for first-time users of a control system.
System software
This Section provides basic know-how about the structure of the operating
system and an application program of a CPU. It should be used to obtain an
overview of the programming methodology, and basis for configuring user
programs.
Communications configuring
This section provides you with basic know-how about the communication
possibilities and how you configure links to the communication partners.
Changeover from STRUC V4.x to D7-SYS
Essential features are included in this section, which have changed over
STRUC V4.x with the introduction of SIMATIC D7-SYS.
Basis software
This section explains the essential use and the functions of the STEP 7
automation software. For first users, it provides an overview on configuring,
programming and commissioning a station.
When working with the basis software, you can access the online help which
provides you with support when it comes to detailed questions on using the
software.
CFC
The CFC language (Continuous Function Chart) allows you to graphically
interconnect blocks.
When working with the particular software, you can also use the online help
which can answer detailed questions regarding the use of the
editors/compiler.
SFC
Configuring sequence controls using SFC (Sequential Function Chart) of
SIMATIC S7.
In the SFC editor, you generate a sequence chart using graphic resources.
The SFC elements of the chart are then positioned according to specific
rules.
These Reference Manuals provide you with an overview of selected function
blocks for the associated technological and drive control components T400,
FM 458-1 DP, SIMADYN D and SIMATIC TDC.
iv Function Blocks - FM 458-1 DP
Edition 12.2004
Page 6
Foreword
Guide
A&D Technical
Support
As first time user, we recommend that this Manual is used as follows:
• Please read the first section on using the software in order to get to
know some of the terminology and basic procedure.
• Then use the particular sections of the Manual if you wish to carry-out
certain processing steps (e.g. loading programs).
If you have already executed a small project, and have gained some
experience, then you can read individual sections of the Manual in order
to get up to speed about a specific subject.
Can be accessed globally at any time of the day:
World-wide
(Nürnberg)
Technical Support
Local time: 0:00 to 24:00 / 365 days
Phone: +49 (180) 5050-222
Fax: +49 (180) 5050-223
E-Mail: adsupport@siemens.com
GMT: +1:00
Europe / Africa
(Nürnberg)
Authorization
Local time: Mo.-Fr. 8:00 to 17:00
Phone: +49 (180) 5050-222
Fax: +49 (180) 5050-223
E-Mail: adsupport@siemens.com
GMT: +1:00
Technical Support and Authorization speak generally German and English.
United States
(Johnson City)
Technical Support and
Authorization
Local time: Mo.-Fr. 8:00 to 17:00
Phone: +1 (423) 262 2522
Fax: +1 (423) 262 2289
E-Mail:
Index ..............................................................................................................................................I-1
viii Function Blocks - FM 458-1 DP
Edition 12.2004
Page 9
1 Input/output blocks
Assignment of the input/output blocks to processor- and peripheral
devices.
Blocks Modules
PM5 PM6 T400 IT41 IT42 EA12 EB11 FM
458
SBM x x
*) with SBM2 Module
EXM
438
EXM
448*)
ITSL*)
Function Blocks - FM 458-1 DP 1-1
Edition 12.2004
Page 10
Input/output blocks
1.1 SBM Rotary encoder block
Symbol
SBM
hardware address ―GV AD YPIDI―position in increments
alarm- or normal FP ―BO DM QF BO―group error message
encoder type ―I TYP RPIDI―max. increments/revolution
baud rate ―I BDR YR―normalized speed
resolution ―I EXP U I―revolutions
rated speed ―R RS YFDW―error detection
Brief description
The SBM function block is used to realize the following tasks:
• Initialize the rotary encoder, which is connected at the SBM2 module
• Determine the position and speed from the encoder data
• Error handling when communication errors develop between the
encoder and SBM2 module
Mode of operation
During the initialization phase of the system, the initialization I/O are read
and the appropriate mode set at the SBM2 module. The following
settings are made for the EQN1325 encoder:
• The encoder power supply is set to 5 V
• Number of revolutions to 4096
• Signal periods per revolution 8192
After the mode has been set, the zero position is determined, and the
starting values for the position and the speed output at the connections.
In the standard mode, the block can assume four different statuses:
• NRM
The values read-out from the SBM2 module (position and speed) are
displayed at the block connections. If an error is detected, the block
goes into the ERR error condition.
• ERR
The following errors can occur in operation:
• Encoder is defective or is not connected
• Encoder was disconnected
• Data transfer error for serial communications between the encoder
and SBM2 module
• SBM2 module not available
In the first three cases, the block goes into the "INI“ initialization
status and in the latter case into the "OFF" status.
1-2 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 11
Input/output blocks
• INI
as for the "initialization phase“ mode
• OFF
Output QF is set and processing terminated.
I/O
AD
TYP
BDR
EXP
DM
RS
YPI
RPI
Y
Hardware address of the SBM2 (initialization input)
Encoder type
TYP = 0 not available
TYP = 1 EQN1325
TYP > 1 incorrect encoder type
Configure the block in cyclic tasks or interrupt tasks
DM=0 SBM in interrupt tasks
This mode is only practical in conjunction with the alarmcontrolled SIMOLINK events (sync interrupt from SLB). Using this
sync interrupt, in this mode, the values of the SBM module are
de-latched. The block should then be configured in the alarm task
started by the same event.
DM=1 SBM in cyclic tasks
If the block is computed in cyclic tasks, then the SBM2 module
register is read-out in the system mode. The contents of the register
are then read-out in the normal mode and the values for the output
connections computed.
Rated speed in revolution/min (RS>0) (default: 1.0)
Position in increments (default: 0)
Max. number of increments per revolution
(depending on the input connection EXP)
RPMmin
encoderrotary the speedform Normalized
RS
(initialization input
default: 1)
(initialization input
default: 0)
(default: 23)
(initialization input
default: 0)
(default: 0)
(default: 0.0)
U
QF
YF
Revolutions (default: 0)
Group error message
QF=0 no error, QF=1 for error (if YF≠0)
Error status of the block
YF=0x0000 no error, YF>0x0000 (refer to error statuses)
(default: 0)
(default:
16#0000 0000)
Function Blocks - FM 458-1 DP 1-3
Edition 12.2004
Page 12
Input/output blocks
Error statuses
Value Significance
Nibble 1
0x0001 Initialization mode
0x0002 No SBM2 module available
0x0004 SBM2 module is processed from another SBM
0x0008 Encoder defective/not available
Nibble 2
0x0010 Unknown carrier or illegal module code
0x0020 Incorrect hardware address
0x0040 Encoder fault/error
→ Check the hardware (encoder, cable etc.)
0x0080 No voltage or short-circuit
Nibble 3
0x0100 No data transfer from or to the encoder
→ check the hardware (encoder, cable etc.)
0x0200 Erroneous data transfer from or to the encoder
→ check the hardware (encoder, cable etc.)
0x0400 Invalid mode parameterized
0x0800 Invalid encoder parameterized
Nibble 4
0x1000 Invalid speed normalization parameterized
0x2000 Invalid baud rate parameterized
0x4000 Sampling time too high; speed computation not possible
→Sampling time: ≤ 4.0 ms
0x8000 Error for the request to save
Nibble 5
0x10000 Invalid resolution parameterized
0x20000 Function block is not configured in the alarm task
0x40000
0x80000
Nibble 6-8
Not defined: Reserve → Default: 0
Not defined: Reserve → Default: 0
Not defined: Reserve → Default: 0
Configuringdata
Computation time [µs] FM 458-1 DP 13,2
Can be inserted online No
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features Can only be used with an EQN 1325 encoder
1-4 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 13
2 Communication blocks
2.1 Central coupling blocks
NOTE
Additional information on this group of function blocks, e.g. symbol,
mode of operation, I/O and technical data are provided in the online
help for the particular block.
2.1.1 @CSL2F PROFIBUS FMS coupling central block
Brief description
• the function block initializes and monitors the PROFIBUS FMS
coupling (CS7 and SS5 module).
• the function block may only be configured in the sampling interval
32 ms <= TA <= 256 ms and only in the communications FP
"Transmit". Otherwise, an entry is made in the communications error
field.
2.1.2 @CSL2L PROFIBUS FDL central block
Brief description
• the function block initializes and monitors the PROFIBUS FDL
coupling (CS7 and SS5 module).
• the function block may only be configured in the sampling interval
32 ms <= TA <= 256 ms and only configured in the communications
FP "transmit". Otherwise an entry will be made in the communications
error field.
2.1.3 @CSPRO Central block PROFIBUS DP coupling
Brief description
Function Blocks - FM 458-1 DP 2-1
Edition 12.2004
• the function block initializes and monitors the PROFIBUS DP coupling
(EXM 448/EXM 448-1).
• the function block may only be configured in the sampling interval
32 ms <= TA <= 256 ms . Otherwise an entry is made in the
communications error field.
Page 14
Communication blocks
2.1.4 @PRODP Central block PROFIBUS DP coupling
Brief description
• the function block initializes and monitors the PROFIBUS DP coupling
at connector X03 on FM 458-1 DP.
• the function block may only be configured in the sampling interval
32 ms <= TA <= 256 ms . Otherwise an entry is made in the
communications error field.
2-2 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 15
Communication blocks
―
―
―
―
―
―
―
―
2.2 Kopplung PROFIBUS DP
2.2.1 DPDIAG Diagnostics overview, PROFIBUS DP
Symbol
DP module name.connector ―GV CTS OK BO―Diagnostics valid
Brief description
DPDIAG
Enable ―BO EN DG1
DG2
DG3
DG4
DL1
DL2
DL3
DL4
MSTBY―Master status
IDW―Identification number
QTSBO―Block status
YTSW―Status display
Slave diagnostics; bits 0 to 31
DW
Slave diagnostics; bits 32 to 63
DW
Slave diagnostics; bits 64 to 95
DW
Slave diagnostics; bits 96 to 127
DW
Data transfer list; bits 0 to 31
DW
Data transfer list; bits 32 to 63
DW
Data transfer list; bits 64 to 95
DW
Data transfer list; bits 96 to 127
DW
The task of the DPDIAG function block is to provide the following
information and data to the user program (i.e. the configured CFC
software):
• System diagnostics (an overview of which slave had signaled
diagnostics)
Mode of operation
• Data transfer list (overview of with which slave data transfer took
place within the PROFIBUS-DP time frame)
• Master status (master-specification information such as the Stop,
Operate and Clear stati)
The PROFIBUS-DP interface is selected using connection CTS.
The function block only enters a communications error for errors, which
are detected during initialization. A communications error cannot be
acknowledged and this function block is only used for diagnostics. This
means, that in normal operation, a communications error is not entered.
Only the cause of the error is signaled at output YTS.
Function Blocks - FM 458-1 DP 2-3
Edition 12.2004
Page 16
Communication blocks
I/O
CTS
EN
Module name.connector of the Profibus-DP interface
Block enable
(Initialization
connection)
(Default: 1)
The block is not processed if EN=0; output OK=0 and YTS=1;
the last value is kept at the other outputs
OK Diagnostics data valid (Default: 0)
DG1
Overview of which slave signaled diagnostics data. This output is
(Default: 0)
bit-coded. Every bit is assigned to a slave with its Profibus
address.
Bit 3 of the 32 bit is, for example, assigned to the slave with
Profibus address 3.
Comment: The bits 0 up to and including 2 are always 0 as the
associated addresses (0 to 2) should be reserved for the DP
master, for a PG and an OP.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
DG2
Overview of which slave had signaled diagnostics data. This
(Default: 0)
output
is bit-coded. Every bit is assigned to a slave with its Profibus
address. The bit 0 of the 32-bit word is, for example, assigned to
the slave with Profibus address 32.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
DG3
Overview of which slave had signaled diagnostics data. This
(Default: 0)
output
is bit-coded. Every bit is assigned to a slave with its Profibus
address. The bit 0 of the 32-bit word is, for example, assigned to
the slave with Profibus address 64.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
DG4
Overview of which slave had signaled diagnostics data. This
(Default: 0)
output
is bit-coded. Every bit is assigned to a slave with its Profibus
address. The bit 0 of the 32-bit word is, for example, assigned to
the slave with Profibus address 96.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
DL1
Overview of with which slave data transfer took place. This output
(Default: 0)
is bit-coded. Every bit is assigned to a slave with its Profibus
address. For example, bit 3 of the 32-bit word is assigned to the
slave with Profibus address 3.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
2-4 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 17
Communication blocks
DL2
Overview of with which slave data transfer took place. This output
is bit-coded. Every bit is assigned to a slave with its Profibus
address. For example, bit 0 of the 32-bit word is assigned to the
slave with Profibus address 32.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
DL3
Overview of with which slave data transfer took place. This output
is bit-coded. Every bit is assigned to a slave with its Profibus
address. For example, bit 0 of the 32-bit word is assigned to the
slave with Profibus address 64.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
DL4
Overview of with which slave data transfer took place. This output
is bit-coded. Every bit is assigned to a slave with its Profibus
address. For example, bit 0 of the 32-bit word is assigned to the
slave with Profibus address 96.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
MST Status of the DP master:
Stop (0x40 ), Clear (0x80) or Operate (0xC0)
ID Master identification number:
(0x8037 for EXM448 as Profibus interface, 0x80EB when
using X3 of the FM458-1)
QTS Block output QTS is used to display whether the block is operating
error-free (QTS = 1) or was de-activated after a communications
error message was entered (QTS = 0).
YTS
Detailed status display:
• YTS=0 Æ o.k.
• YTS=1 Æ Block processing inhibited (EN=0)
For additional values at YTS, refer to: D7-SYS Online Help "Help
events". (Press the F1 button in the CFC and call the topic
"Help on events" under "CFC for D7-SYS".)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
Configuring data
Computation time [µs] FM458-1 DP 42,7
Can be inserted online No
Can be configured in Cyclic tasks
Executed in Initialization mode
Normal mode
Special features This function block may only be configured
once for each PROFIBUS communications
module.
Function Blocks - FM 458-1 DP 2-5
Edition 12.2004
Page 18
Communication blocks
―
―
―
2.2.2 DPSLDG Slave diagnostics, PROFIBUS DP
Symbol
DP module name. connector ―GV CTS OK BO―Diagnostics valid
Number of device-related
Brief description
DPSLDG
Slave address ―I SLA ST1BY―Status 1, standard diagnostics
I LEN ST2BY―Status 2, standard diagnostics
diagnostic bytes
Enable ―BO EN ST3BY―Status 3, standard diagnostics
MPABY―Master Profibus address
IDW―Slave identification number
D01
D59
QTSBO―Block status
YTSW―Status display
1)
normally invisible
Diagnostic bytes v, w, x u. y 1)
DW
Diagnostic bytes v, w, x u. y 1)
DW
The DPSLDG function block provides diagnostics data from a DP slave
to the user program. This diagnostics data correspond, with the exception
of the maximum possible length, to EN 50170. According to this
Standard, the diagnostics data can be a maximum of 244 bytes long. The
function block supports a maximum of 240 bytes
Note
Mode of operation
On the EXM448, there are restrictions regarding the quantity of
diagnostics data. Only diagnostics data (Standard diagnostics data) is
supplied which the function block DIAPRO supplies.
The consistency of the outputs is not ensured. When new diagnostics
data is received, some of the outputs can have "New" information and
some can still have "old" information.
The PROFIBUS-DP interface is selected using connection CTS.
The function block only enters a communications error for errors, which
are detected during initialization. A communications error cannot be
acknowledged and the function block DPSLDG is only used for
diagnostics. This means, that in normal operation, a communications
error is not entered. Only the cause of the error is signaled at output
YTS.
2-6 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 19
Communication blocks
I/O
CTS DP module name, connector of the Profibus DP interface (Initialization connection)
SLA
Diagnostics data required from the slave with the appropriate
station number (3 to 123)
LEN Number of the device-related diagnostic bytes; this means the
diagnostics bytes which extend beyond the Standard diagnostics.
Here, a maximum value of 234 may be set. Whether device-related
diagnostics data is available and, if yes, which significance they
have, should be taken from the user documentation of the relevant
DP slave.
EN Block enable. If EN=0, the block is not processed;
output OK=0 and YTS=1, the last value remains at the other
outputs.
OK Diagnostics data valid (Default: 0)
ST1 Status 1 of the diagnostics according to the Standard (byte 1).
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
ST2 Status 2 of the diagnostics according to the Standard (byte 2).
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
ST3 Status 3 of the diagnostics according to the Standard (byte 3).
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS DP
coupling".
MPA Master Profibus address (byte 4 of the diagnostics according to the
Standard)
ID Identification number of the slave
(bytes 5 and 6 of the diagnosics according to the Standard)
D01
to
D59
Device-related diagnostic bytes; 4 bytes are combined in one
32-bit
word. Bytes 7, 8, 9 and 10 of the diagnostics telegram can be
found
(Initialization connection)
(Default: 3)
(Initialization connection)
(Default: 0, i.e. only
Standard diagnostics, not
device-related diagnostic
bytes)
(Default: 1)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
in D01.
For a more detailed description, refer to the user manual
"FM 458-1 DP", chapter "Configuring", section "PROFIBUS
DP
coupling".
When data is entered at LEN, this has an influence on the
update
of the outputs. For LEN=0, these outputs are not updated.
For LEN=234, D01 up to and including D59 are updated.
Comment:
Bytes 1 to 6 of a diagnostics telegram for PROFIBUS DP
corresponds to the Standard Diagnostics; bytes from 7 onwards
depend on the particular slave (referred to the particular device).
QTS Block output QTS is used to display whether the block is operating
error-free (QTS = 1) or was de-activated after a communications
error message was entered (QTS = 0).
Function Blocks - FM 458-1 DP 2-7
Edition 12.2004
(Default: 0)
Page 20
Communication blocks
YTS Detailed status display:
• YTS=0 Æ o.k.
• YTS=1 Æ Block processing inhibited (EN=0)
• YTS=2 Æ An initialization connection (SLA er LEN) was
changed in cyclic opertion; this change only becomes effective
the next time that the FM458-1 starts
• YTS=3 Æ The block has already been configured once for the
slave addressed via SLA
• YTS=4 Æ The slave, with the address specified at SLA, has not
been configured in the PROFIBUS network.
For additional values at YTS, refer to: D7-SYS Online Help "Help
events". (Press the F1 button in the CFC and call the topic
"Help on events" uncer "CFC for D7-SYS".)
Configuring data
Computation time [µs] FM458-1 DP 29
Can be inserted online No
Can be configured in Cyclic tasks
Executed in Initialization mode
Special features The function block may only be configured
The DPEVT function block (DP event) provides more detailed information
about a Profibus-DP process or diagnostics alarm. The information/data,
provided at the outputs, correspond to the information/data which a
SIMATIC S7 module also has when processing the appropriate alarm
OBs (e.g. OB40, OB55 etc.).
Mode of operation
When an alarm event is output, all of the values at the outputs are
updated.
When the appropriate alarm occurs, the alarm task configured for this
purpose, is started, Within the alarm task, DPEVT reads-out the alarm
information. A new alarm of the same time is only detected again after
the alarm task has been completed.
When a communications error occurs, the cause is also output at output
YTS and the QTS output is set to "0".
Function Blocks - FM 458-1 DP 2-9
Edition 12.2004
Page 22
Communication blocks
I/O
EXT
For EXT=0, only the data/information at outputs Y01
to Y05 is updated.
For EXT=1, in addition, the information/data at outputs Y06 to
Y21 is updated.
OB The number of the appropriate SIMATIC S7 organizational block
(OB) is displayed at this output. In an error-free state, values 40,
55, 56, 57, 82, 83 and 86 are possible here. The actual value
depends on the process alarm configured in the HWConfig for the
particular alarm task.
STA Station address of the slave which had initiated the alarm. Values
of between 1 and 126 are valid values for this address.
SLO Slot of the module which initiated the alarm. Values of between 1
and 244 are valid values for the slot data.
SUB Sub-module of the module which initiated the alarm. Values of
between 1 and 31 are valid values for the sub-module data.
A value of 0 means no sub-module.
SBN Sub-network to which the module, which initiated the alarm, is
connected. Values of between 1 and 255 are valid values for the
sub-network data. The number for the sub-network can be taken
from the properties dialog box in NetPro or HY-Config.
YO1 The first 4 bytes with information about the last alarm event are
available at this output. The actual significance corresponds to
the first byte of the local data of the appropriate S7-OB.
As a whole, the local data comprise 20 bytes; the structuring of
the local data can be taken from the help for the appropriate OB.
YO2 The second 4 bytes with information about the last alarm event
are available at this output.
YO3 The third 4 bytes with information about the last alarm event are
available at this output.
YO4 The fourth 4 bytes with information about the last alarm event are
available at this output.
YO5 The fifth 4 bytes with information about the last alarm event are
available at this output.
Y06
to
Y21
QTS Block output QTS is used to display whether the block is
YTS Detailed status display for additional values at YTS,
You can obtain additional information/data about the alarm, which
goes beyond the local data of the S7-OBs, at these outputs.
The information/data correspond to that which you would obtain if
you would have called the SFB54 "RALRM" within the appropriate
S7-OBs. The outputs are only updated if EXT=1 is set to 1.
Normally, these outputs are switched so that they are invisible,
and, when required, must be first made visible in the CFC, under
the tab "I/O".
operating error-free (QTS = 1) or was de-activated after a
communications error message was entered (QTS = 0).
refer to: D7-SYS Online Help "Help events".
(Press the F1 button in the CFC and call the topic "Help on
events" uncer "CFC for D7-SYS".)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
2-10 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 23
Communication blocks
Configuring data
Computation time [µs] FM458-1 DP 23,6
Can be inserted online No
Can be configured in Alarm tasks
Executed in Initialization mode
Normal mode
Special features
The DPEVT may only be configured in an
alarm
task for which one of the following alarm
causes
is configured in HW-Config:
• Process alarm 1 (OB40)
• DPV1 status alarm (OB55)
• DPV1 update alarm (OB56)
• DPV1 manufacturer-specific alarm (OB57)
• Diagnostics alarm (OB82)
• Withdraw/insert alarm (OB83)
• Failure, subrack alarm (OB86)
If this is not the case, DPEVT signals an
appropriate communications error and stops
processing.
Function Blocks - FM 458-1 DP 2-11
Edition 12.2004
Page 24
Communication blocks
―
2.2.4 DPPEVT Process alarm information, PROFIBUS DP Symbol
Symbol
Brief description
DPPEVT
STAI―Station
SLOI―Slot
SUBI―Sub-module
SBNI―Sub-network
EVCBY―Event classes and IDs
IOFBY―IO flag
INBO―Input module
OUTBO―Output module
MDLW―Logical address
PAD
YYRI―Year
YMOI―Month
YDAI―Day
YHRI―Hour
YMII―Minute
YSEI―Seconds
QTSBO―Block state
YTSW―Status display
OB40_POINT_ADDR
DW
The DPPEV (DP process event) provides more detailed information
about the Profibus DP process alarm (OB40 alarm). Contrary to the
DPEVT, only selected information/data is available, but then, in a
conditioned form.
Mode of operation
When an alarm event is output, all of the values at the outputs are
updated.
For a communications error, the cause is additionally output at YTS and
the QTS output is set to "0".
2-12 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 25
Communication blocks
I/O
STA Station address of the slave which had initiated the alarm. Values
of between 1 to 126 are valid values for this address.
SLO Slot of the module which initiated the alarm. Values of between 1
and 244 are valid values for the slot data.
SUB Sub-module of the module which initiated the alarm. Values of
between 1 and 31 are valid values for the sub-module data.
A value of 0 means no sub-module.
SBN Sub-network to which the module, which initiated the alarm, is
connected. Values of between 1 and 255 are valid values for the
sub-network data. The number for the sub-network can be taken
from the properties dialog box in NetPro or HW-Config.
EVC
This output corresponds to the local data variables
OB40_EV_CLASS of the OB40 for a SIMATIC-S7. A value of
B#16#11(11 hexadecimal) means that the alarm is active.
IOF
This output corresponds to the local data variables
OB40_IO_FLAG of the OB40 for a SIMATIC-S7.
The significance is as follows:
B#16#54 (54 hexadecimal) Æ Input module
B#16#55 (55 hexadecimal) Æ Output module
The (present) possible information is available, in a
conditioned form, at outputs IN and OUT.
IN
OUT OUT=1 Æ Output module had initiated an alarm
MDL This value outputs the logical basis address of the module.
PAD This value supplies additional information about the cause of the
YYR Year
YMO Month
YDA Day
YHR Hour
YMI Minute
YSE Second
QTS Block output QTS is used to display whether the block is
IN=1 Æ Input module has initiated an alarm
IN=0 Æ The alarm was not initiated from an input module
OUT=0 Æ The alarm was not initiated from an output module
The value corresponds to the local data variables
OB40_MDL_ADDR of the OB40 for a SIMATIC-S7.
process alarm. The value corresponds to the local data variables
OB40_POINT_ADDR of the OB40 for a SIMATIC-S7. Additional
information about this is provided in the SIMATIC documentation.
(specifies in which year the alarm was initiated)
(specifies in which month the alarm was initiated)
(specifies on which day the alarm was initiated)
(specifies at which hour the alarm was initiated)
(specifies at which minute the alarm was initiated)
(specifies at which second the alarm was initiated)
operating error-free (QTS = 1) or was de-activated after a
communications error message was entered (QTS = 0).
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
(Default: 0)
Function Blocks - FM 458-1 DP 2-13
Edition 12.2004
Page 26
Communication blocks
YTS Detailed status display; for additional values at YTS,
refer to: D7-SYS Online Help "Help events".
(Press the F1 button in the CFC and call the topic
"Help on events" uncer "CFC for D7-SYS".)
Configuring data
Computation time [µs] FM458-1 DP 23,6
Can be inserted online No
Can be configured in Alarm tasks
Executed in Initialization mode
Normal mode
Special features The DPPEV may only be configured in an
alarm task for which the following alarm
cause is configured in HW-Config
• Process alarm 1 (OB40)
If this is not the case, DPPEV signals an
appropriate communications error and stops
processing.
A new alarm of the same time is only again
detected after the alarm task has been
completed.
(Default: 0)
2-14 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 27
Communication blocks
2.3 FM 458-specific coupling
2.3.1 @CPB P-bus, central coupling block
Symbol
CPU-module-name.PBUS ―GV CTS CDMBO―coupling status
@CPB
QTSBO―block status
Brief description
The central block for the P-bus coupling can only run with an FM 458
application module.
• This function block is responsible for initializing and monitoring the P
bus coupling.
• The function block can only be configured once for each application
module FM 458, as there is only one P-bus coupling for each FM 458.
If a function block is configured a multiple number of times, this is
detected when initializing, and results in an entry in the
communications error field.
• The block may only be configured in the sampling interval
32 ms <= TA <= 256 ms. Otherwise, an entry is made in the
communications error field.
Mode of operation
When initializing the function block, general preparations are made to
enable the coupling. The coupling is only enabled after the standard
mode has been run-through (executed) several times.
After the coupling has been enabled, the central block monitors that
senders and receivers are correctly registered. Further, if required, it reorganizes and updates the block output CDM at each processing cycle.
The function block cannot be used to initialize another P-bus coupling or
monitor this. It can only initialize its own P-bus coupling on which CPU is
configured. An entry is made in the communications error field if another
module name is specified at the CTS input (other than its own).
The CDM block output provides information about the coupling status.
The connection is a 1, if the coupling is enabled for general send/receive
operation. The CDM block output is 0, as long as the coupling is still
being initialized, or is being re-initialized (after a temporary fault).
Function Blocks - FM 458-1 DP 2-15
Edition 12.2004
Page 28
Communication blocks
I/O
CTS The configured name of its own CPU is specified
CDM Specifies the coupling status
QTS Operating status of the function block
at this initialization input.
(faulted = 0, not faulted = 1).
There is an irreparable fault for QTS = 0, for QTS
= 1,
the function block operates error-free.
Configuringdata
Computation time [µs] FM 458-1 DP 16,5
Available online no
Can be configured in Cyclic tasks
Executed in Normal mode
Initialization mode
Special features -
2.3.2 S7RD_P Reading data from a SIMATIC-CPU (P Bus)
Symbol
(default: 0)
(default: 0)
Offs in 128By-PBus-Buffer ―I OFF PTRDW―PtrBuffer Transmitdata
Number bytes to be read ―I LEN QFBO―Error-Status Block
Brief description
Mode of operation
S7RD_P
Enable ―BO EN YFW―StatusInfo Block
This block can only be used for the SIMATIC application module FM 4581 DP.
A SIMATIC-CPU can transfer up to 128 bytes to the FM 458-1 DP in its
output area of the P bus. Block S7RD_P reads this data from the P-Bus
and provides it, via its pointer interface, to the read blocks (DRD…,
CPY_Y) for further processing in the CFC configured software.
This block operates similar to the telegram block CRV_P. A maximum of
128 bytes can be accessed via the pointer interface. These bytes are
sent from the SIMATIC-CPU to the FM 458-1 DP via the P bus.
Data can be read using the read blocks (DRD…) or the copy block
(CPY_P).
This block only communicates with a SIMATIC-CPU. This means that the
required byte or word swap operations are automatically made
(depending on the data type of the connected read/write blocks). The
entry, which is normally required at the SW-connection of the read/write
block, is not evaluated and is therefore not required.
2-16 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 29
Communication blocks
The computation time essentially depends on the amount of data
transferred. A base computation time of approx. 10 µs as well as approx.
1 µs/byte can be assumed as nominal value.
Associated blocks
The following blocks can be connected to this block (pointer input):
DRD, DRD_8, DRD_8D, DRD_8I, DRD_BY, DRD_D, DRD_I, CPY_P
I/O
OFF Offs in 128By-PBus-Buffer
Offset of the value to be sent within the 128 byte memory relative to the start of
the buffer; max. offset: Buffer length - length of the data type
LEN
EN
PTR PtrBuffer Transmitdata
QF
YF
Number bytes to be read
Number of bytes which are read by the SIMATIC-CPU via the P bus.
Max. number: 128 bytes
Enable
For EN=1 at each call, the data sent from the SIMATIC-CPU (max. 128 bytes)
is read.
Pointer to the telegram data buffer; to connect with the same connection type
of other pointer-based communication blocks. The CFC connection can be
changed online.
The connection also includes monitoring information to ensure correct
configuring.
Error status block
QF=1: There is an error; for details, refer to YF
StatusInfo Block
§§ as for the DRD block!
Default:
0
0
1
16#00000000
0.0
16#0000
Configuring data
Computation time [µs] FM 458-1 DP 10,0 + 1 for each byte
Can be inserted online Yes
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
The block must be configured in the same
sampling time
as the blocks, connected via the pointer interface
(CFC connection via connections PTR). This can
only be used for the FM 458-1 DP!
Several S7RD_P blocks can be configured.
Although this is not a typical application, it can
make sense if, for example, the 128 byte area
should be read in several blocks or if data is
required in different sampling times.
Function Blocks - FM 458-1 DP 2-17
Edition 12.2004
Page 30
Communication blocks
2.3.3 S7WR_P Sending data to a SIMATIC-CPU (P Bus)
Symbol
Offs in 128By-PBus-Buffer ―I OFF PTRDW―PtrBuffer Transmitdata
Number bytes to be write ―I LEN QFBO―Error-Status Block
Number bytes to be write ―BO EN YFW―StatusInfo Block
Brief description
Mode of operation
S7WR_P
This block can only be used for the SIMATIC application module FM 4581 DP.
An FM 458-1 DP can send up to 128 bytes to the SIMATIC-CPU via the
P-Bus. The block S7WR_P sends data which were previously loaded
with write blocks via the pointer interface.
This block operates similar to the telegram block CTV_P. A maximum of
128 bytes can be transferred via this pointer interface and via the P bus
to the SIMATIC CPU. This data is previously loaded into the telegram
buffer using write blocks DWR… of the copy block CPY_Y.
This block only communicates with a SIMATIC-CPU. This means that the
required byte or word swap operations are automatically made
(depending on the data type of the connected read/write blocks). The
entry, which is normally required at the SW-connection of the read/write
block, is not evaluated and is therefore not required.
The computation time essentially depends on the amount of data
transferred. A base computation time of approx. 5 µs as well as approx.
0.7 µs/byte can be assumed as nominal value.
Associated blocks
The following blocks can be connected to this block (pointer input):
DWR, DWR_8, DWR_8D, DWR_8I, DWD_BY, DWR_D, DWR_I, CPY_P
I/O
OFF Offs in 128By-PBus-Buffer
Offset of the value to be sent within the 128 byte memory relative
to the start of the buffer;
max. offset: Buffer length - length of the data type
LEN
EN Enable
PTR PtrBuffer Transmitdata
Number of bytes to be written
Number of bytes which are to be sent to the SIMATIC CPU via the P bus.
Max. number: 128 bytes
For EN=1, at each call, the telegram buffer (max. 128 bytes) is sent to
the SIMATIC-CPU.
Pointer to the telegram/data buffer; to connect with the same connection
type of other pointer-based communication blocks.
The CFC connection can be changed online.
The connection also includes monitoring information to ensure correct
configuring.
Default:
0
0
1
16#00000000
2-18 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 31
Communication blocks
QF Error status block
QF=1: There is an error; for details, refer to YF
YF
StatusInfo Block
§§ as for the DRD block!
Configuring data
0.0
16#0000
Computation time [µs] FM 458-1 DP 5,0 + 0.7 for each byte
Can be inserted online Yes
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
The block must be configured in the same
sampling time
as the blocks, connected via the pointer interface
(CFC connection via connections PTR).
This can only be used for the FM 458-1 DP!
Several S7WR_P blocks can be configured.
Although this is not a typical application, it can
make sense if, for example, the 128 byte area
should be written in several blocks or if data is
required in different sampling times.
Function Blocks - FM 458-1 DP 2-19
Edition 12.2004
Page 32
Communication blocks
V
2.3.4 BRCV Block-oriented data reception via an S7 coupling
Symbol
Establish ready to receive ―BO ENR PTRDW―Receive data is ready
Addressing parameters ID ―W ID NDRBO―Status parameter NDR
Addressing parameters R_ID ―DW RID LENDI―Length of data received before
Maximum length, receive data ―DI RLN CTR DI―Number of receive operations
BRC
ERRBO―Status parameter ERROR
STAW―Status, fault display
QTSBO―Block status
YTSW―Status display
Brief description
The function block allows block-oriented data reception via a configured
S7 coupling.
Mode of operation
The BRCV block receives data from a "remote" partner. The "remote"
partner is an SFB/FB, type BSEND (SFB/FB 12) on a SIMATIC S7-400
CPU.
After each data segment which has been received, an acknowledgement
is sent to the partner SFB/FB and the LEN parameter is updated.
The block is ready to receive when a "1" is connected to the control input
ENR. A running task can be interrupted with ENR=0.
The maximum length of the receive area is specified by the data at input
RLN. The length of the data block received is displayed at output LEN.
I/O
ENR Control parameter
The block is ready to receive with ENR = 1
ID Addressing parameter
Reference to the local connection description
(this is specified as a result of the STEP7 configured connection)
RID The value at input RID specifies the association with the send SFB/FB.
The value at the input must match the R_ID parameter for SFB/FB on
the
send side. This allows several SFB/FB pairs to communicate via the
same logical coupling. The block pairs of a logical coupling, defined
using
RID or R_ID must be unique for this coupling.
RLN The maximum length of the received data is defined here.
Only values of between 0 and 65535 may be configured.
PTR The receive data, to be evaluated by the blocks for direct
communication,
is made available here (e.g. types DRD, DRD_I, etc.).
Default: 0
Initialization input,
Default: 0
Initialization input,
Default: 0
Initialization input,
Default: 0
Default: 0
2-20 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 33
Communication blocks
NDR Status parameter NDR
0: Task was still not started (ENR input)or is still running
1: Task was successfully completed
LEN Length of the previously received data in bytes Default: 0
CTR This output counts the total number of successfully complete data
receive
cycles since the last change from STOP to RUN.
ERR An error is output at block output ERR. The detailed information about
the
type of the error is available at output STA.
This output corresponds to the ERROR output of an SFB/FB 13
of an S7-CPU.
STA Detailed status display
This output corresponds to the STATUS output of an SFB/FB 13 of an
S7-CPU.
ERR = 0:
• STA=00H
• STA=11H
ERR = 1:
• STA=01H
• STA=04H
• STA=05H
• STA=12H
• STA=14H
QTS Block output QTS indicates whether the block is operating (QTS = 1) or
became inactive after a communications error message was entered
(QTS = 0).
YTS Detailed status display
• YTS=0 Æ O.K. (ready)
• YTS=1
• YTS=2
For other values at YTS, in addition, a communications error is entered
in
the diagnostics buffer and the block is no longer processed (QTS=0)
No alarm, no fault
Non-synchronous data is received, output LEN indicates the number
of pieces of data previously received in bytes.
Communication problems
(e.g. the coupling description to the ID not loaded, coupling has still
not been established from the partner or the coupling was
interrupted)
Error regarding the data length
The data block sent is longer than the receive range set using input
RLN.
Reset request received, incomplete transfer
R_ID already exists in the coupling
too little working memory
The block is in the DISABLED state, i.e. ENR=0
The initialization connection is changed, the change only becomes
effective at the next STOP Æ RUN transition; the FB operates with
the values at ID, RID and RLN set when running-up
Default: 0
Default: 0
Default: 0
Default: 0
Default: 0
Default: 0
Function Blocks - FM 458-1 DP 2-21
Edition 12.2004
Page 34
Communication blocks
Configuring data
Computation time [µs] FM458-1 DP 5,7
Can be inserted online No
Can be configured in Alarm tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
2-22 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 35
Communication blocks
2.3.5 S7STAT S7 CPU operating state
Symbol
Brief description
Mode of operation
Output value
to ACT or OLD
0x0010 Stop 0 1 0
0x0020 Cold start 0 0 0
0x0040 New start 0 0 0
0x0080 Re-start 0 0 0
0x0100 RUN 1 0 0
0x0200 RUN-R 1 0 0
0x0400 Hold 0 0 1
S7STAT
RUNBO―S7-CPU in RUN
STPBO―S7-CPU in STOP
HLDBO―S7-CPU in HOLD
ACTW―actual operating state
OLDW―previous operating state
The actual and previous S7-CPU operating states are displayed at the
outputs.
The actual and previous operating state of the S7-CPU is determined and
displayed at connectors ACT for the actual and OLD for the previous
operating state. Output RUN is set to TRUE if the S7-CPU is either in the
RUN or RUN-R state.
Operating state RUN STP HLD
NOTE
All other values are used for extended diagnostics.
I/O
RUN S7-CPU in RUN (Default: 0)
STP S7-CPU in STOP (Default: 0)
HLD S7-CPU in HOLD (Default: 0)
ACT Actual operating state of the S7-CPU (Default: 0x8000)
OLD Previous operating state of the S7-CPU (Default: 0x8000)
Please refer to the help for STEP7 for a more detailed description of the
operating states.
Function Blocks - FM 458-1 DP 2-23
Edition 12.2004
Page 36
Communication blocks
Configuring data
Commutation time [µs] FM458-1 DP
Can be inserted online yes
Can be configured in Alarm tasks
Cyclic tasks
Executed in Normal mode
Special features -
2-24 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 37
Communication blocks
2.3.6 S7RD, S7RD_B, S7RD_I, S7RD_D Read from the peripheral area of the
S7-CPU
Symbol
S7RD
Offset ―I OFF YR―Output
Enable ―BO EN QF BO―error output
Brief description
The function blocks, read from the peripheral area of the S7-CPU, can
only run with an FM 458 application module.
The S7RD, S7RD_B, S7RD_I, S7RD_D blocks only differ by the data
type at the output, which must correspond with the parameters to be
read:
• S7RD: REAL
• S7RD_B: BOOL
• S7RD_I: INT
• S7RD_D: DINT
Mode of operation
With this block, data can be read into the assigned net data area of the
SIMATIC S7-CPU, (periphery output) assigned to the FM 458 application
module. This PE area is 128 bytes.
If the enable signal is set, the appropriate value is read from the PA area
and made available at output Y.
The offset determines at which location in the PA area, the value is
retrieved.
Depending on the block- or data type, the offset is specified as follows:
• for REAL data type in 4-byte steps (data length)
value range of the offset: 0 . . . 31
• for BOOL data type in 1-byte steps (data length).
value range of the offset: 0 . . . 127
• for INT data type in 2-byte steps (data length).
value range of the offset: 0 . . . 63
• for DINT data type in 4-byte steps (data length).
value range of the offset: 0 . . . 31
Output QF has the value 1, if an invalid offset was selected, or the block
is not configured on the FM 458.
Function Blocks - FM 458-1 DP 2-25
Edition 12.2004
Page 38
Communication blocks
I/O
Configuringdata
OFF
EN
Y
QF
Offset (default: 0)
Enable (default: 0)
Output (default: 0.0)
Error output (default: 0)
Computation time [µs] FM 458-1 DP 3,3
Available online yes
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Normal mode
Initialization mode
Special features -
2-26 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 39
Communication blocks
2.3.7 S7WR, S7WR_B, S7WR_I, S7WR_D Write into the peripheral area of
the S7-CPU
Symbol
S7WR
Input ―R X QFBO―Error output
Offset ―I OFF
Enable ―BO EN
Brief description
The function blocks, write the peripheral area (I/O) of the S7-CPU can
only run with one FM 458 application module.
The S7WR, S7WR_B, S7WR_I, S7WR_D blocks differ by the data type
at the input, which must correspond with the parameters to be written:
• S7WR: REAL
• S7WR_B: BOOL
• S7WR_I: INT
• S7WR_D: DINT
Mode of operation
Using this block, data can be written into the net (useful) data area of the
SIMATIC S7-CPU, assigned to the FM 458 application module (periphery
input). This PE area is 128 bytes. If the enable signal is set, the input
value is accepted via the input and entered in the PE area.
I/O
The offset determines at which position in the PE area, the input value is
saved. Depending on the block- or data type, the offset is specified as
follows:
• for REAL data type in 4 byte steps (data length).
value range of the offset: 0 . . . 31
• for BOOL data type in 1 byte steps (data length).
value range of the offset: 0 . . . 127
• for INT data type in 2 byte steps (data length).
value range of the offset: 0 . . . 63
• for DINT data type in 4 byte steps (data length).
value range of the offset: 0 . . . 31
Output QF has the value 1, if an invalid offset was selected, or the block
is not configured on the FM 458 application module.
X Input (default: 0.0)
OFF Offset (default: 0)
EN Enable (default: 0)
QF Error output (default: 0)
Function Blocks - FM 458-1 DP 2-27
Edition 12.2004
Page 40
Communication blocks
Configuringdata
Computation time [µs] FM 458-1 DP 3,3
Available online yes
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Normal mode
Initialization mode
Special features -
2-28 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 41
Communication blocks
2.4 Parameterizing SIMADYN D
2.4.1 @FMPAR Parameter processing on FM 458-1 DP modules
Symbol
EXM448 module name. connector ―GV CTS CS BO―COMBOARD status
Parameter language selection ―I PLA QTSBO―Block status
Parameter type float to Comboard ―BO CF YT1W―Status 1.COMBOARD parameter channel
The FB @FMPAR can only be configured on a FM 458-1 DP module.
FB @FMPAR monitors the COMBOARD (communications submodule of
the SIMOVERT MASTER DRIVES, e.g. CBP for PROFIBUS DP) and
processes the parameter tasks which are defined for it.
Several @FMPAR central blocks for various COMBOARDs can be
configured on a FM 458-1 DP module.
It should be configured in a slow sampling time (approx. 100 ms). The
maximum permissible sampling time is 200 ms (as a result of the
monitoring using adjacent modules).
The existence and correction functioning of the COMBOARD is
automatically identified and is displayed at output CS.
Mode of operation
Only one COMBOARD may be configured using FB @FMPAR.
Parameter processing:
Parameters are configured in the comment at each I/O. If the comment
starts with "@TP_", then this I/O is designated as parameter. Every
parameter can be allocated a parameter name (FB-PNAME). Further, a
setting parameter can also be allocated a minimum and a maximum (FBPLIM).
The block handles the following tasks:
• Checks the module code of the COMBOARD
• Monitors the COMBOARD (lifebit counter)
• Transfers the configuration data to the COMBOARD
• Processes the parameter channels
• In standard operation, processes the parameter tasks (in the
sampling time cycle).
Function Blocks - FM 458-1 DP 2-29
Edition 12.2004
Page 42
Communication blocks
The name of the COMBOARD which is to be processed, is configured at
input CTS of the FB @FMPAR. If a name has not be configured at input
CTS, then the FB @FMPAR shuts itself down with an error signal at
output YT1/2.
NOTE
Function blocks CRV and CTV may only be configured once. They can
be configured on any and on different processor modules. However,
parameter processing is possible for all processor modules.
Initialization I/O:
CTS Configured name of the EXM448 coupling module and connector X02, separated by ".".
(Default: - )
CF Parameter data type to transfer SIMADYN D data types REAL and
SDTIME via the parameter channel of the COMBOARD:
• CF=1: Parameter data type, float
• CF=0: 32-bit integer "I4"
(Default: 1)
PLA Parameter language selection (parameter language):
The parameter names are activated, which are configured at all PNAME
function blocks, whose PLA input has the same value
(Default: 0)
Inputs:
PEN Enables the parameter change:
• PEN=1: allows the operator control parameters to be changed through all of the
• PEN=0: inhibits operator control parameter changes via all parameter channels
(Default: 1)
BBF BASEBOARD-Function
• BBF=0: SIMATIC FM 458-1 DP operates as TECHBOARD (parameter number from
• BBF=1: SIMATIC FM 458-1 DP operates as BASEBOARD (parameter number from
(Default: 0)
parameter channels
external view 1000..1999, 3000..3999)
external view 0..999, 2000..2999)
Status outputs:
CS COMBOARD status:
• CS=1, COMBOARD is operational.
• CS=0, COMBOARD has failed or is not available.
(Default: 0)
2-30 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 43
Communication blocks
Diagnose outputs:
QTS Block status:
• QTS=1: Block is operational and is operating error-free.
• QTS=0: Block is shutdown due to a fault with an error output at YT1/2
(Default: 0)
YT1
YT2
• YT1=0: OK status
• Initialization mode: status of the block initialization
• Standard mode: Status of the 1
For additional values, refer to: D7-SYS online help "Help on Events". (press
the F1 key in the CFC and call-up the topic "Help on events"
under "CFC for D7-SYS".)
(Default: 0)
• YT2=0: OK status
• Intialization module: Status of the block initialization
• Standard mode: Status of the 2
For additional values, refer to: D7-SYS online help "Help on events". (press key F1 in the
CFC and call-up the topic "Help on events"
under "CFC for D7-SYS".)
(Default: 0)
st
parameter channel from COMBOARD
nd
parameter channel of COMBOARD
Configuringdata
Computation time [µs] FM 458-1 DP 3,3
Can be inserted online --
Can be configured in Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
• 10<=sampling time<=200 ms
• Block may not be switched-in or
switched-out per task group.
Function Blocks - FM 458-1 DP 2-31
Edition 12.2004
Page 44
Communication blocks
2.4.2 CBCONF COMBOARD configuration
Symbol
CBCONF
name of the module to the right ―GV CTR QTS BO―block status
new configuration command ―BO SET YTSW―status display
FB CBCONF can be configured on the following modules:
• FM458 modules
• T400 technology module
Configuring on a
FM458 module
The function block CBCONF may only be configured once on a FM458
module per COMBOARD. It is configured on the FM458 module on
which the function block @FMPAR was configured for the appropriate
COMBOARD.
2-32 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 45
Communication blocks
Mode of operation
The block saves the configured configuration data in the admin. area of
the COMBOARD. It executes this once after run-up and user-controlled
in the RUN mode. In the RUN mode, it outputs diagnostics data from the
COMBOARD at its outputs.
New configuration data can be transferred online to COMBOARD with a
positive edge at input SET.
I/O
CTR Configured name of the "righthand" adjacent module (initialization connection). The
following data can be entered:
• CTR = 0 if an adjacent module was not configured
• CTR=<module name> or
• CTR=<module name>.<connector> if an adjacent board is configured.
(default value: - )
SET The configuration data is transferred online to the COMBOARD with a rising
edge at this input.
(Default value: 0)
MAA The station number should be assigned depending on the particular protocol
• QTS = 0: The block is disabled with an error output at YTS
(Default value: 0)
YTS Status display, possible values
• - 0: OK status
• - 7CB3: T400 operates as TECHBOARD and a BASEBOARD is available
Additional values, refer to: D7-SYS Online Help "Help on events" (press key F1 in the CFC
and call-up the topic "Help on events" under "CFC for SIMADYN D".)
(Default value: 0)
D01...D28 Max. 28 words of diagnostics data of the COMBOARD
(Default value: 0)
Function Blocks - FM 458-1 DP 2-33
Edition 12.2004
Page 46
Communication blocks
Significance of the
configuring input
for several
COMBOARDs
Input CB-Param
new/old
MAA
P01
P02
P03
P04
P05
P06
P07
P08
P09
P10
P11
P12
P13
P14
...
P28
P918 Bus address Bus address Bus address Bus address Bus address
P711/
P696
P712/
P697
P713/
P698
P714/
P699
P715/
P700
P716/
P701
P717/
P702
P718/
P703
P719/
P704
P720/
P705
P706.1 (END) CAN layer
P706.2 Bus timing
P706.3 (END)
P706.4
The "CB-Param" and "SCB-Param" columns establish the assignment to
the COMBOARD User Manuals.
CB1:
DP
(not used) Diagnostic
PPO-Typ PPO-Typ PPO-Typ - PZD
(END) (END) Protocol selection:
SIMATIC OP
Slave to slave
(END) - PZD
- PZD
Baud rate
PKW: 0:no,
PZD:
CBP:
DP
selection
CBP2:
DP
Diagnostic
selection
0: Profibus-DP
2: USS
writes in:
0: EEPROM
1. RAM
data transfer
failed:
0: Error
1: Warning
CBP2:
USS
- PKW task
- PZD
- PZD
6 = 9,6
kBaud
7 = 19,2
kBaud
8 = 38,4
kBaud
127:yes,
3:one word,
4:one D word
No. of words
CB2:
CAN
receive
PZD send
send length
send rate
receive
Broadcast
receive
Multicast
PZD
receiver
cross
PKW task
Broadcast
Baud rate
2-34 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 47
Communication blocks
Input SCB-
Param
MAA
P01
P02
P03
P04
P05
P06
P07
P08
P09
P10
P11
P12
P13
P14
...
P28
P683.2 Bus address (not used)
P682 SCB1/SCB2-protocol selection:
P685.2 PKW: 0:no,
P686.2 Process data:
P684.2 Baud rate
P687.2 Telegram failure time
(END) (END)
SCB2:
USS-Slave
0:CAN, 1:USS 4-wire,
2:USS-2-wire, 3:Peer
127:yes,
3:one word,
4:one D word
No. of words
SCB2:
Peer
(not used)
(not used)
SCB1:
CAN
Significance of the
diagnostic outputs
Configuringdata
Refer to the COMBOARD User Manuals
Computation time [µs] FM458-1 DP 3,3
Can be inserted online --
Can be configured in Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
• The block can only be configured once for
each communications submodule.
• Additional block required on the CPU
modules: @FMPAR
Function Blocks - FM 458-1 DP 2-35
Edition 12.2004
• The block can only be configured on a FM458 module.
• This block receives warnings A81 to A96 of a COMBOARD
(communications submodule of SIMOVERT MASTER DRIVES, e.g.
CBP2 for PROFIBUS DP).
• Input CTS of the CBRFAW function block is used to define from which
COMBOARD the warnings are to be received.
• Function block CBRFAW may only be configured on a FM458 module
of each COMBOARD. It is configured on the FM458 module, on which
a @FMPAR function block was also configured for the appropriate
COMBOARD.
I/O
Initialization inputs:
CTS Configured name of the EXM448/EXM448-2 module and connector X01 or X02, separated by
".".
(Default: - )
Outputs:
CW Outputs COMBOARD warnings A81 to A96
(Default: 0)
QTS Block status:
• QTS=1: Block is being processed and is operating error-free.
• QTS=0: Block is shut down due to a fault with error output at YTS.
(Default: 0)
YTS Status of the COMBOARD warning channel:
YTS=0: OK condition
For additional values, refer to: D7-SYS online help "Help on events". (press the F1 key in the
CFC and call-up the topic "Help on events" under "CFC for SIMADYN D".)
(Default: 0)
2-36 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 49
Communication blocks
Configuringdata
Computation time [µs] FM458-1 DP 3,3
Can be inserted online --
Can be configured in Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
• The block can only be configured once for
each communications submodule.
• Additionally required block:
@FMPAR
Function Blocks - FM 458-1 DP 2-37
Edition 12.2004
Page 50
Communication blocks
2.4.4 PNAME Parameter names
Symbol
parameter language selection ―I PLA YTSW―status output
parameter name 1 ―S N1
parameter name 2 ―S N2
parameter name 3 ―S N3
parameter name 4 ―S N4
parameter name 5 ―S N5
parameter name 6 ―S N6
parameter name 7 ―S N7
parameter name 8 ―S N8
parameter name 9 ―S N9
parameter name 10 ―S N10
parameter name 11 ―S N11
parameter name 12 ―S N12
parameter name 13 ―S N13
parameter name 14 ―S N14
parameter name 15 ―S N15
parameter name 16 ―S N16
parameter name 17 ―S N17
parameter name 18 ―S N18
parameter name 19 ―S N19
parameter name 20 ―S N20
PNAME
Brief description
Mode of operation
The block is required to configure names for parameters.
The PNAME function block can be configured on the following modules:
• T400 technology module (@DRIVE function block is required)
• FM module
(@FMPAR function block is required)
The block can be configured in the slowest sampling time.
The block saves the configured names in the parameter list of the
function block @FMPAR, and then disables itself.
2-38 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 51
Communication blocks
I/O
PLA Parameter language selection (parameter langage): The configured parameter names are
exactly activated when the data coincides with the PLA input at the @FMPAR block.
(Initialization input)
(Default value: 0)
Nnn The parameter number and the parameter name, separated by a colon are specified
at the Nnn inputs. Example: "H123: parameter name". The parameter number must
always consists of a letter (H or L) and three digits. The parameter name should be
a maximum of 16 characters long; longer names will be cut-off and shorter names,
filled with blanks. .
- 0: OK status (all of the names are activated).
Alarms:
- 1: The names are not activated, as another language is set at function block @FMPAR
- 2: For at least one parameter number, there is no parameter (the name is ignored)
Additional values, refer to: D7-SYS Online Help "Help on events" (press key F1 in the CFC
and call-up the topic "Help on events" under "CFC for SIMADYN D")
(Default value: 0)
Configuringdata
Computation time [µs] FM 458-1 DP 3,3
Can be inserted online --
Can be configured in Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
• additionally required block on the FM
modules: @FMPAR
Function Blocks - FM 458-1 DP 2-39
Edition 12.2004
Using the function block, the following can be realized
• a current device status can be configured,
• the access level can be defined by entering a password,
• the device status and the access level is used to define whether a
parameter may be changed.
The statuses and access level, in which a parameter is to be inhibited or
enabled, are defined using the PLIM function block.
Function block PSTAT may only be configured once in each FM module.
I/O
PSW
PWi Appropriate password for access level i (password i):
STE Actual "device status": There are 16 statuses.
Current password:
If password PSW does not coincide with the PWi values, then this corresponds to access level
0: this does not permit any change.
If password PSW coincides with a value of PWi, then this corresponds to access level i and all
lower access levels.
In access level 8, there are no access authorizations as a result of the access level (all other
access restrictuions, e.g. using the device status, are retained).
(Default: 0)
(Default: 0)
Permissible entry range: 1 to 16
(Default: 1)
2-40 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 53
Communication blocks
WLV Actual access stage i (word level):
The access stage i, determined by the entry at input PSW, is output as binary value. For access
stage n, bit n is set to 1 and all of the other 15 bits, are set to 0.
e.g. for access level = 7, WLVcorresponds to 2#0000000001000000.
(Default: 2#0000000000000000)
WST Device status (word state):
The actual device status STE is output as a binary value. For the current device status ST=n, bit
n is set to 1 and all of the other 15 bits are set to 0.
e.g. for STE=7, WST corresponds to 2#000000001000000.
(Default: 2#0000000000000001)
YTS Status display:
• 7C72: Function block is configured several times
• 7CA9: no @FMPAR function block configured
• 7CC3: one or several incorrect entries were made at input PWi
• 7CC4: illegal entry at input STE
(Default: 0)
For additional values, refer to: D7-SYS online help "Help on events". (press
key F1 in the CFC and call-up the topic "Help on events" under
"CFC for SIMADYN D".)
Configuringdata
Computation time [µs] FM 458-1 DP 3,3
Can be inserted online --
Can be configured in Alarm-Tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features
• Function block may only be configured once
per FM module
• Function block additionally required on the
FM modules:
@FMPAR and PLIM
Function Blocks - FM 458-1 DP 2-41
Edition 12.2004
Page 54
3 Logic blocks
3.1 SAV_TR Save FB for NOV_RAM
Symbol
SAV_TR
input variable―RXYR―output variable
mode of operation―BOMQFBO―no available memory
Brief description
Mode of operation
Write operating
mode (M = 1)
Read operating
mode (M = 0)
INIT Operating
mode
A REAL type quantity is saved in the NOV-RAM of a technology module.
The function block is a read/write memory for a REAL value. It is only
active, if a 0 at output QF indicates that the memory space in the
NOVRAM is available. The function block operating mode is selected at
input M:
• The quantity to be saved is entered at input X. It is transferred to
output Y.
• Further, input quantity X is entered in the NOV-RAM of the module. In
this case, a value, already contained in the NOV-RAM is overwritten.
• The last input quantity, saved in the write operating mode, is output
at Y.
• The NOV-RAM is deleted from the operating system each time the
configured software changes (even when the system is configured for
the first time), i.e. zeros are written into it. If the NOV-RAM is then
read, without having previously written a value into the NOV RAM,
then the initialization value of the NOV RAM (zero) is output at Y.
In the INIT operating mode of the function block, memory is made
available to accept a REAL value. Output QF is set to 1 if this is not (no
longer) possible. The function block is then inactive in the RUN operating
mode.
This function block, which initiates a process interrupt to the SIMATIC
S7-CPU, can only run with an FM 458-1 DP application module.
The function block initiates a process interrupt at the associated S7 CPU.
The IFO double word is transferred to the S7-CPU as supplementary
interrupt information.
A process interrupt is only acknowledged after the process interrupt
OBs (organization block) has been executed on the S7-CPU.
The block does not wait for the acknowledgment. The OB is
parameterized in the HWConfig for the associated S7-CPU.
The process interrupt is only initiated, if the S7-CPU is not processing a
process interrupt from the FM 458-1 DP application module.
Output QF has the value 1, if a new process interrupt is initiated,
although the last process interrupt was still not acknowledged or the
block was not configured on FM 458-1 DP.
Output QF has the value 0, if the acknowledgment from the S7-CPU has
been received, or if input RES has the value 1.
The interrupt is initiated as a function of the input TMB:
• for TMB = 0, if a signal changes from 0 to 1 at input I, or.
• for TMB = 1, if any signal transition occurs at input I.
I/O
Configuringdata
IFO
RES
TMB
I
QF
Computation time [µs]FM 458-1 DP 3,3
Supplementary interrupt information(default: 0)
Reset error(default: 0)
Trigger mode, both edges(default: 0)
Initiate an interrupt(default: 0)
Error output(default: 0)
Available onlineno
Can be configured inInterrupt tasks
Cyclic tasks
Executed inNormal mode
Special features-
Function Blocks - FM 458-1 DP3-3
Edition 03.2003
Page 57
4 Service-/diagnostic blocks
4.1 FMLED Control FM 458-1 DP diagnostics LED
Symbol
FMLED
LED (user error)―IAWF QFBO―error output
LED (online monitoring)―IONL
LED (communications error)―ICOM
LED (sampling time overflow)―ICYC
Brief description
Mode of operation
I/O
Configuringdata
The function block, which controls the FM 458-1 DP diagnostic LEDs,
can only run with an FM 458-1 DP application module.
The LEDs of the FM 458-1 DP application module can be controlled
using this block.
The LED display is canceled for a value of 0 at the appropriate input; for
a value of 1, it is set and for a value of -1, its status is retained,
unchanged. The value of -1 is required, as this block has been configured
a multiple number of times.
Output QF has the value 1, if the inputs have invalid values, or if the
block is not configured on the FM 458-1 DP application module.
AWFLED for user error(default: -1)
ONLLED for online monitoring(default: -1)
COMLED for communications error(default: -1)
CYCLED for sampling time overflow(default: -1)
QFError output(default: 0)
Computation time [µs]
Available online
Can be configured inInterrupt tasks
Executed inNormal mode
Special features-
FM 458-1 DP1,0
yes
Cyclic tasks
Initialization mode
Function Blocks - FM 458-1 DP4-1
Edition 03.2003
Page 58
5 SIMOLINK drive coupling
5.1 @SL SIMOLINK central block
Symbol
Hardware address SLB ―GV TAD YFI―Error status of the block
Filling-up the telegram gaps ―BO FIL NTODI― No. of timeouts
Enable the drive interface ―BO EN CO1DI―No. of waiting cycles
@SL
Operating mode ―I MOD NCP I―No. of nodes
Node address ―I ASL NCYDI―No. of cycles
Send power ―I POW NORDI―No. of overruns
Use PCI Copy ―BO DM NCRDI―No. of CRC errors
Max. blocksize ―I NSL NDMDI―No. of the defective module
CO2DI―No. of CO1 overruns
QFBO―Group error bit
Brief description
The @SL central block allows the initialization and monitoring of
communications with an SLB module.
An SLB module is a system hardware component, which can be an ITSL, an EXM 448-1 module or an optional SLB (SIMOLINK Board) of the
ITSL module.
The @SL central block may only be configured in a cyclic task and once
per SIMOLINK ring.
The following parameters must be set for an SLB module:
• Hardware address SLB (TAD)
• Operating mode (MOD)
• Node address (ASL), only relevant when operating mode 0 is selected
• Send power (POW) for the SLB module
Mode of operation
1. The @SL central block executes the following steps while the system
is being initialized:
− Checks the validity of the value ranges at the input connections
− Checks whether additional @SL central blocks have been
configured at the same hardware address (input TAD)
− Initializes the SLB module corresponding to the data at the
initialization connections
Function Blocks - FM 458-1 DP 5-1
Edition 12.2004
Page 59
SIMOLINK drive coupling
− Sends an initialization sequence (SIMOLINK) and monitors the
starting sequence
2. The @SL central block executes, in the standard mode ("RUN“
operating status) of the system, the following operating steps:
− Monitors communications of the SIMOLINK drive interface
− Outputs fault messages when communication faults occur at the
outputs
− Outputs information about the drive coupling
− New values for the node address (ASL) and send power (POW)
are only transferred after the SIMOLINK drive coupling restarts.
Operating mode
0 Slave mode
The SLB module operates as slave. The SIMOLINK blocks in the CFC chart must be configured
in an interrupt task Ix (x=1 . . . 8).
Timing: an interrupt is initiated each time a SYNC telegram is received, and therefore starts
execution of interrupt task Ix. The received values are read and the values to be sent are written
into the write buffer of the SLB module.
Processing time of the
SIMOLINK blocks
1 Asynchronous mode
The SLB module operates as master. The SIMOLINK blocks in the CFC chart must be
configured in a cyclic task Tx (x=1 . . . 5).
Timing: The blocks are executed each time cyclic task Tx starts. The SIMOLINK telegrams are
sent after the last SIMOLINK block has been calculated.
Processing time of the
SIMOLINK blocks
An SLB module can be initialized and can operate in 6 different operating
modes.
When configuring, the different time characteristics of the SIMOLINK
blocks for the selected operating modes at input MOD.
SYNC telegramSYNC telegramSYNC telegram
SIMOLINK cycle
Cyclic task Tx
Processing ti me of the
SIMOLINK blocks
SIMOLINK cycleSIMOLINK cycle
SIMOLINK cycle
Interrupt task Ix
Processing time of the
SIMOLINK blocks
Processing ti me of the
SIMOLINK blocks
5-2 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 60
SIMOLINK drive coupling
2 Timer mode
The SLB module operates as master. The SIMOLINK blocks in the CFC chart must be
configured in an interrupt task Ix (x=1 . . . 8).
Timing: A timer of the ITSL/EXM 448-1 module initiates, corresponding to the equivalent
sampling time, an interrupt, and therefore execution of interrupt task Ix. The SIMOLINK
telegrams are sent after the last SIMOLINK block has been calculated.
Timer interrupt
SIMOLINK cycleSIMOLINK cycle
Processing time of the
SIMOLINK blocks
Interrupt task Ix
3 Automatic mode
The SLB module operates as master. The SIMOLINK blocks in the CFC chart must be
configured in an interrupt task Ix (x=1 . . . 8).
Timing: Each SYNC telegram which is received, initiates an interrupt, and therefore execution of
the interrupt task Ix. The SIMOLINK bus cycle is automatically re-initiated each time a SYNC
telegram is received. SIMOLINK telegrams are sent and received in parallel with the signal
processing (internal calculations).
SYNC telegramSYNC telegram
Timer interrupt
Processing ti me of the
SIMOLINK blocks
SIMOLINK cycle
Processing ti me of the
SIMOLINK blocks
NOP
SIMOLINK cycleSIMOLINK cycle
Processing time of the
SIMOLINK blocks
Interrupt task
Processing ti me of the
SIMOLINK blocks
4 External mode
The SLB module operates as master. The SIMOLINK blocks in the CFC chart must be
configured in an interrupt task Ix (x=1 . . . 8).
Timing: The bask clock cycle T0 from the system initiates that telegrams are sent, and therefore
the start of the SIMOLINK cycle. A subsequently received SYNC telegram initiates an interrupt
and therefore execution of interrupt task Ix. The signal processing (internal calculations) are
realized after the SIMOLINK telegram has been sent and received.
The SLB module operates as master. The SIMOLINK blocks in the CFC chart must be
configured in a cyclic task T1=T0.
Timing: The basic clock cycle T0 initiates that telegrams are sent (starts the SIMOLINK cycle)
and the SIMOLINK blocks are processed in T1=T0. The signals are processed (internal
calculation) at the same time as sending and receiving SIMOLINK telegrams.
T0 interrupt
T0 interruptT 0 interrupt
SIMOLINK cycle
Processing ti me of the
SIMOLINK blocks
Cyclic task T1 = T0
SIMOLINK cycleSIMOLINK cycle
Processing time of the
SIMOLINK blocks
Processing time of the
SIMOLINK blocks
Function Blocks - FM 458-1 DP 5-3
Edition 12.2004
Page 61
SIMOLINK drive coupling
10 Cyclic-automatic-mode 10
The cyclic-automatic-mode 10 offers the advantage to place the function block configuration in
cyklic tasks, in opposed to mode 3.
SYNC TelegramSYNC Telegram
Processing time of the
SIMOLINK bl ocks
interrupt task
settings
Interrupt source to be set for the interrupt task Ix of the SIMOLINK blocks, if:
Operating
mode
0 LE bus interrupt 1 LE bus interrupt 3 LE bus interrupt 2 LE bus interrupt 4
2 LE bus interrupt 5 LE bus interrupt 6 LE bus interrupt 7 LE bus interrupt 8
3 LE bus interrupt 1 LE bus interrupt 3 LE bus interrupt 2 LE bus interrupt 4
4 LE bus interrupt 1 LE bus interrupt 3 LE bus interrupt 2 LE bus interrupt 4
cycle
NOTE
It is necessary to set interrupt task sources for operating modes
0, 2, 3, 4 and 10, in order to initiate the configured interrupt tasks.
The settings must be made in the HWConfig in the properties
window under the "Interrupt tasks" tab. They are dependent on
the configured hardware components.
first SLB module at
slot 1
NOP
Processing time of the
SIMOLINK blocks
cyclic Task Tx
first SLB module at
slot 2
cycle
second SLB
module at slot 1
cycle
Processing time of the
SIMOLINK bloc ks
second SLB
module at slot 2
NOTE
The first SLB module can be an EXM 448-1- or an ITSL module
without optional SLB. The settings for the second SLB module
are only relevant for an ITSL module with optional SLB.
5-4 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 62
SIMOLINK drive coupling
I/O
TAD
MOD
ASL
POW
FIL
DM
NSL
EN
YF
NCP
NCY
NOR
NTO
NCR
Hardware address SLB (name of the SLB module), which can be
configured in HWConfig.
Operating mode
Sets the required operating mode
(initialization connection)
Node address
Address of the slave (1 . . . 200) in the SIMOLINK ring (this is only
relevant, if operating mode 0 was selected at MOD)
(initialization connection)
Send power
Send power of the SLB module (if a lower send power is used, the
aging processing of the fiber-optic cables is slowed down and errors in
the medium can be more easily identified at start-up). Value range: 1 . .
. 3 (small, medium large);
(initialization connection)
Filling-up the telegram gaps
For FIL=1, if there is a gap between two bus cycles, then this is
filled-up with NOP telegrams.
Note
: if the sampling time T0 is synchronized, then filling-up only
operates correctly if the equivalent sampling time is precisely set to
the value of the cycle time that is used for synchronization.
(initialization connection)
Use PCI Copy
1 = Data with PCI Copy read
0 = Data normal read
max. blocksize
Max. blocksize for a PCI Copy block
Bus enable
Start/stop of the SLB module for telegram data transfer
EN=0 no telegrams are sent
EN=1 telegrams are sent corresponding to the selected operating
mode
Error status of the block
YF=0 No error, YF > 0 refer to coded error output
Number of nodes
Number of nodes in the SIMOLINK ring
(including SL master)
Number of cycles
Number of SIMOLINK cycles which have been executed or the number
of SIMOLINK telegrams
Number of overruns
The number of statuses, where the configured function blocks have not
be able to provide the data or retrieve the data up to the start of the
next SIMOLINK cycle. The data remains consistent, even for errors
such as these and the SIMOLINK cycle is started with old data.
In order to resolve this problem, the interrupt tasks, in which the
SIMOLINK blocks were configured, must be relieved.
No. of timeouts on the SIMOLINK ring
A timeout means that a telegram has failed (not been received).
Number of CRC errors in the SIMOLINK ring
A node sends a telegram with a CRC error.
(default: 0)
(default: 0)
(default: 3)
(default: 0)
(default: 0)
(default: 15)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Function Blocks - FM 458-1 DP 5-5
Edition 12.2004
Page 63
SIMOLINK drive coupling
NDM
CO1
CO2
QF
Number of the defective module and/or node that detected the fault in
the line.
No. of waiting cycles
The number of the processor cycles specifies while the values by PCI
Copy are being waited for.
No. of CO1 Overruns (default: 0)
Group error bit
QF=0 No error, QF=1 for error (if YF≠0)
(default: 0)
(default: 0)
(default: 0)
5-6 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 64
SIMOLINK drive coupling
coded error output
Error statuses which occur for the appropriate block are output in a
coded form at outputs YF of the SIMOLINK blocks. Only the last error
event is displayed.
Value Significance
2 TAD input is incorrectly connected
3 SLB module not inserted or hardware defective
4 SLB module is already being used by another central block @SL
5 Memory problem
6 Central block @SL not configured
7 No SIMOLINK block available
8 Memory register was not set-up
9 Software does not support the hardware combination
10 Block must be configured in an interrupt task
11 Block must be configured in a cyclic task
12 Block must be configured in a cyclic task with TX=T0
13 Equivalent sampling time must be equal to T0
14 Interrupt source for the alarm task is incorrect
15 Blocks must be configured in the same sampling time
16 Operating mode is (still) not supported
17 Node address at input ASL is too high
18 No send- and receive blocks available
Note
: However, if send and receive blocks are configured, then the
fault messages at these blocks should be carefully observed!
19 Maximum number of SIMOLINK telegrams (max. 1021 net
telegrams) exceeded → increase SIMOLINK cycle time or configure
fewer SIMOLINK blocks
20 Slave address too high
21 Channel number too high
22 Slave attempts to write to the incorrect address
23 Cross-data transfer is only possible in one direction per slave
(sending or receiving)
30 Physical data transfer along the SIMOLINK ring is faulted
→ increase the send power at one of the partial segments, or the
fiber-optic cable medium or connector is defective
31 CRC error (check sum error)
32 Timeout error in the SIMOLINK ring
33 Only for MOD=0: signaled SIMOLINK cycle time (in the special
telegram from the SL master) does not correspond to the configured
equivalent sampling time
Function Blocks - FM 458-1 DP 5-7
Edition 12.2004
Page 65
SIMOLINK drive coupling
Configuringdata
Computation time [µs] FM 458-1 DP 69,3
Can be inserted online No
Can be configured in Cyclic task
Executed in Initialization mode
Normal mode
Special features -
5-8 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 66
SIMOLINK drive coupling
5.2 SLAV, SLAVE_R SIMOLINK receive block for one actual
value
Symbol
Hardware address SLB ―GV TAD YA0DI―Actual value from slave 0
Address of the first slave ―I FSL YA1DI―Actual value from slave 1
Number of slaves ―I NSL YA2DI―Actual value from slave 2
Channel number for the actual value ―I CSV YA3DI―Actual value from slave 3
Enable cross-data transfer ―BO QV YA4DI―Actual value from slave 4
SLAV
YA5DI―Actual value from slave 5
YA6DI―Actual value from slave 6
YA7DI―Actual value from slave 7
SEQI―Sequence number
YFI―Block error status
QFBO―Group error bit
Brief description
A max. of 8 actual values can be transferred from max. 8 slaves using
the SLAV receive block. Each slave can only receive one actual value,
and for all of the slaves, only the same channel number is addressed.
The SLAVE and SLAVE_R function blocks are functionally identical. The
only difference is the data type of the actual value connections YA0 to
YA7:
SLAVE: DINT
SLAVE_R: REAL
Mode of operation
1. The SLAV function block executes the following steps while the
system is being initialized
− Checks the task assignment,
− Initializes the task list of the SLB module corresponding to the data
configured at the inputs
2. In the normal system mode ("RUN“ operating status), the SLAV
function block executes the following steps:
− Checks that the inputs are within the permissible value range
− Reads-out the actual values to be received from the receive buffer
of the SLB module#
Function Blocks - FM 458-1 DP 5-9
Edition 12.2004
Page 67
SIMOLINK drive coupling
I/O
TAD
FSL
NSL
CSV
QV
YA0 to
YA7
SEQ
YF
QF
I
SLB hardware address (name of the SLB module), which can be
configured in HWConfig
Address of the first slave from which the actual value YA0 should
be received, value range 1 . . . 200
(initialization connection)
No. of slaves, from which actual values are to be received,
value range 1. . . 8
(initialization connection)
Channel number on which the actual value is received,
value range 0 . . . 7
(initialization connection)
Enable cross-data transfer
This is used, if data is to be sent to a slave in the same cycle which
is physically located in front in the SIMOLINK ring (e.g. from slave 4
to slave 1).
Actual value YA from slaves 1 to 8
A maximum of 8 actual values can be received.
Sequence number
Number of the block in the SIMOLINK block sequence
The value supplies info as to whether the block was correctly
initialized.
Error status of the block
YF=0 no error, YF > 0 refer to coded error output @SL
Group error bit
QF=0 no error, QF=1 for error (if YF≠0)
(default: 1)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Configuringdata
Computation time [µs] FM 458-1 DP 34,7
Can be inserted online No
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
5-10 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 68
SIMOLINK drive coupling
5.3 SLD SIMOLINK delta evaluation
Symbol
Hardware address SLB ―GV TAD DATDI―Delta time
Brief description
SLD
DMXDI―Delta time, max.
DMNDI―Delta time, min.
SEQI―Sequence number
YFI―Block error status
QFBO―Group error bit
A sampling time failure can be detected using function block SLD. The
counter status is interrogated at each SYNC interrupt (this is generated at
the end of every telegram cycle). The block can calculate and output the
difference to the old (previous) value.
Mode of operation
The blocks reads the interrogated value of the counter and generates the
difference to the value which was saved in the old (previous) cycle. This
value is output at DT.
The minimum and maximum values of DT are kept for monitoring
purposes.
I/O
TAD
DT
DMX
DMN
SEQ
YF
QF
SLB hardware address (name of the SLB module), which can be
configured in HWConfig
Delta time
Difference to the last SIMOLINK cycle duration
Delta time, max.
Maximum value of DT
Delta time, min.
Minimum value of DT
Sequence number
Number of the block in the SIMOLINK block sequence
This value provides information as to whether the block was correctly
initialized.
Error status of the block
YF=0 no error, YF > 0 refer to coded error output @SL
Group error bit
QF=0 no error, QF=1 for error (if YF≠0)
Configuringdata
Computation time [µs] FM 458-1 DP 19,8
Can be inserted online No
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Function Blocks - FM 458-1 DP 5-11
Edition 12.2004
Page 69
SIMOLINK drive coupling
5.4 SLDIS SIMOLINK dispatcher
Symbol
Hardware address SLB ―GV TAD SEQI―Sequence number
Number of slaves ―I NSL YFI―Block error status
Number of channels ―I NCN QFBO―Group error bit
Enable cross-data transfer ―BO QV
SLDIS
Brief description
A dispatcher mode is prepared in-line with the SIMOLINK specifications
(as for MASTERDRIVES drive converters) using the SLDIS function
block.
Mode of operation
The block registers the telegrams for all NSL slaves and all NCN
channels.
I/O
TAD
NSL
NCN
QV
SEQ
YF
QF
Hardware address SLB (name of the SLB module), which can be
configured in HWConfig
Number of all of the slaves in the SIMOLINK ring
(initialization connection)
Number of all of the channels
(initialization connection)
Enable cross-data transfer
This is used, if data are to be sent to a slave in the same cycle, which
is located physically in front in the SIMOLINK ring (e.g. from slave 4
to slave 1).
Sequence number
Number of the block in the SIMOLINK block sequence
This value provides information as to whether the block was correctly
initialized.
Error status of the block
YF=0 no error, YF > 0 refer to coded error output @SL
Group error bit
QF=0 no error, QF=1 for error (if YF≠0)
(default: 1)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Configuringdata
Computation time [µs] FM 458-1 DP 14,7
Can be inserted online No
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
5-12 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 70
SIMOLINK drive coupling
5.5 SLSV, SLSV_R SIMOLINK send block for one setpoint
Symbol
Hardware addresse SLB ―GV TAD SEQI―Sequence numbedr
Address of the first slave ―I FSL YF I―Block error status
Number of slaves ―I NSL QFBO―Group error bit
Channel number for the setpoint ―I CSV
Setpoint at slave 0 ―DI XS0
Setpoint at slave 1 ―DI XS1
Setpoint at slave 2 ―DI XS2
Setpoint at slave 3 ―DI XS3
Setpoint at slave 4 ―DI XS4
Setpoint at slave 5 ―DI XS5
Setpoint at slave 6 ―DI XS6
Setpoint at slave 7 ―DI XS7
SLSV
Brief description
A maximum of 8 setpoints can be transferred to a maximum of 8 slaves
using the SLSV send block. Only one setpoint can be sent to each slave,
and for all of the slaves, only the same channel number can be
addressed.
The SLSV and SLSV_R function blocks are functionally identical. The
only difference is the data type of the setpoint connections XS0 to XS7:
SLSV: DINT
SLSV_R: REAL
Mode of operation
1. The SLSV send block executes the following steps while the system is
being initialized:
− Checks the task assignment
− Initializes the task-list of the SLB module corresponding to the data
configured at the inputs
2. In the normal system mode ("RUN" mode), the SLSV send block
executes the following:
− Calculates the setpoints
− Checks that the inputs are within the permissible value ranges
− Enters the setpoints to be sent into the write buffer of the SLB
module
Function Blocks - FM 458-1 DP 5-13
Edition 12.2004
Page 71
SIMOLINK drive coupling
I/O
TAD
FSL
NSL
CSV
XS0
to
XS7
SEQ
YF
QF
Hardware address SLB (name of the SLB module), which can be
configured in HWConfig
Address of the first slave to which setpoint XS0 should be sent,
value range 1 . . . 200
(initialization connection)
Number of slaves to which the setpoint should be sent,
value range 1. . . 8
(initialization connection)
Number of the channel on which the setpoint is sent,
value range 0 . . . 7
(initialization connection)
Setpoint XS for slaves 1 to 8,
A maximum of 8 setpoints can be sent.
Sequence number
Number of the blocks in the SIMOLINK block sequence
This value provides information as to whether the block was correctly
initialized.
Error status of the block
YF=0 no error, YF > refer to coded error output @SL
Group error bit
QF=0 no error, QF=1 for error (if YF≠0)
(default: 1)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Configuringdata
Computation time [µs] FM 458-1 DP 34,7
Can be inserted online No
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
5-14 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 72
SIMOLINK drive coupling
5.6 SLSV2, SLSV2R SIMOLINK send block for 2 setpoints
Symbol
Hardware addresse SLB ―GV FSL SEQI―Sequence number
Address of the first slave ―I NSL YFI―Block group error status
Channel number for setpoint 2 ―I CSV
Channel number for the setpoint ―I XSA
Common setpoint of the main angle ―DI XO0
Setpoint offset for slave 0 ―DI XO1
Setpoint offset for slave 1 ―DI XO2
Setpoint offset for slave 2 ―DI XO3
Setpoint offset for slave 3 ―DI XO4
Setpoint offset for slave 4 ―DI XO5
Setpoint offset for slave 5 ―DI XO5
Setpoint offset for slave 6 ―DI XO6
Setpoint offset for slave 7 ―DI XO7
SLSV2
No. of slaves ―I ACL QFBO― Group error bit
Axix cycle length ―DI CTV
Brief description
2 setpoints can be sent to each slave using the SLSV2 send block. In this
case, the block can handle a maximum of 8 slaves. The first setpoint is
transferred to all of the 8 slaves.
This functionality can be used to implement a virtual shaft, especially if
the time and the position/angular setpoint must be transferred to the
slaves.
Mode of operation
The SLSV2 and SLSV2R function blocks are functionally identical. The
only difference is the data type of the setpoint connections XO0 to XO7:
SLSV2: DINT
SLSV2R: REAL
1. The SLSV2 send block executes the following steps while the system
is being initialized:
− Checks the task assignment
− Initializes the task list of the SLB module corresponding to the data
configured at the inputs
2. In the normal system mode ("RUN" mode), the SLSV2 send block
executes the following steps:
− Calculates the setpoints
− Checks that the inputs are within the permissible value ranges
− Enters the setpoints to be sent into the write buffer of the SLB
module
Function Blocks - FM 458-1 DP 5-15
Edition 12.2004
Page 73
SIMOLINK drive coupling
I/O
TAD
FSL
NSL
ACL
CTV
CSV
XSA
XO0
to
XO7
SEQ
YF
QF
Hardware address SLB (name of the SLB module), which can be
configured in HWConfig
Address of the first slave to which setpoint XO0 should be set, value
range 1 . . . 200
(initialization connection)
Number of slaves to which the setpoint should be sent, value range
1. . . 8
(initialization connection)
Axis cycle length
Upper integrator limit value
Channel number for setpoint 2, value range 0 . . . 7
(initialization connection)
Number of the channel on which the setpoint is sent,
Value range 0 . . . 7
(initialization connection)
Common setpoint XS of the main angle/position for all NSL slaves (default: 0)
Setpoint offset XO for slaves 1 to 8,
A maximum of 8 setpoint offsets can be sent.
Sequence number
Number of the block in the SIMOLINK block sequence
This value provides information as to whether the block was correctly
initialized.
Error status of the block
YF=0 no error, YF > 0 refer to coded error output @SL
Group error bit
QF=0 no error, QF=1 for error (if YF≠0)
(default: 1)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Configuringdata
Computation time [µs] FM 458-1 DP 39,6
Can be inserted online No
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
5-16 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 74
SIMOLINK drive coupling
A
A
A
A
A
A
A
A
A
5.7 SLSVAV SIMOLINK send and receive block for one slave
Symbol
Hardware addresse SLB
addresse of the slave
Number of send channels
Number of receive channels
setpoint at channel 0
setpoint at channel 1
setpoint at channel 2
setpoint at channel 3
setpoint at channel 4
setpoint at channel 5
setpoint at channel 6
setpoint at channel 7
Brief description
SLSVAV
GV
I
I
I
DI
DI
DI
DI
DI
DI
DI
DI
TAD
SL
NSV
NAV
XS0
XS1
XS2
XS3
XS4
XS5
XS6
XS7
YA0
YA1
YA2
YA3
YA4
YA5
YA6
YA7
SEQ
YF
QF
DI
DI
DI
DI
DI
DI
DI
DI
I
Sequence number
I
Block error status
BO
Group error bit
ctual value from slave 0
ctual value from slave 1
ctual value from slave 2
ctual value from slave 3
ctual value from slave 4
ctual value from slave 5
ctual value from slave 6
ctual value from slave 7
A maximum of
• 8 setpoints and
• 8 actual values
can be transfered to and from one slave. The number of addressed
channels for the setpoints and the actual values is configured at the
inputs.
Mode of operation
1. The SLSVAV send and receive block executes the following steps
while the system is being initialized:
• Checks the task assignment
• Initializes the task-list of the SLB module corresponding to the
data configured at the inputs
2. In the normal system mode ("RUN" mode), the SLSVAV send and
receive block executes the following:
• Checks that the inputs are within the permissible value range
• Enters the setpoints to be sent into the write buffer of the SLB
module
• Reads-out the actual values to be received from the receive
buffer of the SLB module
Function Blocks - FM 458-1 DP 5-17
Edition 12.2004
Page 75
SIMOLINK drive coupling
I/O
TAD
ASL
NSV
NAV
XS0
to
XS7
YS0
to
YS7
SEQ
YF
QF
Hardware address SLB (name of the SLB module), which can be
configured in HWConfig
Address of the slave for dataexchange,
value range 1 . . . 200
(initialization connection)
Number of channels for the setpoint to be sent,
value range 0. . . 8
(initialization connection)
Number of channels for the actual values to be received,
value range 0 . . . 8
(initialization connection)
Setpoint XS for channel 0 to 7,
A maximum of 8 setpoints can be sent.
Actual values YS from channel 0 to 7,
A maximum of 8 actual values can be received.
Sequence number
Number of the blocks in the SIMOLINK block sequence
This value provides information as to whether the block was
correctly initialized.
Error status of the block
YF=0 no error, YF > 0
Group error bit
QF=0 no error, QF=1 for error (if YF≠0)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Configuringdata
Computation time [µs] FM458 / PM6 34,7
Can be inserted online no
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
5-18 Function Blocks - FM 458-1 DP
Edition 12.2004
Page 76
6 Closed-loop control blocks
6.1.1 INT_M Modulo integrator for axis cycle correct integration
Symbol
INT_M
Denominator, ratio ―DI DN YF W―Block error status
Modulo value ―DI MOD YDI―Output
Input ―DI X QPBO―Positive oberflow
Numerator, ratio ―DI NM QNBO―Negative overflow
Setting value ―DI SV
Reset ―BO R
Set ―BO S
Hold ―BO H
Brief description
the virtual master block INT_M is used to generate position reference
values in angular synchronism.
Mode of operation
The block sums the input values X, weighted with ratio NM and DN.
If the sum of the modulo value MOD exceeds or falls below 0, the modulo
value is subtracted or added, and an overflow bit QP or QN is set for the
duration of the sampling time.
I/O
MOD
X
NM
DN
SV
R
S
H
Modulo value, value range 1 . . .
Input quantity of the integrator
e.g. velocity (ramp-function generator output)
Numerator value for the ratio (gearbox factor)
NM ∗ X may not exceed
value range: –
Denominator value for the ratio (gearbox factor),
value range: –
Setting value
Is the value which is set to the output Y with S=1.
Reset
R=1 → Y=0
Setting
Bit to set the output value Y to the setting value SV
S=1 → Y=SV (initial offset)
Hold
Holds the instantaneous value at output Y
H=1 → Y=Y
old
30
2
30
2
2
to + 230
to + 230
31
30
2
,
(default: 0)
(default: 0)
(default: 1)
(default: 1)
(default: 0)
(default: 0)
(default: 0)
(default: 0)
Function Blocks - FM 458-1 DP 6-1
Edition 12.2003
Page 77
Closed-loop control blocks
Y
QP
QN
YF
Output quantity of the integrator
R=S=H=0 → Y=Yold+X∗NM/DN
Positive overflow
QP=1 → Y + X ≥ MOD (Y=Y-MOD)
Negative overflow
QN=1 → Y+X < 0 (Y=Y+MOD)
Error status of the block
YF=0 no error, YF > 0 coded error output
Coded error output
Configuringdata
(default: 0)
(default: 0)
(default: 0)
(default: 0)
The error status is output in a coded form at output YF of the modulo
integrator INT_M. The last error event is always displayed.
Value Significance
1
4 Division overflow, positive
8 Division overflow, negative
16 Overflow, rest positive
32 Overflow, rest negative
MOD > 230 or < 1
Computation time [µs] FM 458-1 DP 19,8
Can be inserted online Yes
Can be configured in Interrupt tasks
Cyclic tasks
Executed in Initialization mode
Normal mode
Special features -
6-2 Function Blocks - FM 458-1 DP
Edition 12.2003
Page 78
Index
@
@CPB P bus, central coupling block .......................................................................................... 2-15
@CSL2F PROFIBUS FMS coupling central block........................................................................ 2-1
@CSL2L PROFIBUS FDL central block ....................................................................................... 2-1
@CSPRO Central block, PROFIBUS DP coupling................................................................2-1, 2-2
@FMPAR Parameter processing on FM458 modules................................................................ 2-29
@SL SIMOLINK central block....................................................................................................... 5-1
B
BRCV Block-oriented data reception via an S7 coupling............................................................ 2-20