Manual
ibaBM-DPM-S-64
60
Issue 2.5
Figure 24:
ibaLogic, output signal to S7
4.
Start the SIMATIC-Manager, enter a new variable table and display the transmitted
generator signal (DB13.DBW6) in INT format.
11.2.2
Sample projects
On the disk which is part of the delivered package you will find four sample projects
with examples for the different modes:
S300_SFC_DPM-S64.zip
Using SFC14/15 with S7-300
S400_SFC_DPM-S64.zip
Using SFC14/15 with S7-400
S7_L2B-DPM.zip
Using PEW/PAW accesses
11.2.3
Reloading S7 Application Data from/to DP Master
When assigning the slaves in the master system several data blocks are defined in the
peripheral address space at the same time. The block-wise reloading of application da-
ta is used to reach a higher security and a better detection of short termed failures.
In order to reload the data from or to the periphery the use of SFC14 and SFC15 is
recommended. Please refer to the sample projects in order to see how it's done.
When dealing with the S7-300 family more than one call of SFC14/SFC15 is required
because the data block length is limited to 32 Bytes. When working with the S7-400
family, 122 Bytes are available per data block. This is the reason why you find different
GSD-files on the disk.
Note
In former version V1.1 the delivered GSD files permitted to work with reload commands
directly in the peripheral output area ("PQ-area"). You will find these GSD files on the
disk too (folder \L2B_Card), since this mode of operation is still supported. But unlike
this older version the method of using the SFCs for reloading offers a better behaviour
in case of DP faults and data-consistent blocks. When using the new GSD files the us-
age of SFCs is required because the direct reload commands are not supported.
