Install-Handling

SUMMARY

The AbvSpu database keeps the necessary parameters of the Data Objects MPs and PVs for the S7-Program 'AbvSpu' to run.

CONTENTS

  1. Scope of delivery
  2. Installation

Scope of delivery

AbvSpuOpt-MsPv (SAPI)
The S7-Program 'AbvSpuOpt-MsPv-Sapi' for S7-300/400 is delivered as AWL-Source and contains the following S7-Files:
File Meaning
SpuOpt_Sapi_1.awl AbvSpu-Kernel with communication based on SOFTNET-IE (Industrial Ethernet ISO)
BEHAVIOUR ON STARTING:
The defined start values are entered on any start/restart.
SpuOpt_Sapi_2.awl AbvSpu-Kernel with communication based on SOFTNET-IE (Industrial Ethernet ISO)
BEHAVIOUR ON STARTING:
The defined start values are entered on the first start with a new AbvSpu database only.
Ob1_sapi.awl OB1-Template (cyclic operation) with the calls for the necessary AbvSpu modules.
Ob100.awl OB100-Template (start) with the calls for the necessary AbvSpu modules.
Ob101.awl OB101-Template (restart) with the calls for the necessary AbvSpu modules.
abvspu_sapi.sdf AbvSpu-Symbol File.
builtin.sdf Symbol File of the SFB/SFC-Modules out of the SIMATIC Manager - Standard Library.
iec.sdf Symbol File of the IEC-Modules out of the SIMATIC Manager - Standard Library.
WARNING
The AbvSpu uses the IEC-Module FC8 (DT_TOD) of the SIMATIC Manager - Standard Library. That module must be copied manually to the according S7-Module folder.

AbvSpuOpt-MsPv (UDP)
The S7-Program 'AbvSpuOpt-MsPv-Udp' for S7-300/400 is delivered as AWL-Source and contains the following S7-Files:
File Meaning
SpuOpt_Udp_1.awl AbvSpu-Kernel with UDP-communication (Multicast-IP)
BEHAVIOUR ON STARTING:
The defined start values are entered on any start/restart.
SpuOpt_Udp_2.awl AbvSpu-Kernel with UDP-communication (Multicast-IP)
BEHAVIOUR ON STARTING:
The defined start values are entered on the first start with a new AbvSpu database only.
Ob1_udp.awl OB1-Template (cyclic operation) with the calls for the necessary AbvSpu modules.
Ob100.awl OB100-Template (start) with the calls for the necessary AbvSpu modules.
Ob101.awl OB101-Template (restart) with the calls for the necessary AbvSpu modules.
abvspu_udp.sdf AbvSpu-Symbol File.
builtin.sdf Symbol File of the SFB/SFC-Modules out of the SIMATIC Manager - Standard Library.
iec.sdf Symbol File of the IEC-Modules out of the SIMATIC Manager - Standard Library.
WARNING
The AbvSpu uses the IEC-Module FC8 (DT_TOD) of the SIMATIC Manager - Standard Library. That module must be copied manually to the according S7-Module folder.

For the program version AbvSpu-UDP the following SIMATIC-NET CP300/400-Communication modules must be copied to the module bin:

CP300: FC5=AG_SEND (from V4.1), FC6=AG_RECV (from V4.5)
CP400: FC50=AG_LSEND, FC60=AG_LRECV

WARNING
The module numbers FC5 and FC6 are already used by the IEC-Modules 'DI_STRNG' and 'DT to DATE'. Either both these Symbol-Entries are removed prior to copying the modules FC5 and FC6 or different module numbers are used for FC5 and FC6.

Installation

Import Symbols
Open the Symbol Editor with its function "Table/Import..." and import the following tables:

The import of the external symbol files is necessary on setting up a new S7-Program or when AbvSpu is upgraded.

Insert external sources
The external sources are copied to the source bin of the S7-Programs. The files are inserted via the context menu function "Insert new Object>External Source..." (Multiple selections is possible)

Compiling external sources
To compile external sources the IEC-Module FC8 (DT_TOD) is needed in the Module-Bin. If missing it can be copied out of the "SIMATIC MANAGER Standard Library/IEC-Functions".

The external sources must be compiled in the following sequence: To compile the external source, the according file in the source-bin has to be selected and the compilation started via the context menu function "Compile Ctrl+B".
On compiling the source files in the KOP/AWL/FUP-Editor are opened. If the compiler ends without errors the S7-Modules are created in the Module-Bin with the actual modification date.

WARNING
The OB1-Source contains a module-call to the AbvSpu database, i.e. it must be compiled AFTER the AbvSpu database was imported and compiled.

AbvSpu-Database
The AbvSpu database generated by the AvET (AWL- and SDF-Files) will be integrated to the S7-Program as described below "Import Symbols" und "Insert/Compile external sources"

Afterwards the OB1-Source can be compiled.

Taking the AbvSpu Database to the PLC:
Note:
The newly compiled modules (identified by the actual modification date) must not be copied online to the PLC! For copying the new database modules the PLC must be stopped and afterwards started again.

OB1
The OB1-Template contains the following Module-Calls:
Name Description
U DB195.DBX 161.0 // AbvSpu-Start-Up flag. On an error execution of OB1 is abandoned.
BEB
CALL "abvspu_100MS_TS" // 100ms-Time Stamp
CALL "abvspu_CP_RECV" // Receiving via SAPI/UDP
CALL "abvspu_WorkPvObj" // Process Variables
ZDB:=DB195.DBW20
CALL "spuDB_ILOPLC" // Blocking-Logic
CALL "abvspu_WorkDynLmts" // Dynamic Limits
CALL "abvspu_PRE_XMP" // Measuring Points - Preprocessing
CALL "abvspu_Work_DMP" // Binary-Measuring Points
CALL "abvspu_Work_AMP" // Analogue-Measuring Points
CALL "abvspu_POST_XMP" // Measuring Points - Postprocessing
// CALL ... // Technology-Program
CALL "abvspu_SAPI_QUIT" // SAPI-Acknowledgement (only in the SAPI-Program Version)
CALL "abvspu_CP_SEND" // Sending via SAPI/UDP
CALL "abvspu_1MS_CYCLE" // Calculation of the cycle time

Technology Program
The technology program should be incorporated at the point defined by the OB1-Template.
Note:
After importing a new (modified) AbvSpu Database the technology modules using the Object-Interface of the AbvSpu must be compiled again to make sure the actual Object Numbers are substituted correctly


The following procedure is suggested.