Softplc B
Softplc B
SICAM Contents
SICAM PAS
Getting Started 1
V8.05 Basic Principles 2
Commands 3
Automation Blocks Indications 4
Measured Values and Metered Values 5
Special Blocks 6
Time Blocks 7
Sequence Blocks 8
User-Specific Blocks 9
PAS Standard Library 10
Examples 11
Appendix A
E50417-H8976-C436-A7 Literature
Index
NOTE
For your own safety, observe the warnings and safety instructions contained in this document.
This document has been subjected to rigorous technical review Copyright © Siemens AG 2015. All rights reserved.
before being published. It is revised at regular intervals, and any The disclosure, duplication, distribution and editing of this
modifications and amendments are included in the subsequent document, or utilization and communication of the content are not
issues. The content of this document has been compiled for permitted, unless authorized in writing. All rights, including rights
information purposes only. Although Siemens AG has made best created by patent grant or registration of a utility model or a design,
efforts to keep the document as precise and up-to-date as possible, are reserved.
Siemens AG shall not assume any liability for defects and damage
which result through use of the information contained herein.
Registered Trademarks
This content does not form part of a contract or of business
relations; nor does it change these. All obligations of Siemens AG SIMATIC®, SIMATIC NET®, SIPROTEC®, DIGSI®, SICAM®,
are stated in the relevant contractual agreements. SIMEAS®, SINAUT®, OSCOP®, and DAKON® are registered
trademarks of SIEMENS AG. An unauthorized use is illegal.
Siemens AG reserves the right to revise this document from time to
time. All other designations in this document can be trademarks whose
use by third parties for their own purposes can infringe the rights of
the owner.
Document Release: E50417-H8976-C436-A7.03
Edition: 08.2014
Product version: V8.05
Preface
This manual is a reference document for the graphical and textual configuration of the SICAM PAS automation
by means of the SICAM PAS automation blocks. The basic knowledge required for the work with the SICAM
PAS automation blocks is provided in Chapter Basics. The remaining chapters describe the functionality of the
automation blocks as well as the parameterization and connection of the block inputs and outputs.
Target Group
This manual is mainly addressed to persons configuring and parameterizing substation automation systems.
These persons should have already gained experience in the implementation of automation tasks based on the
IEC 61131-3 automation standard.
Standards
The SICAM PAS automation blocks are developed in compliance with the ISO 9001:2008 standard.
Further Support
If you have any further questions regarding SICAM PAS V8.05 please do not hesitate to contact your
local Siemens representative.
Hotline
Training Courses
If you are interested in our current training program, please contact our training center:
Siemens AG
Siemens Power Academy
Humboldtstr. 59
90459 Nuremberg
Germany
Notes On Safety
This document is not a complete index of all safety measures required for operation of the equipment (module,
device). However, it comprises important information that must be noted for purposes of personal safety, as
well as in order to avoid material damage. Information is highlighted and illustrated as follows according to the
degree of danger:
DANGER
DANGER means that death or severe injury will result if the measures specified are not taken.
WARNING
WARNING means that death or severe injury can result if the measures specified are not taken.
CAUTION
CAUTION means that medium-severe or slight injuries can result if the measures specified are not taken.
NOTICE
NOTICE means that material damage can result if the measures specified are not taken.
NOTE
Important information about the product, product handling, or a certain section of the documentation, which
must be given particular attention.
Only qualified electrical engineering personnel may commission and operate the equipment (module, device)
described in this document. Qualified electrical engineering personnel in the sense of this document are people
who can demonstrate technical qualifications as electrical technicians. These persons may commission,
isolate, ground and label devices, systems and circuits according to the standards of safety engineering.
Use as Prescribed
The equipment (device, module) may only be used for such applications as set out in the catalogs and the
technical description, and only in combination with third-party equipment recommended and approved by
Siemens.
When electrical equipment is operated, hazardous voltages are inevitably present in certain parts. If proper
action is not taken, death, severe injury, or material damage can result:
• The equipment must be grounded at the grounding terminal before any connections are made.
• All circuit components connected to the power supply may be subject to dangerous voltage.
• Hazardous voltages may be present in equipment even after the supply voltage has been disconnected
(capacitors can still be charged).
• Equipment with exposed current-transformer circuits must not be operated. Before disconnecting the
equipment, ensure that the current-transformer circuits are short-circuited.
• The limit values stated in the document may not be exceeded. This must also be considered during testing
and commissioning.
Among other things, this product contains Open Source Software that was developed by third parties. The
Open Source Software included with this product and the relevant Open Source Software license agreement
can be found in Readme_OSS. The Open Source Software program is protected by copyright. You are permit-
ted to use the Open Source Software according to the Open Source Software license agreement. Should con-
tradictions occur between the Open Source Software license conditions and the Siemens license conditions
applicable to the product, the Open Source Software license agreement with respect to the Open Source Soft-
ware shall prevail. The Open Source Software is provided free of charge. If stipulated by the Open Source Soft-
ware license agreement, the source text of the software is available until the end of the third year after
purchasing the product. Shipping charges will apply separately. We are liable for the product including the Open
Source Software according to the license agreement for the product. Any liability arising from the use of the
Open Source Software that exceeds the intended program flow of the product, as well as liability for defects
that were caused by changes made to the Open Source Software, is excluded. If the product was modified, we
cannot provide technical support.
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Open Source Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1 Basic Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2 Starting the SICAM PAS SoftPLC UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2.1 Task in SICAM PAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.2.2 Inserting a PAS Firmware Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.2.3 Programming a Command Interlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.2.4 SoftPLC-Internal Command (Marker Command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.3 Compiling the Project Data into the Destination System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.4 Programming with ST, SFC and STL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.4.1 Special Procedures for SICAM PAS when Using ST, SFC, STL . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2 Basic Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.1 Important Information on the Programming of the SICAM PAS SoftPLC . . . . . . . . . . . . . . . . . . . . . . . 38
2.2 Startup Behavior of the SICAM PAS SoftPLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.3 POUs and Tasks in the SICAM PAS SoftPLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.4 SICAM PAS Process Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.4.1 Components of the Process Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.4.2 Showing the Contents of the Process Data Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.4.3 Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.5 Data Types Used in the SoftPLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.5.1 BOOL(BO) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.5.2 BYTE(BY) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.5.3 WORD(W) Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.5.4 DWORD (DW) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.5.5 INTEGER(I) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.6 REAL(R) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.7 TIME(TI) Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.8 STRING Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.5.9 SICAM PAS Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.6 Configuration of the Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.7 Checking PAS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.8 CFC Chart-in-Chart Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.9 Reusability of POUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.10 Online Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.1 Command Processing Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.1.1 Commands to the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.1.2 System-Internal Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.2 PAS_CRCOM - Command Derivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.2.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.2.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.2.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.3 PAS_COMMCP - Command Output to the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.3.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.3.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.3.3 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.3.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.4 PAS_COMMCP_EX - Command Output to the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.4.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.4.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.4.3 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.5 PAS_SELC - Marker Command for the SoftPLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.5.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.5.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.3 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.5.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.6 PAS_SELC_EX - Marker Command for the SoftPLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.6.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.6.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.6.3 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4 Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.1 Concept of Indication Processing in Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.2 PAS_CRI - Creating Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.2.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.2.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.3 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.2.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
11 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
11.1 Switchgear Interlocking for Busbar Feeder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
11.2 Switching Sequences of the SoftPLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
11.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
11.2.2 Switching Sequence in SFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
A.1 Components of the Process Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
A.1.1 Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
A.1.2 Initiator Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
A.1.3 Additional Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
A.1.4 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
A.1.5 Extended Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
A.1.6 Value Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
A.1.7 Type of TIme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
A.1.8 Identification Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
A.1.9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
A.2 Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
A.3 Data Types of SICAM PAS Process Data Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
A.4 Data Types According to IEC 61131 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Overview
Based on a sample configuration, the present chapter illustrates how to start the SoftPLC, how to connect an
automation block and how to define all related parameters.
Contents
Prerequisites
In order to be able to start the SICAM PAS SoftPLC UI (SoftPLC User Interface), the following prerequisites
must be met:
• A system has been created in SICAM PAS UI – Configuration.
• This system comprises an Automation application.
• A SoftPLC is inserted under Automation.
• Under this SoftPLC, the Info. from - / Cmd. to SoftPLC and Info. to - / Cmd. from SoftPLC devices
are inserted.
CFC1.tif
NOTE
Siemens recommends creating only 1 automation project (application) in a SICAM PAS project.
If you create several SICAM PAS automation projects in a SICAM PAS project, pay attention not to map com-
mands simultaneously to several automation projects. Otherwise the command interlock can not be ensured.
✧ Proceed as follows to open SICAM PAS UI – Configuration via the Windows Start menu:
Siemens Energy > SICAM > PAS > UI – Configuration.
✧ In the tree structure of the mapping view, click Info. from - / Cmd. to SoftPLC.
✧ Map the Information - Monitoring Direction and the Information - Command Direction.
CFC2.tif
Fig. 1-3 SICAM PAS UI – Configuration: mapping of information - Info. from - / Cmd. to SoftPLC
✧ In the tree structure of the mapping view, click Info. to - / Cmd. from SoftPLC.
✧ Map the Information - Monitoring Direction and the Information - Command Direction.
CFC21.tif
NOTE
The SoftPLC Tag Group and SoftPLC Tag Name columns must include an entry for each mapped item of
information. These entries are used as tag names for the PAS interface tags in the SICAM PAS SoftPLC UI.
When mapping an item of information, the SoftPLC Tag Group and the SoftPLC Tag Name are defined au-
tomatically. You can change these default settings.
✧ Highlight SoftPLC in the configuration tree and select Open from the context menu.
SICAM PAS SoftPLC UI opens. The following two files are shown in the project browser:
• Main.ST
is an empty ST program (textual programming).
• pasglob.POU
is always generated automatically (POU stands for Program Organization Unit). The file includes the
PAS interface tags declared as global tags.
The tags describe the items of information mapped in the Mapping view of
SICAM PAS UI – Configuration or by the SoftPLC.
CFC3.tif
✧ In the SICAM PAS SoftPLC UI, click File > New. The Create a new file windows opens.
✧ In the File Type box under POU, select the Program unit. Available program templates are shown in the
Templates pane. Click the I and L buttons in the top right-hand corner above the program templates to
switch between the icon representation style (I) and the list representation style (L).
✧ Click OK to confirm.
CFC4.tif
✧ When the system prompts you as to whether you want to add the CFC program to the active resource,
click Yes to confirm.
✧ The new CFC program is shown in the editor window. The program organizational units available in the
project are shown in the POUs tab of the Catalog. These units include e. g. the PAS firmware blocks (e. g.
PAS_ACQ).
CFC5.tif
Task
Tasks do not need to be configured in SICAM PAS SoftPLC. A task already exists, which considerably simpli-
fies configuration. Each time the SoftPLC is called up, all POUs programmed in the SoftPLC are computed.
NOTE
A mixed task which can be called up cyclically or event-controlled can be created by means of the
SFC_RunCyclic ST block (see chapter 10.7).
POU
In SICAM PAS, PAS firmware blocks do not have a number which specifies the task sequence.
The task sequence depends on the arrangement of the blocks: As a rule, a POU is processed from top to bot-
tom and from left to right.
✧ After creating a new CFC program, click the POUs tab in the Catalog.
✧ Under Firmware, select the block which you want to insert. Next, drag and drop the block into the editor
window.
As soon as you release the mouse button, the mouse pointer changes its shape depending on the possible
plug-in positions.
• If the mouse pointer shows a prohibition sign, you cannot insert the block.
• If the mouse pointer shows Insert, you can click to insert the block.
CFC6.tif
NOTE
In order to ensure that the CFC program can send/receive information to/from SICAM PAS, you must intercon-
nect the program with PAS interface tags.
The tags describe the items of information mapped in the Mapping view of SICAM PAS UI – Configuration
or by the SoftPLC.
The PAS firmware blocks are interconnected by means of the connectors in the right-hand and left-hand margin
bars in the editor window:
✧ In the Catalog, click the Tags tab. The tags available in the project are shown.
✧ Select one or several tags to be interconnected via a margin bar. Be aware of the interconnection
options of PAS interface tags (refer to Table 1-1).
CFC7.tif
✧ Drag and drop the selected tags to the margin bar. The tags are shown in the margin bar and can be
interconnected.
NOTE
The tag selection catalog provides various filter options, such as:
Filtering according to the Data Type via a selection box in the column header
Filtering according to the Used column (only refers to CFC POUs) via a selection box in the column header.
The tags shown in the Catalog window can be interconnected via the margin bars as illustrated in the table
below:
Information PAS data type Name of global tag Can be interconnected to the
The left-hand and right-hand margin bars in the editor window with CFC program provide different functions.
The following functions can be selected from the left-hand margin bar:
• Commands to the SoftPLC
• Incoming indications, metered values and measured values to be processed
Connecting a block
The block is connected with other blocks by means of the left-hand and right-hand margin bar.
In the example below, a group indication is formed with PAS_ORI (refer to figure 1-10).
✧ Interconnect a PAS interface tag representing an indication with a connector in the left-hand margin bar.
✧ Interconnect an input of the PAS_ORI block via the left-hand margin bar:
− To do this, select the input of the block and the corresponding connector with the PAS interface tag
in the left-hand margin bar.
− In SICAM PAS SoftPLC UI, click Insert > Insert Connection. The input of the block is
interconnected with the connector in the margin bar.
✧ The output is connected in a similar way, but you connect the output to a group indication in the right-hand
margin bar.
CFC8.tif
NOTE
✧ Click the destination and release the SHIFT key. The source and the destination are now connected.
To write into blocks, you can insert text blocks in the CFC program.
✧ Highlight the editor window of the CFC program and select Insert Text Block from the context menu.
The shape of the mouse pointer changes depending on the possible plug-in positions:
• If the mouse pointer shows a prohibition sign, you cannot insert the text block.
• If the mouse pointer shows Insert, you can click to insert the text block.
✧ Enter the desired text in the input text and then press the ENTER key. The text block is shown in gray
(disabled).
✧ In order to be able to edit the text in the text block again, double-click the block.
✧ After you have opened the CFC program in the SICAM PAS SoftPLC UI, click the POUs tab in the
Catalog.
✧ Under Firmware, select the PAS_COMMCP block. Next, drag and drop the block into the editor window.
As soon as you release the mouse button, the mouse pointer changes its shape depending on the possible
plug-in positions.
• If the mouse pointer shows a prohibition sign, you cannot insert the block.
• If the mouse pointer shows Insert, you can click to insert the block.
Description
The BVALUE output of the PAS_ORI block is interconnected with the LOCK input of the PAS_COMMCP block.
For PAS_COMMCP, the OUT output is interconnected.
CFC10.tif
The blocks are arranged in a grid of the CFC editor. They cannot be arranged freely. To simplify programming,
this grid can be shown.
In SICAM PAS SoftPLC UI, click View > Grid (CFC) in order to show or hide the grid.
✧ Highlight the block and select Toggle Unused Connectors from the context menu.
Pre-assigning inputs
✧ Double-click the input and enter the desired value in the input box. To do this, be aware of the admissible
data type for the input value.
✧ Press the ENTER key. The input with the new value is shown in gray.
✧ After you have opened the CFC program in SICAM PAS SoftPLC UI, click the POUs tab in the Catalog.
✧ Under Firmware, select the PAS_SELC block. Next, drag and drop the block into the editor window.
✧ As soon as you release the mouse button, the mouse pointer changes its shape depending on the
possible plug-in positions.
If the mouse pointer shows a prohibition sign, you cannot insert the block.
If the mouse pointer shows Insert, you can click to insert the block.
Interconnecting a block
✧ Interconnect a connector in the left-hand margin bar with a PAS interface tag representing a command.
✧ Select the related connector with the PAS interface tag in the left-hand margin bar.
✧ In SICAM PAS SoftPLC UI, click Insert > Insert Connection. The IN input of the block is interconnected
with the connector in the margin bar.
CFC11.tif
The PAS_SELC block is not completely connected. For example, the outputs can be used to start
switching sequences.
Prior to compilation
✧ Select the desired program in the Files tag of the project window.
✧ Highlight the selected program and select Link to Active Resource from the context menu.
If the menu item is disabled (shown in gray), the program has already been added to the active resource
(e. g. when inserting a program).
CFC12.tif
NOTE
Each program must be selected individually and assigned a resource. Multiple selections are not possible. This
step is important for specifying the SoftPLC and must not be forgotten!
The following options are available to optimize the compilation process and to adapt it to your requirements:
• Speed only
The machine code is generated directly, debugging is not possible (fast execution).
• Size only
Interpreter code, debugging is possible (slow execution). This is the default setting for test purposes. As
soon as all testing and commissioning tasks have been completed, switch to the normal setting.
• Normal
This setting is an optimization focusing on the existing programming. Both an interpreter code and a
machine code are used.
In the Edit Resource - SICAM PAS window, select the desired option under Options.
NOTE
As soon as all programming and test steps have been successfully completed, the system should be switched
to Normal for performance reasons.
Compilation
To compile a project:
As soon as you have successfully completed the compilation, the program and the project data are automati-
cally entered in the SICAM PAS database.
NOTE
For more detailed information on programming with the CFC, SFC, STL and ST programming languages, refer
to the online help of the SICAM PAS SoftPLC UI, ? menu > Content and Index.
1.4.1 Special Procedures for SICAM PAS when Using ST, SFC, STL
All SICAM PAS firmware blocks (names beginning with PAS_) which create an indication, a command or a tim-
er must be initialized during the first computing cycle of the resource. When using CFC, this initialization is per-
formed automatically, since all blocks are compulsorily computed during each computing cycle and thus also
during the first cycle.
A simple call of the corresponding block instance without parameters is sufficient in most cases. However, it is
safer to call up the block instance with those parameters which are also used after the first cycle in order to
create a timer, an indication or a command. However, this is performed without actually creating the timer, the
indication or the command upon initialization.
In the SFC Editor, the first step (initialization step) should be used for this purpose, since this step is always run
during the first cycle. However, this is not a prerequisite for ST and STL.
If a SICAM PAS firmware block is called up in ST or STL code without conditions and the POE is not exited by
a RETURN statement, no explicit initialization is required.
If, however, a SICAM PAS firmware block is called up via one single condition (e.g. IF statement, CASE state-
ment, loop), it is not ensured that the condition is already met during the first computing cycle. In this case, the
instance should be initialized at the beginning of the POE.
If no initialization is performed, it is possible that the blocks can only execute some of their functions or no func-
tions at all later during runtime.
Using SFC
When using SFC, an instance of the SFC_RunCyclic block (see chapter 10.7) must be created in a comple-
mentary ST, STL or CFC program and called up with a CYCLETIME.
The call-up via the Main.ST program is recommended. This program is automatically included in the project
and already linked by default to the active resource.
Overview
This chapter describes rules and basic principles of the graphical and textual configuration of SICAM PAS in
the SoftPLC. Knowledge of these rules and basics is a necessary prerequisite.
Contents
2.12 Synchronization of Persistent Data between the SoftPLCs in Case of System Redundancy 57
Caution
Configuration and consistency rules must be strictly adhered to in order to prevent the creation of erroneous
information or data loss.
The following distinctions must be made for the consistency check of PAS data types:
• Process information, indications, metered values, measured values, derived commands (PASDAT-
ABLOCK)
• Group indications (PASGROUP)
• Commands (PASCOMMANDBLOCK)
The compiler outputs error messages if the SICAM data types are not connected properly.
SICAM PAS UI - Configuration ensures that the tag names are unique.
The syntax of the interconnection of process information (indications, measured and metered values) is
checked. This information is not processed if an error is detected.
During the startup of the SICAM PAS SoftPLC, a general interrogation is performed for all indications mapped
to the SoftPLC (slave indications) apart from fleeting indications. The current values are read from the central
image of the SICAM PAS system.
Principles
POUs
In SICAM PAS SoftPLC UI, all three POU types based on IEC 61131-3 are available for code generation (POU
is the abbreviation for Program Organization Unit).
Since all types have advantages and disadvantages and since many programmers only generated program
POUs in the past due to a lack of knowledge, the use of these types is briefly described in this section. The
following applies for all POU types: POUs must not be called up recursively, i. e. they must not call up them-
selves.
Functions
The simplest POUs are referred to as 'functions'. As a rule, they are used for less complex and frequently oc-
curring logic.
Functions have no memory (i. e. local tags are not saved beyond the function call). They always have a return
value and any number of input parameters. Since they have no memory, functions usually always provide the
same result with the same input connection.
Functions cannot be used for the direct processing of PAS information, but only for the processing of
IEC 61131-3 data types. The code of a function is not copied, but only referenced from other POUs (functions,
function blocks or programs). If the code of a frequently used function is changed, the logic for all POUs which
perform calls also changes.
Functions can only be generated with the STL and ST programming languages.
Function blocks
Function blocks are particularly important POUs which are often underestimated. The logic can have any de-
gree of complexity. Function blocks can have any number of inputs and outputs, can access global tags and
are suitable for reuse scenarios in the SICAM PAS SoftPLC.
Function blocks are particularly useful for frequently used, identical logics. Contrary to functions, they have a
memory. Local tags of a function block instance are not lost after the call. For the next call, they are available
with the values defined last. Functions usually always provide the same result with the same input connection.
However, this rule does not apply for function blocks, since their result can depend on saved information.
The instance principle applies for function blocks, i. e. each instance has its own memory. Any change of the
code of a function block automatically changes all instances, since the code is shared (this means that tags
are assigned per instance, but the code exists only once).
Function blocks can be created using the STL, ST and CFC programming languages. They can call up func-
tions and other function blocks.
Programs
Programs unite functions and function blocks in a comprehensive and functional logic. They can also feature
any degree of complexity. Function blocks can have any number of inputs and outputs, can access global tags,
but are not suitable for reuse scenarios in the SICAM PAS SoftPLC.
In the programs, global PAS information is usually interconnected with PAS firmware blocks, individual function
blocks and functions (if used). A smooth program code ensures fast processing.
Comprehensive and coherent logic (including function blocks and functions) should always be realized in a pro-
gram and not distributed between several programs.
Contrary to function blocks, a resource always includes one single program of the same type. Contrary to
IEC 61131-3, one single task is always generated from a program in the SICAM PAS SoftPLC, i.e. a program
cannot be assigned several tasks. This would not make sense, since the SICAM PAS SoftPLC currently fea-
tures only one general, event-controlled task.
Programs can be created in all SICAM PAS SoftPLC programming languages (STL, ST, CFC and SFC).
Task
One single task exists in the SICAM PAS SoftPLC, which considerably simplifies configuration. During each
call of the SoftPLC, all linked programs are computed.
NOTE
A mixed task which can be called up cyclically or event-controlled, can be created by means of the ST block
SFC_RunCyclic (see Chapter 10.7).
NOTE
The sequence of a timeout of a PAS_TIMERSW instance initiates another computation of the entire resource.
If several instances are used in a project with short times (less than 1 s), performance problems can occur due
to the frequent computation of the entire resource.
In these cases, only one single PAS_TIMERSW instance should be used in order to trigger the cyclic compu-
tation of the entire resource.
At all other positions in the project, where a relative time trigger is required, the TON, TOF and TP IEC 61131-
3 standard blocks should be used.
Example:
Proceed as follows to use five different time values: 20 ms, 100 ms, 1000 ms, 3 m and 10 m:
Instead of using five instances of the AS_TIMERSW block, you use one single instance with a timing which
corresponds to the greatest common divisor of all timers. In the example, 20 ms should be used.
At all other positions, a trigger block can be programmed by means of the standard blocks. Example for a cyclic
trigger block in ST with a cycle time of one second:
VAR_INPUT
C_TIME: TIME:= T#1000ms; (* default timeout 1 second *)
END_VAR
VAR_OUTPUT
TRIGGER: BOOL; (* this output alternates with every timer timeout *)
END_VAR
VAR
FB_TON_ON: TON; (* instance of IEC 61131-3 TON function block *)
END_VAR
(* call TON always with TRUE here, because we want a cyclic trigger *)
FB_TON_ON(IN:= TRUE, PT:= C_TIME);
TRIGGER:= TRUE;
ELSE
TRIGGER:= FALSE;
END_IF;
General
The SICAM PAS process data of the PASDATABLOCK data type is arranged according to a defined structure,
the so-called SICAM PAS process data structure (refer to chapter 2.4.1).
The SICAM PAS process data structure is subdivided in individual, uniquely positioned structure blocks. Struc-
ture blocks comprise information and additional information such as time stamp, status, cause, etc. The unique
position of the structure blocks allows for the unique addressing of different items of partial information within
the SICAM PAS process data structure.
The SICAM PAS process data structure is mapped in the main memory of the PAS hardware by means of a
structured area. The information mapped here and additional information is combined as PAS information and
distributed within the system, i. e. it is available at any location within the PAS system.
Due to the unique structure, i. e. the unique position of the structure blocks within the information structure, spe-
cific PAS firmware blocks can be used to filter partial information from PAS information in order to make it avail-
able for logical links or additional processing steps.
The sections below provide basic information on the process data structure.
An overview of the available component variants and their significance is provided in Appendix A.1.
Indications, measured values, metered values or command derivations (PAS_CRCOM block) always consist
of one single process data structure block. The PAS_SASS automation block splits PAS information and shows
the individual structure elements (see Chapter 6.2).
Commands
Commands in the PASCOMMANDBLOCK SICAM PAS data format consist of several process data structure
blocks (composed command structure).
2.4.3 Pointers
General
In SICAM PAS, a process data structure block is referred to as PAS information. Each item of PAS information
is stored at a specific location within the main memory of the SoftPLC. By means of the address, this position
is uniquely assigned and can be identified.
No data records are transmitted for the mapping of PAS information via the SICAM PAS SoftPLC. Pointers are
set to the corresponding addresses instead. The data transfer between the blocks or the task and the items of
PAS information is restricted to the transfer of addresses, i. e. of scalable values.
This address transfer is represented on the graphical user interface of the SoftPLC as follows:
• Only addresses are entered in the margin bars of the SoftPLC user interface, i. e. pointers are set.
• The pointers are connected to the inputs or outputs of the blocks.
A
Pointers
PD structure
zeiger.cdr
NOTE
In the following text, the term pointer refers to the address of an item of PAS information (i. e. of a process data
structure block) in the main memory of the SoftPLC.
General
The inputs and outputs of the SICAM PAS automation blocks process different data types depending on the
type of the incoming or outgoing signals. Possible data types are listed below:
• BOOL (BO)
• BYTE (BY)
• WORD (W)
• DWORD (DW)
• INTEGER (I)
• REAL (R)
• TIME (TI)
• STRING
• PASDATABLOCK
• PASCOMMANDBLOCK
• PASGROUP
• PASSTATELINK
NOTE
A summary of further data types according to EC 61131 is available in the chapter Data Types According to
IEC 61131, page 270.
FALSE FALSE
TRUE TRUE
0 to 255 dec. 28 28
-3.456e-3 -3.456e-3
2.573e19 2.573e19
T#123456789ms T#3h25m45s678ms
T#32m5s T#32m5s
NOTE
NOTE
For inputs and outputs of PAS firmware blocks where pointers have been applied to a PASDATABLOCK, PAS-
COMMANDBLOCK, PASGROUP or PASSTATELINK, the compiler issues an error message in
SICAM PAS SoftPLC UI if incorrect connections have been programmed.
An error message is only issued in case of an incorrect interconnection of the structure types. However, the
compiler in SICAM PAS SoftPLC UI does not check if an incorrect interconnection exists within the same struc-
ture type.
General
The inputs and outputs can be configured directly. The permitted tag format depends on the data type and is
explained in the sections describing the individual data types (see Chapter 2.5).
CFC
✧ Double-click on the input and enter the desired value in the input box. Be aware of the admissible data
type for the input value.
✧ Press the ENTER key. The input with the new value is shown in gray.
In the program code, the block is programmed via the function call.
NOTE
Before configuring and interconnecting the inputs and outputs of blocks, read the descriptions of the related
automation blocks in chapter 3 to chapter 8 or table A-11 on page 268 in Appendix A.
Check
The following section explains how to check PAS information transmitted to the automation blocks (process
data structure block):
• Polls of the change marker of the incoming PAS information:
If no change occurs, the processing is canceled.
• Plausibility check of the input tags:
• The input tag type is checked. Type errors are fatal errors.
• Processing of additional information:
The status byte is required to display warnings and errors. All warnings and errors are added to the out-
going indication. If the incoming indication is marked as INVALID, the outgoing indication is also marked
as INVALID. Each modified item of PAS information starts the processing of the value. The time stamp
of the incoming PAS information is copied to the outgoing information.
• If no error status was determined by the processing of additional information, the value is calculated. An
overflow during calculation is detected as an error and the corresponding error status is set.
Error processing
Compound block
Compound blocks extend a CFC and provide for the consistent structuring a CFC. These blocks can be used
in order to significantly extend the size of a CFC. Consider the following aspects:
• When copying a compound block, the entire logic (CFC code) is copied, i. e. changes in a copied block
do not automatically influence all copied instances (in contrast to function blocks or functions).
• By copying a compound block, the code of the POU is doubled with regard to the logic behind the block.
However, a POU must not exceed the code size of 64 kilobytes in compiled state!
• Compound blocks cannot be exported!
• They must be considered like a GOTO in high-level languages and should only be used if no other option
can be applied for the extension or wrapping of functions.
• 90% of the compound blocks used in existing projects are not required and could be replaced through an
optimized logic or through the use of function blocks / functions providing significant benefits in this con-
text.
Export
To export a program:
✧ Select the program in the project browser of the SICAM PAS SoftPLC UI.
✧ Right-click the program and then select Properties from the context menu.
The Save as window opens.
Import
To import a program:
✧ In the SICAM PAS SoftPLC UI, click on File > Import File.
The imported file is shown in the project navigator.
NOTE
The interconnection via the margin bar is an integral part of the CFC program. It is imported or exported auto-
matically together with the program.
NOTE
If a mere code file is imported without the related POU file, the code file must be opened once after the import
in order to perform a manual syntax check. This creates the POU file.
TCP is the default driver and permanently set on the local computer.
CFC17.tif
✧ In the Connection Setup window, click on Edit. The Edit Connection window opens.
CFC18.tif
EditResourceProperties.tif
If system redundancy has been defined via the related parameters, the redundant SoftPLCs are operating in a
redundancy mode which slightly differs from non-redundant operation.
Although both SoftPLCs are provided with up-to-date process data and compute the parameterized logic, the
standby SoftPLC does not initiate any process outputs: Interlock requests always get a positive response, but
are suppressed in the application layer of the SoftPLC application. Since this occurs in the application layer,
the actual logic is, however, not influenced.
In the optimal case that both systems start up almost simultaneously, the states in the logics will always be al-
most identical. The restriction ’almost’ means that slight time deviations can nevertheless occur, and this is
even generally the case with a non-realtime operating system.
Since optimal parallel operation is not always possible, deviations can occur in the logics because the logics
are working with different process values or value histories. For example, it is possible that a setpoint value was
defined while the standby SoftPLC was not active due to maintenance work and therefore unable to realize
these value changes.
If system redundancy has been defined via the related parameters, the persistent data of the SoftPLC, i.e. the
so-called RETAIN data, is synchronized by the master SoftPLC upon the startup of the standby SoftPLC. This
means that up-to-date, persistent values stored in the master SoftPLC are transmitted to/received from the
standby SoftPLC. This is particularly important for setpoint values and the states of finite state machines in or-
der to ensure their synchronism even if the two systems did not start up parallely or if one of them has been
inactive for a long time.
NOTE
Be aware that - even in case of redundancy - a startup update of the process values is performed only for Soft-
PLC messages. This means that the current images of setpoint values (marker commands), derived com-
mands, messages generated by the SoftPLC and group indications are not available for the non-process
controlling SoftPLC (standby SoftPLC) during the startup phase! A synchronization of these values must there-
fore always be performed with persistent data (RETAIN data)!
A block type consisting of three instances, for example, includes one code segment (same code), one initial
data segment (same internal pre-assignments) and three data segments (i.e. the instance data).
NOTE
At the end of the compilation process, the compiler outputs the total size of the resource and the reserved data
segments. This output includes all segments and the additional memory required on the controller for internal
segments, segment tables, etc.
The compiler shows that maximum segment sizes have been exceeded.
Only in native code it is possible to exceed the limit of 64 kilobytes for code segments by combining several
code segments. This is performed automatically by the compiler of the programming system. The optimization
of the task or resource must be set to "speed".
Code size
The following rules must be observed in order to achieve an optimal code size:
• Use the data type which meets the requirements of the functionality and has the lowest possible memory
requirements, refer to Data Types According to IEC 61131, page 270.
• Use function blocks instead of compound blocks (chart-in-chart technology) and therefore swap out the
code from program POUs into function blocks.
Performance
NOTE
Assuming that different instances are created for each type used, three segments per type are required (code,
data, initial data). If several instances of the same type are created, only one further segment per instance is
required (data).
When compiling into native code, a native code segment is created for each CS. An average number of three
segments per instance is therefore assumed.
Overview
This chapter explains the SICAM PAS blocks of the command block group. They are used for the creation and
editing of commands. The examples below illustrate how to use the individual blocks.
Contents
Command jobs
Marker commands
The system-internal command is a type of marker command. They are set for specifying the information value
of system-internal objects, e. g.:
• for parameter changeovers or for the clearing/pre-assignment of metered values
CFC view
PAS_CRCOM.tif
3.2.1 Function
Based on Boolean input signals, the PAS_CRCOM block creates command structures (CM) for the derivation
of commands. The command derivation depends on the input connection of the block. Three inputs (one indi-
cation input, two Boolean inputs) are available, one of which must be connected.
Creating a command
The command block is created on the output depending on the selected input:
• INDIC
Depending on the configuration of the INVERT input, INDIC creates a command block upon the rising
edge (RAISED indication, INVERT = FALSE) or clearing edge (CLEARED indication, INVERT = TRUE)
of a single- or double-point indication.
• SEND
creates a command block only with a rising edge, i. e. when the value of the input changes from FALSE
to TRUE.
• CHANGE
always creates a command block when the change marker changes, i. e. from FALSE to TRUE or from
TRUE to FALSE.
Command derivation
To derive the created command, the OUTPUT output must be connected with the COMM input of a down-
stream PAS_COMMCP, PAS_ACQ (restoring of metered values) or PAS_SELC block (derivation of SoftPLC-
internal commands). In order to connect more than one PAS_CRCOM to a command block, a PAS_MUXTEL
block must connected between them (refer to PAS_MUXTEL).
Additionally, the IN input of this downstream block must be connected to the left-hand margin bar of the Soft-
PLC.
The OUT output for PAS_COMMCP must be connected to the right-hand margin bar - CFC/output tag - ST/
STL of the SoftPLC.
3.2.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is for- TRUE
warded to the ENO output.
FALSE = block disabled
TRUE = block enabled
INVERT BOOL Configuration input for inverting the indication status FALSE
FALSE = no inversion
RAISED indication → command ON
CLEARED indication → command OFF
TRUE = inversion
RAISED indication → command OFF
CLEARED indication → command ON
TRIGGER BOOL The indication input is used as a trigger for the command FALSE
output. The value of the command is predefined by the
DW_VALUE and BO_VALUE inputs.
NOTE
The indication value does not influence the command value.
SEND BOOL If the value of the input changes from FALSE to TRUE (rising FALSE
edge), a command block (CM) is created.
NOTE
Must be connected if CHANGE is not connected and must
not be connected if CHANGE or INDIC are connected!
NOTE
Must be connected to the CHANGE output of another block if
SEND is not connected. Must not be connected if SEND or
INDIC are connected!
NOTE (With
Must be configured! command 19)
DW_VALUE DWORD The value is interpreted as a double word (32 bits) and the 0
command is updated for this value.
NOTE
Must be configured! If the value of the command derivation is
not determined via the created indication (INDIC).
Caution:
BO_VALUE
influences the
least significant
bit of
DW_VALUE!
NOTE
The internal system time is entered if the input is not as-
signed.
Outputs
NOTE
Must be connected to the COMM input of a downstream command block!
3.2.3 Example
Command derivation
In the example below, the Boolean logic controls the command derivation. When the Boolean signal rises, a
switch ON or OFF occurs after each second Boolean signal.
Beispiel1_BoolSignal.tif
Description
PAS_CRCOM block
The Boolean signal is transmitted via the INDIC input of the block.
The EN input is assigned the value TRUE, the CAUSE input is assigned 19, the INITCAT input is assigned 4
and the VALTYPE input is assigned 14.
The command derivation is performed via the OUTPUT output to the COMM input of the PAS_COMMCP block.
PAS_COMMCP block
Persistent command
Beispiel2.tif
Description
PAS_CRCOM block
The following inputs are assigned related values: EN input=TRUE, CAUSE input=19, INITCAT input=4,
VALTYPE input=13.
An indication is present directly on the INDIC input. Depending on whether the indication has been switched
ON or OFF, a persistent command is transmitted to the PAS_COMMCP block via OUTPUT. An inverted output
is performed if the INVERT input is assigned TRUE.
PAS_COMMCP block
CFC view
PAS_COMMCP.tif
3.3.1 Function
The PAS_COMMCP block has three tasks:
1. Transmission of commands in case of a command derivation (in combination with PAS_CRCOM,
PAS_STATE)
2. Interlock check for the PAS distribution system (DSI server; the DSI server requests whether the LOCK,
REL_ON, REL_OFF inputs allow for a switching of the command)
3. Configuration of switchgear interlocks in the SoftPLC.
In this context, the block receives a message when commands are connected externally. It updates the OK,
ERR and ACTIVE outputs accordingly.
The PAS_COMMCP block is used for all commands (slave functionality) transmitted by the SoftPLC (to other
drivers, command derivation) as well as for the configuration of interlocks.
The ACTIVE, OK and ERR outputs are updated both for commands triggered by the SoftPLC, e. g. command
derivation, and for commands which are not triggered by the SoftPLC, e. g. HMI.
The PAS_COMMCP block detects whether and which commands have been activated.
In SICAM PAS, the central DSI server monitors the command process. It ensures a consistent command exe-
cution and has a monitoring time (SICAM PAS UI Configuration). Monitoring times are not configured in the
SoftPLC!
The PAS_COMMCP block ensures the processing of command interlocks. The interlock is independent of the
command processing. If a command which is to be connected as TO BE LOCKED has been configured in the
PAS system, the DSI server transmits a request to the SoftPLC in order to find out whether the command has
been released. A PAS_COMMCP block must be specified for this command in the SoftPLC. It processes the
request and checks the LOCK, REL_ON and REL_OFF inputs. If they allow switching, the DSI server receives
a positive acknowledgement. If this is not the case, the response is negative. It is not relevant for the interlock
function whether a command is active or not.
NOTE
All slave commands and interlocks are specified using the PAS_COMMCP block.
3.3.2 Connections
Inputs
NOTE
For the general interlock, the LOCK input must be connected to one
of the ION, IOFF or NOT_DBI outputs of an INDIC block (depending
on the circuit logic) which determine the current status of a switch.
If TRUE is present on the LOCK input, it is locked and an incoming
command job receives a negative acknowledgement.
All commands are accepted if the LOCK input is not connected.
NOTE
Can be connected to the OUTPUT output of a PAS_CRCOM block.
Outputs
OUT PASCOMMANDBLOCK The output sets a pointer to the address of a command structure
all command types (PAS information). It consists of several process data structure blocks.
NOTE
Must be interconnected, i. e. the output is connected to the right-hand
margin bar of the CFC!
OK BOOL After a successful command (COE+), this output is TRUE during one poll.
ERR BOOL After an incorrect command (COE-), this output is TRUE during one poll.
DIAG WORD This output visualizes Diagnostic Information (refer to Appendix A.2).
3.3.3 Miscellaneous
Error processing
Non-connected inputs are checked. If inputs which must be connected in order to ensure the proper functioning
of the block are not linked or linked incorrectly, no information is processed in the block. The error information
is output on the DIAG diagnostic output (refer to Appendix A.2).
3.3.4 Example
For a PROFIBUS FMS bay device, a command must be derived for two switching sequences. The command
derivation is connected via the COMM input and the PAS_MUXTEL block.
Beispiel3.tif
Description
PAS_MUXTEL block
The switching commands of the switching sequences are present on the IN1 and IN2 inputs. The
PAS_MUXTEL inputs feature an OR logik, i. e. as soon as a switching command is present, it is forwarded via
the OUT output to the COMM input of a downstream command block.
PAS_COMMCP block
Via its COMM input, the block receives the derived command of the switching sequences. As soon as a switch-
ing command arrives, it is forwarded via the OUT output, i. e. the output is linked to an item of PAS information.
NOTE
The derived commands are only issued if the interlock conditions do not prevent this (LOCK, REL_ON,
REL_OFF).
Each slave command mapped to the SoftPLC automatically uses the DSI server interlock check. Consequently,
no interlock check can be performed if a slave command is mapped to the SoftPLC without being connected
to a PAS_COMMCP block.
The following rule applies: All slave commands of the SoftPLC must be interconnected with a PAS_COMMCP
in a program.
CFC view
PAS_COMMCP_EX.tif
3.4.1 Function
Apart from one exception, a PAS_COMMCP_EX block works according to the same principles as a
PAS_COMMCP block (see chapter 3.3). Using the PAS_COMMCP_EX block, an additional switchgear inter-
lock can be made by means of the originator (refer to Originator category). If the command is triggered by an
originator which does not correspond to the one on the REL_ICAT input or to one of the specified exceptions,
the command receives a negative acknowledgement with the additional cause Violation of Switching Au-
thority (99).
The originators SoftPLC (4) and Originator irrelevant (0) are never considered for the additional switchgear
interlock.
3.4.2 Connections
Inputs
NOTE
For the general interlock, the LOCK input must be connected
to one of the ION, IOFF or NOT_DBI outputs of an
INDIC block (depending on the circuit logic) which determine
the current status of a switch.
If TRUE is present on the LOCK input, it is locked and an in-
coming command job receives a negative acknowledgement.
All commands are accepted if the LOCK input is not connect-
ed.
NOTE
The originators SoftPLC (4) and Originator irrelevant (0)
are never considered for the additional switchgear interlock.
NOTE
Can be connected to the OUTPUT output of a
PAS_CRCOM block.
Outputs
OUT PASCOMMANDBLOCK The output sets a pointer to the address of a command structure
all command types (PAS information). It consists of several process data structure blocks.
NOTE
Must be interconnected, i. e. the output is connected to the right-hand
margin bar of the CFC!
OK BOOL After a successful command (COE+), this output is TRUE during one poll.
ERR BOOL After an incorrect command (COE-), this output is TRUE during one poll.
3.4.3 Miscellaneous
Error processing
Non-connected inputs are checked. If inputs which must be connected in orderto ensure the proper functioning
of the block are not linked or linked incorrectly, no information is processed in the block. The error information
is output on the DIAG diagnostic output (refer to Appendix A.2).
CFC view
PAS_SELC.tif
3.5.1 Function
This block is used for SoftPLC-internal commands such as marker commands, setpoint commands (e. g. com-
mand with setpoint input to the SoftPLC logic) or commands for starting a switching sequence. It cannot be
used for slave commands.
The block sets a trigger pulse for each valid pending command. This pulse is reset during the next trigger of
the task. To obtain a trigger pulse only for a positive or negative edge, an AND_operation must be performed
with the BO_VALUE output.
A command is terminated if either the TERM_POS input (command successful) or the TERM_NEG input
(command unsuccessful) is set to TRUE. This has the advantage that the command does not need to be ter-
minated in the same task execution (e. g. switching sequence) in which the command was triggered. The com-
mand is only terminated when the signal rises.
If TERM_POS is set to TRUE, each command can still be terminated positively in the same task execution.
After the termination of a command, the ACTIVE output switches back to FALSE.
To prematurely cancel running commands which have not yet received positive or negative acknowledgement,
the PAS_SELC block can process cancel commands. The current command is canceled by means of a cancel
command. The ACTIVE output is set to FALSE and the TRM_TRIG output for this task execution is set to
TRUE.
The cancel option ensures that the PAS_SELC block is suitable for switching sequence commands.The actual
switching sequence is realized by means of the PAS_STATE and PAS_TRANS blocks. The PAS_SELC block
initiates this network.
3.5.2 Connections
Inputs
NOTE
Can be interconnected with the ACTIVE output of other
command blocks!
NOTE
Can be connected to the OUTPUT output of a
PAS_CRCOM block!
NOTE
Must be connected!
Outputs
DIAG WORD This output visualizes Diagnostic Information (refer to Appendix A.2).
3.5.3 Miscellaneous
Error processing
Non-connected inputs are checked. If inputs which must be connected in order to ensure the proper functioning
of the block are not linked or linked incorrectly, no information is processed in the block. The error information
is output on the DIAG diagnostic output (refer to Appendix A.2).
3.5.4 Example
Refer to Chapter 11.4, Transformer Switching,
refer to Chapter 11.2, Switching Sequences of the SoftPLC
CFC view
PAS_SELC_EX.tif
3.6.1 Function
Apart from one exception, a PAS_SELC_EX block works according to the same principles as a PAS_SELC
block (see chapter 3.5). Using the PAS_SELC_EX block, an additional switchgear interlock can be set by spec-
ifying an originator (refer to Originator category). If the command is triggered by an originator which does not
correspond to the one on the REL_ICAT input or to one of the specified exceptions, the command receives a
negative acknowledgement with the additional cause Violation of Switching Authority (99).
The originators SoftPLC (4) and Originator irrelevant (0) are never considered for the additional switchgear
interlock.
3.6.2 Connections
Inputs
NOTE
Can be interconnected with the ACTIVE output of other
command blocks!
NOTE
The originators SoftPLC (4) and Originator irrelevant (0)
are never considered for the additional switchgear interlock.
NOTE
Can be connected to the OUTPUT output of a
PAS_CRCOM block!
NOTE
Must be connected!
Outputs
DIAG WORD This output visualizes Diagnostic Information (refer to Appendix A.2).
3.6.3 Miscellaneous
Error processing
Non-connected inputs are checked. If inputs which must be connected in order to ensure the proper functioning
of the block are not linked or linked incorrectly, no information is processed in the block. The error information
is output on the DIAG diagnostic output (refer to Appendix A.2).
Overview
This chapter describes the SICAM PAS automation blocks of the indication processing group. They are divided
into two groups: Indication and comparison blocks. They are used to create and edit indications. The examples
in this chapter illustrate how to use these blocks.
Contents
Tasks
NOTE
An overview of the possible input values and their significance is provided in Appendix A.1.
CFC View
PAS_CRI.tif
4.2.1 Function
Single-point, double-point and fleeting indications are created by means of the PAS_CRI block. The indication
created by the block is always transmitted when the value on the SEND or CHANGE input changes.
4.2.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
SEND BOOL Creates an indication upon the change from FALSE to TRUE (point- FALSE
er to PAS information)
NOTE
Must be connected if CHANGE is not connected and must not be
connected if CHANGE is connected!
NOTE
Must be connected if SEND is not connected and must not be con-
nected if SEND is connected!
NOTE
Must be configured!
TIMEHIGH WORD Time stamp If the inputs are left free, the in- 0
(bits 32 to 47) ternal system time is entered.
Outputs
INDIC PASDATABLOCK The indication structure block is located on this output. (pointer to
SP, DP, EVENT PAS information)
NOTE
Must be connected, i. e. the output is connected with the right-hand CFC margin
bar or set as output tag in the ST program!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
4.2.3 Miscellaneous
Error processing
If you specify an incorrect indication type, the default value is set for the type. The INVALID bit is set to TRUE
in the status byte.
4.2.4 Example
The example below illustrates how an indication is created from the linkage of four Boolean values.
Bsp_ANDI_CRI.tif
Description
ANDI block
The inputs of the PAS_ANDI block are assigned PASDATABLOCK indications. The output signal of the
PAS_ANDI block is assigned to the SIGNAL_1 input of the PAS_CRI block.
PAS_CRI block
An indication is created if the signal on the SIGNAL_1 input changes. After its creation, this indication is con-
nected to the right-hand margin bar (or to the input of the downstream block).
Further examples
CFC view
PAS_FI.tif
4.3.1 Function
For each incoming indication of an indication group, this block creates a fleeting indication with a time stamp,
a status and the spontaneous cause at the input.
However, indications of the indication group that arrive at the input with the bay block status or with the startup
general interrogation cause are not evaluated.
4.3.2 Connections
Inputs
Outputs
SIZE WORD Number of indications of the indication group arriving at the input
MARKER DWORD Change counter incremented with each new fleeting indication on the output
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
CFC view
PAS_TSP.tif
4.4.1 Function
The PAS_TSP block converts double-point indications into single-point indications. The time of the initiating in-
dication is applied for the result indication.
4.4.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
Outputs
INDIC PASDATABLOCK The converted indication structure block is assigned to this output.
SP
NOTE
Must be connected, i. e. the input is linked to an item of PAS information!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
4.4.3 Miscellaneous
Error processing
A fatal error is output if the inputs are connected to the incorrect indication type (e. g. fleeting indication).
4.4.4 Example
In the chart below, a double-point group indication is converted into a single-point indication.
Bsp_ANDI_TSP.tif
Description
PAS_ANDI block
Double-point indications appear on the IN1, IN2, IN3 and IN 4 inputs of the PAS_ANDI block. The indications
are linked logically in the block. The result, a double-point group indication, is output as an indication structure
block on the INDIC output.
PAS_TSP block
The indication structure block on the output of the PAS_ANDI block is connected to the IN input of the
PAS_TSP block. The incoming double-point indication is converted onto a single-point indication and output as
PAS information via the INDIC output.
CFC view
PAS_ANDI.tif
PAS_ORI.tif
4.5.1 Function
PAS_ANDI
The PAS_ANDI block realizes AND operations for group indications of single-point and/or double-point indica-
tions. The block can perform an AND operation of up to 4 indications at the same time. If several indications
exist, it can be cascaded.
AND operation
The group indication is set as soon as all indications are present (RAISED). When the first of the linked indica-
tions disappears, the group indication is cleared, i. e. set to CLEARED. The time of the indication which was
present last or the time of the indication which disappeared first is applied for the result indication.
The startup indication is transmitted as soon as the startup indications of all inputs have been received.
The status of the raising group indication corresponds to the OR link of the state of all indications on the inputs.
Exception: If at least one of the transmitted CLEARED indications has the topical status, the result indication
is also assigned the topical status.
PAS_ORI
The PAS_ORI block realizes OR operations for group indications of single-point and/or double-point indica-
tions. The block can perform an OR operation of up to 4 indications at the same time. If several indications
exist, it can be cascaded.
The blocks link the logical values of indications. For example, they form one logical value (e. g. 01 becomes
FALSE) from the value of a double-point indication and perform a logical link for this value. A pointer to the
result indication (PAS information) is output.
The result indication always has the "double-point indication" type. The cause of the transmission (CAUSE) is
always set to SPONTANEOUS for a result indication.
OR operations
The group indication is set as soon as the first linked indication is present (RAISED). When the last of the linked
indications disappears, the group indication is cleared, i. e. set to CLEARED. The time of the indication which
raises first or is cleared last is applied for the result indication.
The startup indication is transmitted as soon as the startup indications of all inputs have been received.
The status of the cleared group indication corresponds to the OR link of the states of all indications on the in-
puts.
Exception: If at least one of the transmitted RAISED indications has the topical status, the result indication is
also assigned the topical status.
4.5.2 Connections
Inputs
NOTE
Must be connected, i. e. the input is linked to an item of
PAS information!
up to
NOTE
Must be connected, i. e. the input is linked to an item of
PAS information!
Outputs
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
EN_EVENT BOOL TRUE in the case of a value change (BVALUE), otherwise FALSE
INDIC PASDATABLOCK The address of the result indication is present on this output.
DP
NOTE
Must be connected, i. e. the input is linked to an item of PAS information!
4.5.3 Miscellaneous
Error processing
4.5.4 Example
Refer to Example of a PAS_ANDI and PAS_TSP block, page 93,
refer to Example of a PAS_ANDI, PAS_ORI and PAS_INVER block, page 100.
CFC view
PAS_INVER.tif
4.6.1 Function
With the PAS_INVER block, you can invert single-point and double-point indications, i. e. RAISED indications
are converted into CLEARED indications and vice-versa. Incoming indications are checked for validity before
they are processed.
4.6.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
Outputs
INDIC PASDATABLOCK The address of the result indication is present on this output.
DP
NOTE
Must be connected, i. e. the input is linked to an item of PAS information!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
4.6.3 Miscellaneous
Error processing
4.6.4 Example
The example below shows a logical link of five error indications. The logical result of the outgoing indication
may only be TRUE if the following conditions are met:
• At least one of the first four error indications is set to TRUE.
• The fifth error indication must be set to FALSE.
Bsp_ANDI_ORI_INVER.tif
Description
PAS_ORI block
The PAS_ORI block is assigned with the four error indications. If at least one of the error indications is TRUE,
the indication on the INDIC output is assigned the logical value TRUE.
PAS_INVER block
The PAS_INVER block is activated with EN = TRUE. The IN input of the PAS_INVER block is connected to the
fifth error indication. The inverted indication is present on the INDIC output, i. e. the logical value of the indica-
tion is inverted.
PAS_ANDI block
The PAS_ANDI block checks whether both above-mentioned conditions are met. If the conditions are met, the
outgoing indication on the INDIC output receives the logical value TRUE; otherwise it is FALSE.
CFC view
PAS_DELAYI.tif
4.7.1 Function
This block filters indications and processes fleeting indications. Via the Boolean inputs RAISED_I, CLEAR_I
and UNDEF_I, you can specify for which indication criteria the filter time responds - except for fleeting indica-
tions which can only be filtered without a filter time.
If the filter time is set to zero, the indication is suppressed when the defined filter criterion appears.
4.7.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on TRUE
to the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Responds to specified filter criteria.
NOTE
Only valid for double-point indications.
UDF_MODE BYTE This input specifies how the intermediate position is output: 0
0 = output intermediate position without change
1 = output intermediate position as 00
2 = output intermediate position as 11
Outputs
INDIC PASDATABLOCK The address of the result indication is present on this output.
SP, DP
NOTE
The data type of the result indication (SP or DP protocol type) must correspond
to the data type of the incoming indication on the IN input.
Must be interconnected, i. e. the input is linked to an item of PAS information!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
4.7.3 Miscellaneous
Error processing
4.7.4 Example
The example below displays the connection and parameterization of the PAS_DELAYI block for filtering a
RAISED indication. This indication is forwarded after a specified period of time.
Bsp_PAS_DELAYI.tif
Description
The incoming indication is present on the IN input. A pending period of 10 ms is defined on the TIME_IN input.
To filter RAISED indications, the RAISED_I input must be assigned TRUE.
As the CLEAR_I (CLEARED indication) and UNDEF_I (intermediate position indication) inputs are defined
FALSE, only RAISED indications are filtered. They are output on the INDIC output after a period of 10 ms.
CLEARED and intermediate position indications are not considered, i. e. they are forwarded immediately
(INDIC output) without pending for a certain period of time.
CFC view
PAS_GROUPI.tif
4.8.1 Function
The PAS_GROUPI block is a group indication block. It enables the rapid parameterization of a group indication
with an OR operation.
The parameterization is performed via groups in SICAM PAS UI.
The individual values in an automation program do not need to be connected. Only a connection from the PAS-
GROUP data type to a PAS_GROUPI block is performed.
The block processes single-point and double-point indications. If one of the values is ON, the BVALUE output
value is TRUE; otherwise it is FALSE. If a change occurred with the ON value at the time of the block call, the
ALARM output toggles. This does not necessarily mean that the BVALUE output value has changed!
If a BVALUE value change exists or if a value has changed during startup, a new outgoing indication is gener-
ated (INDIC).
With each new outgoing indication, EN_EVENT is set to TRUE for this call of the automation program.
The status of the cleared group indication corresponds to the OR link of the states of all indications on the in-
puts.
Exception: If at least one of the transmitted RAISED indications has the topical status, the result indication is
also assigned the topical status.
NOTE
Indications with the not topical and manually update status are ignored by the PAS_GROUPI block and not
included in the group indication (refer to Chapter 2.2, Startup Behavior of the SICAM PAS SoftPLC).
The Bay Block Active status is transmitted only once. If a Bay Block Active indication is transmitted after-
wards, no group indication processing is performed until all indications of the group have reset the Bay Block
Active status.
As soon as an indication of the group is transmitted with a cause other than General Interrogation, the cause
of the group indication is set to spontaneous. The new group indication is assigned the time stamp of the caus-
ing indication.
During startup, the block creates a cleared double-point indication with the General Interrogation cause and
the not topical and manually updated status and the time stamp of the initialization of the group indication
(first call of the corresponding PAS_GROUPI block).
4.8.2 Connections
Inputs
Outputs
ALARM BOOL Toggling with new RAISED indication with the spontaneous cause
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
CFC view
PAS_CMPT.tif
PAS_CMPTC.tif
4.9.1 Function
The following blocks are used to compare transformer tap indications:
• Comparison of two transformer tap indications
• Comparison between a transformer tap indication and a constant
PAS_CMPT
This block compares two transformer tap indications.
Depending on the comparison status, the Boolean outputs are set to TRUE or FALSE (TRUE-active).
The corresponding indication is derived from the result of a comparison of the transformer tap indications by
means of an interconnection with the CRI block. The time stamp is applied from the transformer tap indication
which has been received last.
PAS_CMPTC
This block compares a transformer tap indication with a constant.
Depending on the comparison status, the Boolean outputs are set to TRUE or FALSE (TRUE-active).
The corresponding indication is derived from the result of a comparison of the transformer tap indications by
means of an interconnection with the CRI block. The time stamp is applied from the transformer tap indication
which has been received last.
4.9.2 Connections
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
IN1 PASDATABLOCK The address of a first transformer tap indication is applied to this 0
ST input.
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
IN2 PASDATABLOCK The address of a second first transformer tap indication is applied 0
ST to this input.
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INDIC PASDATABLOCK The address of a transformer tap indication is applied to this input. 0
ST
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
CONST BYTE This parameter specifies the constant with which the transformer 0
tap indication is compared.
NOTE
Must be configured!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
4.9.3 Miscellaneous
Error processing
Indications with an incorrect type or non-connected inputs cause a fatal error. Indications with the correct type
cause an error if they include erroneous information. The Boolean outputs are set to FALSE in both cases.
4.9.4 Example
The example below illustrates the monitoring of two transformers. An indication is displayed if the transformer
taps of the two transformers are identical.
Bsp_PAS_CMPT_CRI.tif
Description
PAS_CMPT block
A transformer tap indication from Transformer 1 is present on the IN1 input. A transformer tap indication from
Transformer 2 is present on the IN2 input. If the two transformer tap indications are identical, the output is
EQUAL = TRUE.
PAS_CRI block
The EQUAL output of the PAS_CMPT block is connected to the SIGNAL_1 input of the PAS_CRI block. Via
the TIMEHIGH and TIMELOW inputs, it receives the time stamp of the transformer tap indication which was
received last in the PAS_CMPT block.
The type of the derived indication (single-point indication = 3) is defined on the INDICTYP input. The indication
is issued on the INDIC output.
CFC view
PAS_CMPB.tif
PAS_CMPB.tif
4.10.1 Function
The following blocks are used to compare bit pattern indications:
• Comparison of two bit pattern indications:
The absolute values of bit pattern indications are compared. For example, bit pattern 1001 (= 9) is greater
than 0111 (= 7).
• Comparison between a bit pattern indication and a constant
PAS_CMPB
This block compares two bit pattern indications.
Depending on the comparison status, the Boolean outputs are set to TRUE or FALSE (TRUE-active).
To derive an indication from the result of the evaluation, connect a PAS_CRI block downstream. The time stamp
is applied from the bit pattern indication which has been received last.
PAS_CMPBC
This block compares a bit pattern indication with a constant.
Depending on the comparison status, the Boolean outputs are set to TRUE or FALSE (TRUE-active).
To derive an indication from the result of the evaluation, connect a PAS_CRI block downstream. The time stamp
is applied from the bit pattern indication which has been received last.
4.10.2 Connections
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
IN1 PASDATABLOCK The address of a first transformer tap indication is applied to this 0
BO input. First bit pattern indication created.
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
IN2 PASDATABLOCK The address of a second transformer tap indication is applied to this 0
BO input. Second bit pattern indication created.
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INDIC PASDATABLOCK The address of a bit pattern indication is applied to this input. 0
BO
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
CONST DWORD This parameter specifies the constant with which the bit pattern in- 0
dication is compared.
NOTE
Must be configured!
4.10.3 Miscellaneous
Error processing
Indications with an incorrect type or non-connected inputs cause a fatal error. Indications with the correct type
cause an error if they include erroneous information. The Boolean outputs are set to FALSE in both cases.
4.10.4 Example
The example below illustrates the comparison between the setpoint value and the actual value of bit pattern
indications. An indication is derived from the result on the EQUAL output by means of a connection with a
PAS_CRI block.
Bsp_PAS_CMPB_CRI.tif
Description
PAS_CMPB block
The setpoint value is located on the IN1 input, whereas the actual value is present on the IN2 input. If the bit
pattern values are identical, the output is EQUAL = TRUE.
PAS_CRI block
The EQUAL output of the PAS_CMPB block is connected to the SIGNAL_1 input of the PAS_CRI block. The
CHANGE input is defined with TRUE, i. e. an indication is created if the signal on the SIGNAL_1 input changes.
Via the TIMEHIGH and TIMELOW inputs, it receives the time stamp of the bit pattern value which arrived last
in the PAS_CMPB block.
The type of the derived indication (single-point indication = 3) is defined on the INDICTYP input. The indication
is issued on the INDIC output.
CFC view
PAS_INDIC.tif
4.11.1 Function
The status and state of single-point and double-point indications are displayed via the PAS_INDIC block. Inter-
lock links are made with the Boolean outputs by means of Boolean logic blocks.
The IOFF, ION, NOT_DBI, DBI0 and DBI1 outputs are set to TRUE or FALSE depending on the state of the
indication on the input of the PAS_INDIC block (e. g. indication via the switching state of a switching device).
If the incoming indication is a single-point indication, the DBI0 and DBI1 outputs are not assigned, i. e. they are
set to FALSE.
4.11.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INDIC PASDATABLOCK The address of an indication structure block is applied to this input. 0
SP, DP
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
Outputs
4.11.3 Miscellaneous
Error processing
Non-connected inputs are checked. If inputs which must be connected to ensure the functionality of the block
are not linked, no information is processed in the block.
4.11.4 Example
Switchgear interlocking
In the example below, Boolean signals are derived from a pulse command for the logical control of an interlock.
Beispiel5.tif
Description
PAS_INDIC
An incoming indication is present on the INDIC input of each of the two PAS_INDIC blocks. The EN input is
assigned TRUE for each of them. The ION output of the first and the second PAS_INDIC block is connected to
the IN0 or IN1 input of the Boolean block.
AND block
PAS_COMMCP
The Boolean signal is received on the _LOCK input and output via the OUT output.
CFC view
PAS_GROUPINIDIC.tif
4.12.1 Function
The SICAM PAS_GROUPINDIC firmware block is used to access individual indications of an indication group.
Additionally, it detects which indication of the input group has changed. With this block, special group indication
blocks can be created in one of the languages supported by IEC 61131-3, i.e. CFC, ST or STL.
Method of operation
A specified indication group is assigned to the IN input of the block. The SIZE output indicates how many indi-
cations the group consists of.
As soon as one indication in the group changes on the input, the block indicates this by toggling the CHANGE
output and by the incrementation of the MARKER output. Additionally, the index of the changed indication is
shown on the CHANGE_IDX output.
The changed indication is reflected on the I_... outputs through another call of the block with the index on the
SELECT input.
Access to the individual indications functions according to the same principles as the indexing of an array in
other programming languages (the arrays or indices start with 1).
NOTE
The SICAM PAS SoftPLC initiates a startup GI (general interrogation) of all typical indications (apart from fleet-
ing indications) in order to initialize all SICAM PAS firmware blocks which process these indications. This ini-
tialization is not deactivated by the PAS_GROUPINDIC block. All indications of the input group, apart from
fleeting indications, are assigned the General Interrogation cause and the not topical and manually updat-
ed status and transmitted to the SoftPLC logic.
4.12.2 Connections
Inputs
Outputs
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
SIZE UINT Number of indications of the indication group arriving at the input
Overview
This chapter describes the SICAM PAS automation blocks for measured-value and metered-value processing.
They are divided into the following groups:
• Measured-value / metered-value blocks
• Arithmetical blocks
• Comparison blocks
The examples in this chapter illustrate the use of more complex blocks.
Contents
The blocks are used to process measured and metered values independently of the acquisition sources (bay
and protection devices, internally formed measured and metered values).
NOTE
An overview of the possible input values and their significance is provided in Appendix A.1.
Bay and protection devices of the SIPROTEC series as well as bay and protection devices connected via
PROFIBUS FMS transmit the measured values standardized to a defined 100% reference value:
With the IEC61850 protocol, measured values are transmitted as INT32 or as FLOAT32 depending on the de-
vice type.
The 100% absolute value corresponds to the maximum value range of the output variable, e. g.:
20 mA 20
The definition of the 100% acquisition value depends on the maximum transmission value and on the reference
variable of the acquisition device.
CFC view
PAS_NLC.tif
5.3.1 Function
The PAS_NLC block is used to linearize acquisition values which have been read in. Some measuring trans-
ducers have a non-linear measuring transducer characteristic, i. e. a certain measuring range is mapped at a
high resolution (zoom effect), whereas the remaining range has a significantly lower resolution.
The PAS_NLC block can linearize the acquisition values of measuring transducer characteristics with different
measuring resolutions (up to 5 salient points), e. g.:
• Stretched start range
• Stretched end range
• Zero offset
• Salient points
mvOUTPUT
120%
1320
100%
KP3
20%
KP2
mvINPUT
mvOUTPUT
120%
1320
100%
KP3
80%
KP2
mvINPUT
Zero offset
mvOUTPUT
120%
1320
100%
KP2
80%
mvINPUT
5 salient points
mvOUTPUT
120%
1320
100% KP5
55% KP4
28%
KP3
6% KP2 mvINPUT
5.3.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
BREAK_NR BYTE This parameter specifies the number of salient points. Up to 5 can 0
be defined.
SYMMETRY BYTE This parameter specifies the characteristic symmetry (zero offset). 0
0 = characteristic only in the 1st quadrant
1 = characteristic symmetrical to zero point
2 = characteristic symmetrical to y-axis
NOTE
Must be configured!
NOTE
Must be configured!
NOTE
Must be configured!
NOTE
Must be configured!
Outputs
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
5.3.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
CFC view
PAS_ACQI.tif
5.4.1 Function
Using the PAS_ACQ block, you can realize metered-value processing of counter additions within the SoftPLC.
Absolute metered values as input values are rejected by the PAS_ACQ block. The output is performed as a
counter addition, absolute metered value or as a mixed version of both.
The metered value to be processed can be preset, also during operation (32-bit setpoint). The presetting for
the startup is defined separately.
The metered values are added up and restored via telecontrol, HMI or at cyclic intervals. If cyclic restoration
was specified, restore commands can also be processed. However, they are not considered when counting the
restoration processes for the clear cycle (parameterization on the WITH_CLR input) of the internal counter con-
tent, i. e. the PAS_ACQ restores the current counter content without clearing.
NOTE
Exception: When defining the WITH_CLR input with 1 (number of the restoration processes = 1), the counter
content is cleared after each restoration.
5.4.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is for- TRUE
warded to the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
The internal metered value can be predefined during opera-
tion.
NOTE
Must be defined if SEND, COMM is not connected!
Outputs
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
5.4.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
5.4.4 Example
In the example below, a counter addition is restored and cleared at cyclic intervals every 30 minutes (referred
to the full hour).
A start value for the startup is predefined via WinCC.
Bsp_PAS_ACQ.tif
Description
PAS_ACQ block
The block must be defined as follows for the above-mentioned basic conditions:
• The cycle time of 30 minutes is defined on the CYCLE input.
• The WITH_CLR input must be set to 1 in order to reset the metered value after the restoration.
• The STARTVAL input is defined with 5. This is the start value used during the system startup.
The presetting of the counter content, i. e. a 32-bit scheduled value command, is specified on the VALUE input
for the running operation.
The metered value added in the buffers of the PAS_ACQ block is present on the INPUT input. The result of the
addition is output every 30 minutes on the OUTPUT output.
CFC view
PAS_LIMU.tif
PAS_LIML.tif
5.5.1 Function
Use these blocks for monitoring limit values:
• Monitoring of a configurable upper limit
• Monitoring of a configurable lower limit
If the blocks exceed the specified limit, a limit value indication (single-point indication) is triggered or a Boolean
value is produced. A hysteresis can be specified for limit value editing.
PAS_LIMU
This block monitors the configurable upper limit. If a hysteresis has been defined, the violation of the upper limit
is only reset when the measured value or metered value falls below the limit, reduced by the hysteresis value.
Violations of upper limits are output as RAISED indications (otherwise CLEARED indications) or via the Bool-
ean value 1 (otherwise 0).
IN_100_ABS
LIMVALUE
1050
HYSVALUE
1000
SIGNAL
PAS_LIML
This block monitors the configurable lower limit. If a hysteresis has been defined, the violation of a lower limit
is only reset when the measured value or metered value has exceeded the limit value, increased by the hys-
teresis value.
Violations of lower limits are output as RAISED indications (otherwise CLEARED indications) or via the Bool-
ean value 1 (otherwise FALSE).
IN_100_ABS
HYSVALUE
1050
LIMVALUE
1000
SIGNAL
5.5.2 Connections
Inputs
Table 5-5 Inputs of the PAS_LIMU and PAS_LIML limit value blocks
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INPUT PASDATABLOCK Input for measured or metered value (pointer to PAS information) 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
NOTE
Must be defined!
HYSVALUE REAL Hysteresis value, absolute value of the difference to the limit value 0
NOTE
Must be defined for measured values and is irrelevant for metered
values!
IN_100_ABS REAL 100% absolute value, corresponds to the maximum value of the 0
real mesured value.
NOTE
Must be defined for measured values and is irrelevant for metered
values!
Outputs
Table 5-6 Outputs of the PAS_LIMU and PAS_LIML limit value blocks
SIGNAL BOOL Output for the derivation of the limit value indication:
1 = Limit value exceeded
INDIC PASDATABLOCK Output for limit value indication with time stamp of the incoming measured value
SP or metered value (pointer to PAS information)
NOTE
Must be interconnected, i.e. the output is always connected to the right-hand
margin bar of the CFC or set as output variable in the ST program!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
5.5.3 Miscellaneous
Fault processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
5.5.4 Example
The example below illustrates voltage monitoring. An indication is created in case of an overvoltage.
Bsp_PAS_LIMU.tif
Description
PAS_LIMU block
The measured value of the voltage to be monitored is present on the INPUT input.
A RAISED indication is created on the INDIC output whenever the measured value is greater than 9 V. If the
voltage falls below 7 V again (limit value - hysteresis), a CLEARED indication is created on the INDIC output.
CFC view
PAS_AVG.tif
5.6.1 Function
This block provides a mean value formation. Either periodic mean values (mean value formation after N values
each) or continuous mean values (mean value formation over the last N values) can be determined with a fix
number N. The number N is specified on the MEAN_NO input, whereas the mean value type (periodic or con-
tinuous) is specified on the CONTIN input.
To read in a new measured value for the mean value formation, a valid measured value must be connected to
the INPUT input and a Boolean pulse must be triggered on the VAL_TRIG input. In this context, the block does
not evaluate the rising edge, but only the value 1. As a rule, the VAL_TRIG input should be triggered at cyclic
intervals (e. g. via the TIMER_SW block).
If a bay block is defined on the device which produces the measured value, the PAS_AVG block transmits a
new mean value with the value 0 and the bay blocking status. When the bay block is undone, another mean
value is transmitted with the value 0, but with the OK status. The internal mean value formation is reset and
restarted.
The current sum and number of read in values can be read on the VAL_SUM and VAL_CNT outputs (e .g. for
diagnosis or further processing).
With each new mean value which is not transmitted, because of a reset or a bay blocking setting, a Boolean
pulse is output on the VAL_NEW output.
5.6.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
VAL_TRIG BOOL Read-in signal for measured value: If TRUE is present during the FALSE
call of the block, the current measured value for the mean value for-
mation is read in.
MEAN_NO DWORD Number of values for the formation of the mean value. 0
RESET BOOL Reset input. If TRUE is present, the current mean value formation FALSE
is reset.
Outputs
OUTPUT PASDATABLOCK Mean value measured-value / metered-value output (pointer to PAS information)
ME_FL, ME_I,
IT
VAL_NEW BOOL Outputs a Boolean pulse when a new mean value is formed (not for reset or bay
blocking).
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
5.6.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
CFC view
PAS_NRP.tif
5.7.1 Function
You can realize a slave pointer function via the PAS_NRP block. This so-called slave pointer function saves the
current maximum or minimum of the corresponding measured or metered value.
The slave pointer value is reset via the Boolean RESET input and can be triggered via a marker command (see
chapter 3.5), an indication, etc. For this purpose, the slave pointer value is determined as follows:
• for the maximum function: to the smallest possible value
• for the minimum function: to the highest possible value
5.7.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INPUT PASDATABLOCK Input for measured or metered value (pointer to PAS information) 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
RESET BOOL Trigger input for a slave pointer value reset FALSE
NOTE
When TRUE is present, the slave pointer is set to the current value.
MAX_MIN BOOL This parameter specifies whether the minimum or the maximum FALSE
value is saved.
FALSE = Minimum value
TRUE = Maximum value
Outputs
NOTE
Must be connected, i. e. the output is connected with the right-hand CFC
margin bar or set as output variable in the ST program!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
5.7.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
5.7.4 Example
In the example below, a maximum current input is detected and stored. The detection starts after a motor star-
tup phase of 5 seconds.
Bsp_PAS_INDIC_PAS_TIMERSW_PAS_NRP.tif
Description
PAS_INDIC block
A start indication for the motor is present on the INDIC input of the block. It is transmitted to the F_TRIG block
via the Boolean output.
F_TRIG block
F_TRIG is a standard block and pulse generator. The block transmits the pulse to the PAS_TIMERSW.
PAS_TIMERSW block
A start/reset timer (Mode2) is started via the rising edge R_TRIG (indication appeared) and is active for a period
of 5 seconds. This active signal is used to permanently reset the PAS_NRP block during these 5 seconds.
PAS_NRP block
The measured value of the motor current recording is present on the INPUT input of the PAS_NRP block. To
record the maximum current, the MAX_MIN input must be configured with TRUE.
CFC view
PAS_ADD.tif
PAS_SUB.tif
PAS_SUBC.tif
PAS_MUL.tif
PAS_MULC.tif
PAS_DIV.tif
5.8.1 Function
These blocks can be used to apply simple arithmetical functions to measured values and metered values.
The measured values can be processed both in the 32-bit REAL format (value type 28) and in the 16-bit INTE-
GER format (value type 30). Metered values are always processed in the 32-bit INTEGER format (value
type 30).
PAS_ADD
This block adds from 2 to 4 metered or measured values in the REAL format (value type 28) or in the INTEGER
format (value type 30).
In the run sequence, PAS_ADD must always follow the blocks generating the measured or metered values.
This means that the values must have been processed prior to addition. Otherwise, a connection error is cre-
ated. The first value specifies the output data type.
PAS_ADDC
This block adds a metered or measured value in the REAL format (value type 28) or INTEGER format (value
type 30) with a constant.
In the run sequence, PAS_ADDC must always follow the blocks generating the measured or metered values.
This means that the values must have been processed prior to addition. Otherwise, a connection error is cre-
ated.
PAS_SUB
The PAS_SUB block can subtract two measured or metered values and create an item of PAS information. The
data type of the created PAS information corresponds to the data type of the PAS information which is present
on the MINU input.
PAS_SUBC
This block subtracts a metered or measured value in the REAL format (value type 28) or INTEGER format (val-
ue type 30) with a constant.
In the run sequence, PAS_SUBC must always follow the blocks generating the measured or metered values.
This means that the values must have been processed prior to subtraction. Otherwise, a connection error is
created.
PAS_MUL
This block multiplies from 2 to 4 metered or measured values in the REAL format (value type 28) or in the IN-
TEGER format (value type 30).
In the run sequence, PAS_MUL must always follow the blocks generating the measured or metered values.
This means that the values must have been processed prior to multiplication. Otherwise, a connection error is
created. The first value specifies the output data type.
PAS_MULC
The PAS_MULC block can multiply a measured or metered value with a constant and create an item of PAS
information. The data type of the created PAS information corresponds to the data type of the PAS information
which is present on the INPUT input.
PAS_DIV
The PAS_DIV block can divide two measured or metered values and create an item of PAS information. The
data type of the created PAS information corresponds to the data type of the PAS information which is present
on the NUMER input.
5.8.2 Connections
IN1 PASDATABLOCK Input for measured or metered value 1 (pointer to PAS information) 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
IN2 PASDATABLOCK Input for measured or metered value 2 (pointer to PAS information) 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
up to
IN4 PASDATABLOCK Input for measured or metered value 4 (pointer to PAS information) 0
ME_FL, ME_I, IT
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
MINU/ PASDATABLOCK Input for measured or metered value 1 (minuend / dividend) (pointer 0
NUMER ME_FL, ME_I, IT to PAS information).
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
SUBTR/ PASDATABLOCK Input for measured or metered value 2 (subtrahend / divisor) (point- 0
DENOM ME_FL, ME_I, IT er to PAS information).
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
DIAG WORD This output visualizes diagnostic information. (refer to Appendix A.2).
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INPUT PASDATABLOCK Input for measured or metered value (pointer to PAS information). 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
NOTE
Must be configured!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
NOTE
Must be configured!
DIAG WORD This output visualizes diagnostic information. (refer to Appendix A.2).
5.8.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
CFC view
PAS_CMP.tif
PAS_CMPC.tif
5.9.1 Function
PAS_CMP
This block compares 2 metered or measured values in the REAL format (value type 28) or INTEGER format
(value type 30). The result of the comparison is output on the corresponding Boolean output (value = TRUE).
PAS_CMPC
This block compares a metered/measured value with a constant in the REAL format (value type 28) or INTE-
GER format (value type 30). The result of the comparison is output on the corresponding Boolean output (value
= TRUE). The second value is set as a constant via the CONST input.
5.9.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
INPUT1 PASDATABLOCK Input for measured or metered value 1 (pointer to PAS information) 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
INPUT2 PASDATABLOCK Input for measured or metered value 2 (pointer to PAS information) 0
ME_FL, ME_I, IT
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar or indicated as a poll parameter within the frame-
work of ST programming!
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Must be configured!
Outputs
5.9.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the corresponding block.
Overview
This chapter explains the SICAM PAS automation blocks of the special block group. They are important tools
for the connection and processing of PAS information in SICAM PAS.
Contents
CFC view
PAS_SASC.tif
6.1.1 Function
The PAS_SASC block forms an item of PAS information (PASDATABLOCK data type) from individual compo-
nents. This new item of PAS information can be further processed in other blocks.
This option can e. g. be used to simulate PAS information for testing individual states of automation blocks.
6.1.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
SEND BOOL Creates an item of PAS information during the change from FALSE to FALSE
TRUE.
FALSE = no PAS information
TRUE = creation of PAS information
NOTE
Must be connected if CHANGE is not interconnected and must not be
connected if CHANGE is connected!
NOTE
Must be connected if SEND is not connected and must not be connect-
ed if SEND is connected!
DW_VALUE DWORD The value is interpreted as a double word (32 bits) and the command 0
is updated for this value.
NOTE
The use depends on the defined value type.
R_VALUE REAL The value is interpreted as real and the information is updated based 0
on this value.
NOTE
The use depends on the defined value type.
NOTE
If the TIMELOW and TIMEHIGH inputs are not assigned, the internal
system time (UTC) is used.
NOTE
If the TIMELOW and TIMEHIGH inputs are not assigned, the internal
system time (UTC) is used.
Outputs
6.1.3 Miscellaneous
Error processing
Non-connected inputs are checked. If inputs which must be connected in order to ensure the proper functioning
of the block are not linked, no information is processed in the block.
CFC view
PAS_SASS.tif
6.2.1 Function
The PAS_SASS block splits the structure of an item of PAS information, a tag of the type PASDATABLOCK,
into individual components. The block can e. g. be used as a diagnostic tool to check the connection in
SICAM PAS.
6.2.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Must be connected, i. e. the input is connected with the left-hand
CFC margin bar of the CFC editor or connected with an upstream
PAS block!
Outputs
NOTE
The use depends on the defined value type.
NOTE
The use depends on the defined value type.
6.2.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
6.2.4 Example
Refer to Example of a switchgear interlock, page 121 (PAS_INDIC and PAS_COMMCP)
CFC view
PAS_CMD_STRUCT.tif
6.3.1 Function
The PAS_CMD_STRUCT block can be used to visualize the command structure of SICAM PAS. To do this, the
command on the IN input is split in three command elements:
• Command
• CO+/-
• COE+/-
They are assigned as a data structure to the outputs in order to visualize/process the elements of the individual
structures.
The block converts a command of the PASCOMMANDBLOCK type into three elements of the
PASDATABLOCK type. They can be conveniently processed by means of one PAS_SASS block each in order
to visualize the most important elements of the command / acknowledgement / termination data structure.
6.3.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is TRUE
passed on to the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Must be connected!
Outputs
CMD_BF PASDATABLOCK The actual command is available as a data structure for further processing
on this output.
CMD_ACK PASDATABLOCK CO+/- is available as a data structure for further processing on this output.
CMD_TERM PASDATABLOCK COE+/- is available as a data structure for further processing on this
output.
6.3.3 Example
The following example illustrates the allocation of command elements to three PAS_SASS blocks.
sample_cmd_struct.tif
Description
PAS_CMD_STRUCT block
The command is present on the IN input. The CMD_BF, CMD_ACK and CMD_TERM outputs provide the com-
mand and the CO+/- and COE+/- command elements.
PAS_SASS blocks
The command elements are assigned to the inputs of the blocks. The individual components of the command
elements are available on the outputs.
CFC view
PAS_MUXTEL.tif
6.4.1 Function
This block allows for the connection of several sources of information to one block in the SoftPLC. It maps up
to four items of information to the input of another block.
The PAS_MUXTEL block is mainly used for the derivation of commands if several triggers may possibly exist
(e. g. switching sequence).
6.4.2 Connections
Inputs
up to
Outputs
NOTE
Must be connected!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
6.4.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
The saving of setpoint values is useful e.g. when pre-defining limit values from a control center or the HMI for
an automatic sequence in the SoftPLC in order to ensure that these limit values have a permanent effect. If
these values were not saved persistently, all pre-defined values would have to be re-defined upon each restart
of the SoftPLC (e.g. due to a restart of the computer). If, however, these values are saved by means of persis-
tent variables, they are immediately available upon a restart of the SoftPLC.
This is extremely useful in redundant operating mode because, in case of a system failure, the changes of per-
sistent setpoint values from this system are synchronized by the active system upon a restart. Otherwise, set-
point values which are not persistent would not be applied by the temporarily inactive system.
To persistently save data in the SICAM PAS SoftPLC, use the RETAIN-declared variable. This is possible in
any POE type, except functions (no local data in accordance with IEC 61131-3) and CFC-POEs (the declaration
is not possible in the Editor).
To use persistent variables in these POE types, you declare them in a global data declaration or a program
POE of another language type (e.g. ST, IL, SFC) as a global variable with the RETAIN key word.
6.5.1 Examples
NOTE
In order to create a user block for any native IEC 61131-3 data type, all declarations of the INTEGER data type
in the example illustrated below must be replaced by the native IEC 61131-3 data type.
✧ Under the File type, navigate to the Function block and highlight the ST Function block template.
FensterErstellenEinerNeuenDateiFBST.tif
Fig. 6-6 Dialog window for creating a new file, ST function block
✧ Under File name, enter the desired designation for the function block, e. g. PersistentInteger, and click
on OK to confirm. The function block is created and shown in the editor window.
✧ In the editor window, enter the description for the PersistentInteger function block.
FunktionsbausteinPersistentIntegerBeschreiben.tif
✧ In order to check the syntax, click on File > Check syntax. If this check was successful, 0 errors,
0 warning(s) are shown in the output window.
PersistentInteger.tif
✧ Under File type, navigate to the Function block and highlight the ST Function block template.
FensterErstellenEinerNeuenDateiFBST.tif
Fig. 6-9 Dialog window for creating a new file, ST function block
✧ Under File name, enter the desired designation for the function block, e. g. FB_SELC_PERS and click
on OK to confirm. The function block is created and shown in the editor window.
✧ In the editor window, enter the description for the FB_SELC_PERS function block.
FunktionsbausteinBeschreiben_SELCPERS.tif
✧ To check the syntax, click on File > Syntax check. If the check was successful, 0 errors, 0 warning(s)
are shown in the output window.
FB_SELC_PERS.tif
CFC view
PAS_DATA.tif
Function
NOTE
The outdated PAS_DATA firmware block is replaced by the new FB_DATA block (see chapter 10.4). All existing
instances of the PAS_DATA block should be replaced with this block.
Overview
This chapter explains the SICAM PAS automation blocks of the time block group.
Contents
View
PAS_TIMERSW.tif
7.1.1 Function
The PAS_TIMERSW block provides a timer block for the SoftPLC. With every sequence of the timer, the task
is initiated again to perform calculations (if required).
To start the PAS_TIMERSW block during the startup of SICAM PAS already, the START input must be set to
TRUE. In this case, the TIMER already starts during the startup process.
The PAS_TIMERSW block provides 4 different modes: As long as the START input is set to TRUE, a pulse is
generated at cyclical intervals in the Cyclic Pulse mode. Additionally, the pulse interval is set to 0:00 h in case
of a Synchronous Pulse. The Start/Reset Timer mode describes a timer with start and a possible reset signal.
If the Delay is used, the system checks whether a signal is present without interruption during a defined time.
PAS_TIMERSWcyclic.tif
PAS_TIMERSWsync.tif
PAS_TIMERSWstartreset.tif
Delay mode
PAS_TIMERSWdelay.tif
7.1.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
Outputs
CHANGE BOOL The value changes from FALSE to TRUE or vice versa with each successful timer
sequence.
OUT BOOL The output for the current timer sequence is set to TRUE with every successful
timer run.
ERR BOOL The output for the current sequence is set to TRUE with every incorrect timer run
(reset or abortion).
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
7.1.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
CFC view
PAS_TIMES.tif
7.2.1 Function
This block splits the system-internal time format into individual components. The T_MODE input provides the
following options:
• Output of the current time stamp at the time of the block call
• Output of the present time via the two TIMEHIGH and TIMELOW inputs
• Output of the time of the present PAS information
• Output of the time stamp at the time of the trigger pulse
7.2.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Active when T_Mode = 3 !
NOTE
Must be connected if T_Mode = 2 !
NOTE
Must be connected if T_Mode = 1 !
NOTE
Must be connected if T_Mode = 1 !
Outputs
7.2.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
CFC view
PAS_GETTIME.tif
7.3.1 Function
This block can be used to generate a current UTC value or a time stamp based on the local time (independent
of the time zone) for PAS firmware blocks (e. g. for PAS_CRI, PAS_CRCOM or PAS_SAC).
The time zone of the computer on which the SICAM PAS SoftPLC runs is used for local time stamps.
7.3.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is passed on to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
TRIGGER BOOL Toggling of the input generates a new time stamp. FALSE
Outputs
7.3.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
Overview
This chapter explains the SICAM PAS automation blocks of the sequence block group. This block is used to
realize functional sequences and switching sequences.
Contents
CFC view
PAS_STATE.tif
8.1.1 Function
The PAS_STATE block acts as a state, e. g. within the framework of the configuration of a state machine (refer
to Petri networks). An action is triggered when activating a state. It is defined on the SACTION input. The block
is activated via the Boolean value TRUE on the ACTIVATE input.
PAS_TRANS blocks are used to define transitions to another state (connection via CONNECT). In the se-
quence of execution, a PAS_STATE block is always located downstream of its assigned PAS_TRANS blocks.
If a transition is performed via a PAS_TRANS transition block, the previous and the following state are activat-
ed.
The subsequent transitions (PAS_TRANS block) are connected to the (PAS_STATE block) state via the
CONNECT inputs/outputs.
The step type can be defined on the SACTION input (refer to table below). Upstream transitions communicate
to the PAS_STATE block via the ACTIVATE block when it becomes active. The specified action is executed via
the SACTION input after each activation. The START input of the corresponding PAS_STATE block must be
activated for the starting state of the Petri network model.
8.1.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
Only one PAS_STATE block should be defined as start state.
ACTIVATE DWORD The specified action is executed as soon as this input is activated 0
and the state becomes active.
Outputs
CONNECT PASSTATELINK This output is connected to the CONNECT input of PAS_TRANS blocks.
OUT PASDATA Telegram output depending on the specified action – an indication, a command,
BLOCK etc. (refer to SACTION input) (pointer to PAS information)
As a rule, it is used with the COMM input of a PAS_COMMCP or directly connect-
ed to the margin bar (indication).
ACTIVE BOOL Indicates which state is active or has been activated via the
START or ACTIVATE input.
8.1.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
8.1.4 Example
Refer to Transformer Switching, page 250
CFC view
PAS_TRANS.tif
8.2.1 Function
The PAS_TRANS block acts as a transition e. g. within the framework of the configuration of a Petri network.
The transition is connected to the downstream states (PAS_STATE block) via the CONNECT input. The tran-
sition switches as soon as the OK condition is met. The upstream states (PAS_STATE block) are activated via
the ACTIVATE output.
Depending on the individual setting, the PAS_TRANS block calls the task again via the STARTTASK input.
Blocks which are positioned before the PAS_TRANS block in the sequence of execution are computed again.
The task is initiated via the Boolean value TRUE on the STARTTASK input.
8.2.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded to TRUE
the ENO output.
FALSE = block disabled
TRUE = block enabled
NOTE
The transition can only switch if the downstream state is active.
OK BOOL Switching condition for transition. The transition switches if TRUE is FALSE
present.
Outputs
ACTIVATE BOOL This output is set to TRUE when the transition switches.
8.2.3 Miscellaneous
Error processing
If inputs which must be connected in order to ensure the proper functioning of the block are not linked, no in-
formation is processed in the block.
8.2.4 Example
Refer to Transformer Switching, page 250.
Overview
This chapter illustrates the principles of user-specific automation blocks. For a more detailed functional descrip-
tion of these blocks, contact your Siemens partner.
Contents
CFC view
PAS_ANDI_EX.tif
PAS_ORI_EX.tif
9.1.1 Function
PAS_ANDI_EX
The PAS_ANDI_EX block differs from PAS_ANDI with regard to status processing only.
The status processing of the PAS_ANDI_EX block is compatible with the status processing of SICAM SAS. The
exceptions of the PAS_ANDI block do not apply for this block.
The PAS_ANDI_EX block realizes AND operations for group indications of single-point and/or double-point in-
dications. The block can perform an AND operation for up to 4 indications at the same time. If several indica-
tions exist, it can be cascaded.
AND operation
The group indication is set as soon as all indications are present (RAISED). When the first of the linked indica-
tions disappears, the group indication is cleared, i. e. set to CLEARED. The time of the indication which was
present last or the time of the indication which disappeared first is applied for the result indication.
The startup indication is transmitted as soon as the startup indications of all inputs have been received.
The status of the raising group indication corresponds to the OR link of the states of all indications on the in-
puts.
PAS_ORI_EX
The PAS_ORI_EX block differs from the PAS_ORI with regard to status processing only.
The status processing of the PAS_ORI_EX block is compatible with the status processing of SICAM SAS. The
exceptions of the PAS_ORI block do not apply for this block.
The PAS_ORI_EX block manages OR operations for group indications of single-point and/or double-point in-
dications. The block can perform an OR operation for up to 4 indications at the same time. If several indications
exist, it can be cascaded.
The blocks link the logical values of indications. For example, they form one logical value (e. g. 01 becomes
FALSE) from the value of a double-point indication and perform a logical link for this value. A pointer to the
result indication (PAS information) is output.
The result indication always has the 'double-point indication' type. The cause of the transmission (CAUSE) is
always set to SPONTANEOUS for a result indication.
OR operations
The group indication is set as soon as the first linked indication is present (RAISED). When the last of the linked
indications disappears, the group indication is cleared, i. e. set to CLEARED. The time of the indication which
rises first or is cleared last is applied for the result indication.
The startup indication is transmitted as soon as the startup indications of all inputs have been received.
The status of the cleared group indication corresponds to the OR link of the states of all indications on the in-
puts.
9.1.2 Connections
Inputs
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
up to
NOTE
Must be interconnected, i. e. the input is linked to an item of
PAS information!
Outputs
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2)
EN_EVENT BOOL TRUE in the case of a value change (BVALUE), otherwise FALSE
INDIC PASDATABLOCK The address of the result indication is present on this output.
DP
NOTE
Must be interconnected, i. e. the input is linked to an item of PAS information!
9.1.3 Miscellaneous
Error processing
9.1.4 Example
Refer to Example of a PAS_ANDI and PAS_TSP block, page 93,
refer to Example of a PAS_ANDI, PAS_ORI and PAS_INVER block, page 100.
CFC view
PAS_GROUPI_EX.tif
9.2.1 Function
The PAS_GROUPI_EX block is a group indication block. It allows for the detection of changes within a group
indication. Besides this, it can be configured to respond to spontaneous changes only. The configuration is per-
formed via groups in the SICAM PAS UI.
The individual values in an automation program do not need to be connected. Only a connection from the PAS-
GROUP data type to a PAS_GROUPI_EX block is performed.
The block processes single-point and double-point indications. It has two operating modes:
• Respond to spontaneous changes only
• Respond to all changes
In the spontaneous changes mode (SPON input assigned with TRUE), a double-point indication is created
on the input for each new, incoming, spontaneous and valid indication. Its value toggles upon each creation.
The value on the ALARM output also toggles. The BVALUE output value is TRUE if the outgoing indication is
RAISED. It is FALSE if the output indication is CLEARED.
With each new outgoing indication, the EN_EVENT output is set to TRUE for this call of the automation pro-
gram.
9.2.2 Connections
Inputs
SPON BOOL FALSE = the block processes all incoming indications FALSE
TRUE = the block responds only to spontaneous indications
Outputs
EN_EVENT BOOL TRUE for a new outgoing indication for the time of a poll.
NOTE
Must be connected!
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2)
CFC view
PAS_UDIFF.tif
9.3.1 Function
The PAS_UDIFF block provides information about limit value violations depending on boundary conditions.
If a limit value is violated for a period T1 and if the measured-value change for the evaluation period T2 is great-
er than a defined threshold value, a Boolean output tag is set to True.
The block can have an upper and a lower limit value. Independent threshold values and time intervals can be
defined for both limit values.
Example
In the present example, the measured value falls below the lower limit.
udiff_example.tif
and if
• the measured-value change (current measured valuecurrent - Measured ValueT2_ENC) is greater than the
DU_ENC limit (T2_ENC > T1_ENC; 2 condition).
The BENC output is reset if the U_REF measured value exceeds the U_ENC limit again.
9.3.2 Connections
Inputs
EN BOOL This input activates the block. The input assignment is forwarded TRUE
to the ENO output.
FALSE = block disabled
TRUE = block enabled
T1_ENC TIME Minimum acquisition time for a violation of the lower limit [s]: Must T#10s
(1) be a multiple of T_MCYC
T2_ENC TIME Time for measured value for the lower threshold [s]: Must be a mul- T#40s
(1) tiple of T_MCYC
T1_DEC TIME Minimum acquisition time for a violation of the upper limit [s]: Must T#5s
(1) be a multiple of T_MCYC
T2_DEC TIME Time for measured value for the upper threshold [s]: Must be a T#40s
(1) multiple of T_MCYC
(1) In case of a change of the input during operation, the block performs an internal RESET.
Outputs
ERROR BOOL 0 = OK
TRUE = error
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2)
BENC BOOL Output signal for the trigger of a violation of the lower threshold
BDEC BOOL Output signal for the trigger of a violation of the upper threshold
BU_T1ENC BOOL Output signal for acquisition time, lower limit reached
BU_T1DEC BOOL Output signal for acquisition time, upper limit reached
Overview
This chapter explains the blocks of the PAS standard library. The library is always installed and can be used in
the current project.
Contents
Prerequisites
✧ In the project browser of the SICAM PAS SoftPLC UI, click the Bib tab.
✧ Under Libraries, right-click on PASStdLib and select Use in Current Project in the context menu.
✧ In the Catalog, right-click the POUs tab and select Refresh in the context menu. The blocks of the
PAS standard library are shown under Library.
PASStandardBibliothek.tif
CFC view
BusBarEmulation.tif
10.2.1 Function
This block is used to select a busbar voltage from the voltages on two line feeders. Depending on the position
of the voltage transformer relay and the applied voltages, one of the voltages is reflected on the output (de-
pending on the status of the voltages and the position of the voltage transformer relays). The system always
tries to assign a valid voltage to the output. If one of the applied voltages becomes invalid (invalid or overflow),
the alternative voltage is reflected on the output, provided that it is valid and that no overflow has occurred. If
both voltages are valid, either the first or the second voltage is reflected on the output, depending on the state
of the voltage transformer relays (outgoing single-point indication).
If both indications for the voltage transformer relay drop-out are raising, a ZERO indication is created, i. e. a
voltage with the value 0.0 and the Invalid status.
10.2.2 Connections
Inputs
Outputs
ResVolt PASDATABLOCK Voltage resulting from the processing of incoming indications (measured value,
floating point)
CFC view
CTRL_MUX.tif
10.3.1 Function
The CTRL_MUX block selects the measured value to be transmitted and makes it available on the OUT output.
The SELECT input is connected to the SELECT output of the SLCT_MUX block (see chapter 10.8). The mea-
sured value whose number is present on the SELECT input is now shown on the output. If the numeric value
on the SELECT input is greater than 7, the value 0.0 is shown on the OUT output.
10.3.2 Connections
Inputs
Outputs
CFC view
FB_DATA.tif
10.4.1 Function
NOTE
The FB_DATA block replaces the outdated PAS_DATA firmware block (see chapter 6.5.2). All existing instanc-
es of the PAS_DATA block can be replaced with this block.
In order to persistently save data create type-specific user blocks that use RETAIN-declared variables, refer to
Layout of the PersistentInteger user block, page 178 and Layout of the FB_SELC_PERS user block, page 180
10.4.2 Connections
Inputs
R_CHG BOOL Trigger input for values of the REAL data type on R_IN input FALSE
Values are only applied if the input is toggled.
R_IN REAL Input for values of the REAL data type 0.0
This input is kept persistent if no PAS information is interconnected
on the PAS_IN input.
Outputs
CFC view
FB_GROUPI.tif
10.5.1 Function
This ST block behaves like the PAS_GROUPI firmware block (see chapter 4.8).
It serves as an implementation example for the use of the PAS_GROUPINDIC firmware block (see
chapter 4.12) or as a template for the creation of the group indication blocks
.
NOTE
The code of the block can be viewed in the SICAM PAS installation directory, \PlcUI\ini\lib\PASStdLib subdi-
rectory.
10.5.2 Connections
Inputs
Outputs
ALARM BOOL Toggling in case of a new RAISED indication with the spontaneous cause
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
CFC view
FB_NGCGROUPI.tif
10.6.1 Function
Apart from one exception, this ST block behaves like the PAS_GROUPI firmware block (see chapter 4.8). The
exception is that the block does not consider blocked indications (bay and/or telecontrol block). If an indica-
tion is transmitted to the block as blocked, the block ignores it as long as the blocking persists. The group in-
dication pending on the output therefore never receives the bay and/or bay block active status.
10.6.2 Connections
Inputs
Outputs
ALARM BOOL Toggling in case of a new RAISED indication with the spontaneous cause
DIAG WORD This output visualizes diagnostic information (refer to Appendix A.2).
CFC view
SFC_RunCyclic.tif
10.7.1 Function
In order to be able to use a program of the SFC IEC language (Sequential Function Chart) in the
SICAM PAS SoftPLC, a SFC_RunCyclic is required. This ensures the cyclic run of the active resource.
The block must be instantiated in a program which is linked to the active resource. Additionally, it must be called
up in each run without conditions.
The following example illustrates the available Main.ST ST program (cycle time 100ms):
BeispielSFC_RunCyclic.tif
NOTE
If one or several PAS_TIMERSW block(s) (see chapter 7.1) is (are) already used in the active resource for the
creation of cyclic pulses, the use of the SFC_RunCyclic block is possibly not required, since the resource is
already cyclically processed.
10.7.2 Connections
Inputs
CYCLETIME TIME Cycle time of the active resource, the time must 0
be >= 10 ms
Outputs
ERR BOOL FALSE: the defined cycle time is plausible, the block functions properly
TRUE: the defined cycle time is not plausible, the block is inactive
CFC view
SLCT_MUX.tif
10.8.1 Function
The SLCT_MUX block is used to select the measured value to be transmitted by means of a single-point/dou-
ble-point indication.
With a raising single/double-point indication on one of the inputs, the number of the input is shown on the
SELECT output. The indication starts a timer which ensures that the number of the input is present at least dur-
ing the specified runtime of the timer on the SELECT output.
If no or more than one single/double-point indications is raising on the input, the value 65535 is shown on the
SELECT output.
As long as the SELECT output is active, the single-point indication is raising on the OUT output. This output
is used for the cascading of several SLCT_MUX blocks.
The SELECT output is connected to the SELECT input of the CTRL_MUX block (see chapter 10.3).
10.8.2 Connections
Inputs
TIMEOUT TIME Time during which a value is present at least on the SELECT output.
Outputs
SELECT INTEGER Shows which input is active and is connected with the SELECT input of the
CTRL_MUX block (see chapter 10.3).
OUT PASDATABLOCK Single-point indication for the cascading of several SLCT_MUX blocks
CFC view
ToggleSP.tif
10.9.1 Function
With each incoming, spontaneous indication on the input (any type), the block creates a single-point indication
with a toggling value on the output. The time stamp and the status are applied by the incoming indication. The
created single-point indication always has the spontaneous cause. During startup, a cleared single-point indi-
cation with the General Interrogation cause is created once.
10.9.2 Connections
Inputs
Outputs
Overview
This chapter presents possible solutions for frequently occurring task definitions.
Contents
SS1 busbar
SS2 busbar
Q1 disconnector Q2 disconnector
Q0 circuit breaker
Switching conditions
The following switching conditions must be met for the busbar change represented in Figure 11-1:
• The Q0 circuit breaker can only be switched if the Q1 and Q2 disconnectors are not in the intermediate
position.
• The Q1 and Q2 disconnectors can only be switched if the Q0 circuit breaker is disconnected.
Logical equations
The logical equations regarding the above-mentioned switching conditions are as follows:
➊ ➏
➋ ➐
➌ ➑
Beispiel6.tif
Description
This block locks the busbar feeder via the control center if the switching authority is local (key switch - INDIC ➍
input).
PAS_COMMCP Q1/Q2
The PAS_COMMCP1 Q1 and PAS_COMMCP2 Q2 blocks monitor the transmission of the switching
commands to the Q1 and Q2 disconnectors for both switching directions (ON and OFF) depending on the
signals on the REL_ON and REL_OFF enable inputs. Both are 1-active.
PAS_COMMCP Q0
PAS_COMMCP Q0 monitors the issue of the switching command for the Q0 circuit breaker for the ON
switching direction depending on the signal on the REL_ON enable input (TRUE-active).
AND
The AND block performs the AND linkage of the logical equation (I). An AND operation of intermediate position
indications is performed via the PAS_INDIC Q1 and Q2 blocks and assigned to the REL_ON enable input of
the PAS_COMMCP Q0 block.
PAS_INDIC Q1/PAS_INDIC Q2
If required, these blocks derive the intermediate position indication of the Q1 and Q2 disconnectors. The
PAS_INDIC inputs are connected to the INDIC outputs of the PAS_COMMCP Q1 and PAS_COMMCP Q2
blocks.
This block produces the enable or interlock signal for the PAS_COMMCP Q1 and PAS_COMMCP Q2 blocks
depending on the logical equations (II) and (III). The INDIC input of the block is connected to the
INDIC output of the PAS_COMMCP Q0 block. Whenever the Q0 circuit breaker is switched OFF, the OFF
output is TRUE (1). It controls the enable inputs of the PAS_COMMCP Q1 and PAS_COMMCP Q2 blocks.
➊ Q2 process feedback
➋ Q1 process feedback
➌ Q0 process feedback
➏ Q2 command
➐ Q1 command
➑ Q0 command
11.2.1 Overview
Several block types are used to specify a switching sequence in the SoftPLC. The following information must
be specified by means of these blocks within the framework of parameterization:
• Information on the switching sequence start
• Control of the switching sequence, check of the switching conditions and command generation
• Command output
Table 11-1 Contents of the Enable Circuit Breaker for Maintenance sample switching sequence
✧ As a local variable, create a PAS_SELC instance in order to enable the processing of the start command.
VariableDeclaration.tif
Cont. of Section 1:
• The third switching operation step Disco2_OFF
opens Disconnector 2.
• 2 transitions which check whether the command for
opening Disconnector 2 has been executed
successfully (Disco2_OK) or not (Disco2_NOK).
In case of an error (negative response to command
acknowledgment or command termination), the
system jumps to the Seq_NOK error processing
step.
• 2 steps:
The Seq_OK step positively terminates the start
command because the entire switching sequence
has been successful. The Seq_NOK step, which
also serves as a jump target for the error processing
of all steps, negatively terminates the start
command because an error has occurred.
• 2 transitions (Dummy1 and Dummy2), which
always initiate a switching operation, are required in
order to jump to the Init initialization step because a
direct jump back is not permissible after this step.
• Jump back to the Init initialization step.
SFCOverview2.tif
Initialization step
InitStep.tif
Start enables the next switching operation step if the start command has been received with the ON switching
direction.
StartTransOK.tif
The Start_NOK transition activates the Seq_NOK error processing jump if the command has been received,
but the switching direction is OFF.
StartTransNOK.tif
The Break_OFF switching operation step triggers the command for opening the circuit breaker.
✧ Call up the corresponding PAS_CRCOM instance with the value TRUE on the SEND input. All other
parameters have already been assigned during the Init initialization step. Using the SEND input for
triggering the command ensures that the command is triggered only once even if this switching operation
step is executed several times.
BreakerStep.tif
The following Break_OK transition is switched if the command execution has been acknowledged positively.
As can be seen in this example, the PAS_COMMCP instance is not called up again, but only its OK output is
checked. This is not necessary because the active Break_OFF switching operation step and its subsequent
transitions are always executed during one computing cycle and the block is already called up during this
switching operation step.
BreakerTransOK.tif
Analogous to the Break_OK transition, Break_NOK switches if the command execution has been
acknowledged negatively.
BreakerTransNOK.tif
Further steps
The steps which follow now for switching the remaining switching elements are structured similar to the circuit
breaker elements and only differ with regard to the use of the specific block instances for the corresponding
commands.
DisconnectorStep.tif
DisconnectorTransOK.tif
During the last two Seq_OK and Seq_NOK steps, the switching sequence start command is terminated
depending on the successful execution of the switching sequence.
This means that the entire switching sequence is executed successfully and the start command terminated
positively, even if the command for closing the Earth2_ON grounding conductor has been executed
successfully (Seq_OK).
SequenceStepOK.tif
The Seq_NOK step (which also serves as a jump target for all other error processing actions) is executed
accordingly if the last switching step (Close Earth2_ON grounding conductor) could not be executed
successfully.
SequenceStepNOK.tif
The two Dummy1 and Dummy2 transitions after the Seq_OK and Seg_NOK steps always switch over to an
Init initialization step.
These transitions are necessary in accordance with the IEC 61131-3 standard for sequential programming
languages, e.g. SFC (Sequential Function Chart). The transition variables are fixedly assigned with TRUE.
DummyTrans.tif
11.3.1 Overview
A redundancy switchover could happen while a switching sequence is running in SFC.
By appropriate evaluation of the AddCause, the switching sequence can be continued after a redundancy
switchover. If there is no evaluation of the AddCause in the logic of the switching sequence, the switching se-
quence will be terminated according to the logic.
Since the affected command had a negative termination, a command can be re-send directly after the
switchover.
The following section describes how you can react to a redundancy switchover during a switching sequence in
the SFC flow-chart.
11.3.2 Principle
The following logic steps can be added to the SFC flow-chart for any command processing:
• The command is split into its single components.
• The AddCause is checked in terms of an error:
− If the AddCause is not AddCDeviceStatus the "normal" error handling is performed.
− If the AddCause is AddCDeviceStatus a redundancy switchover happened.
• In case of a switchover, the switching sequence should at least wait for the feedback-monitoring time set
in the device. This is, because the device will not accept any other commands while the switching
command is running.
• When the timer has finished the command feedback is being checked.
• If the command feedback is OK the sequence can be proceeded.
• If the command feedback is not OK the customer has to react.
In the example below, the user tries to issue the command again.
The following sections show a flow-chart completed with this logic (Fig. 11-17) and subsequently the ST code
of the displayed function blocks.
SwSeq.tif
Declarations Init
FB_CMDSTRUCT_CIRCUITBREAKER : PAS_CMD_STRUCT;
FB_SASS_CIRCUITBREAKER : PAS_SASS;
ADDCAUSE_CIRCUITBREAKER : BYTE;
COT_CIRCUITBREAKER_116 : BOOL;
(* Timer *)
FB_PAS_TIMERSW_DELAY : PAS_TIMERSW;
(* Feedback evaluation *)
FB_PAS_INDIC_FEEDBACK : PAS_INDIC;
FEEDBACK : BOOL;
Initialization Init
FB_CMDSTRUCT_CIRCUITBREAKER(IN:=FB_COMMCP_CIRCUITBREAKER.OUT);
FB_SASS_CIRCUITBREAKER(INPUT:=FB_CMDSTRUCT_CIRCUITBREAKER.CMD_TERM);
ADDCAUSE_CIRCUITBREAKER := 0;
COT_CIRCUITBREAKER_116 := FALSE;
(* Timer *)
(* Note: TTIME has to be greater than the Feedback Monitoring Time in the Device*)
(* Feedback evaluation *)
FB_PAS_INDIC_FEEDBACK(EN:=FALSE, INDIC:=S_G7SA6311_Steuerung_Q0_1_Position);
FEEDBACK := FALSE;
Break_OFF:
FB_CRCOM_CIRCUITBREAKER(SEND:=TRUE);
FB_COMMCP_CIRCUITBREAKER();
FB_CMDSTRUCT_CIRCUITBREAKER(EN:=1, IN:=FB_COMMCP_CIRCUITBREAKER.OUT);
FB_SASS_CIRCUITBREAKER(EN:=1,INPUT:=FB_CMDSTRUCT_CIRCUITBREAKER.CMD_TERM);
ADDCAUSE_CIRCUITBREAKER:=FB_SASS_CIRCUITBREAKER.ADDCAUSE;
(* Reset Timer *)
FB_PAS_TIMERSW_DELAY(START:=0);
Break_OK:
Break_OK := FB_COMMCP_CIRCUITBREAKER.OK;
Break_NOK:
Break_NOK := FB_COMMCP_CIRCUITBREAKER.ERR;
CheckAddC:
COT_CIRCUITBREAKER_116 := true;
else
COT_CIRCUITBREAKER_116 := false;
end_if;
OtherAddC:
RedSwitch:
RedSwitch := COT_CIRCUITBREAKER_116;
Wait:
(* Start Timer *)
FB_PAS_TIMERSW_DELAY(START:=1);
FB_COMMCP_CIRCUITBREAKER(COMM:=FB_CRCOM_CIRCUITBREAKER.OUTPUT);
Timer_fin:
Timer_fin := FB_PAS_TIMERSW_DELAY.OUT;
CheckFB:
FB_PAS_INDIC_FEEDBACK(EN:=TRUE,
INDIC:=S_G7SA6311_Steuerung_Q0_1_Position);
FEEDBACK := true;
else
FEEDBACK := false;
end_if;
FB_OK:
FB_OK := FEEDBACK;
FB_NOK:
Method of operation
The switching is distributed to the individual sheets of the CFC chart according to the corresponding basic
function:
• Sheet 1 (see Figure 11-18):
Main chart: Command or indication preprocessing and control logic for the transformer tap
• Sheet 2 (see Figure 11-19):
Transformer tap command with value conversion: Chart-in-chart technology.
This is the TR_SET block of the main chart.
• Sheet 3 (see Figure 11-20):
Read in of the current transformer indication and comparison with the step value. Logic for evaluation
purposes. Chart-in-chart technology.
This is the TR_CHECK block of the main chart.
• Sheet 4 (see Figure 11-21):
Step-down of the transformer and evaluation of the process feedback:
Chart-in-chart technology.
This is the TR_DOWN block of the main chart.
• Sheet 5 (see Figure 11-22):
Step-up of the transformer and evaluation of the process feedback:
Chart-in-chart technology.
This is the TR_UP block of the main chart.
Sheet 1
On Sheet 1 of the main chart (see Figure 11-18), the set command for the transformer tap is transmitted to the
CFC logic (TR_SET block). The set command remains active until the process is terminated with a positive or
negative result. The setpoint value of the transformer tap is transmitted to the TR_CHECK block via the
TR_SET output (TR_SET block).
In the TR_CHECK block, the setpoint value is further processed for a value comparison with the actual value.
The resulting action is initiated.
The transformer tap is controlled via the PAS_MUXTEL and PAS_COMMCP blocks. The TR_DOWN and
TR_UP blocks trigger the transformer commands and TR_CHECK evaluates the new process feedback.
Sheet 2
The transformer tap command with value conversion is realized on Sheet 2 (see Figure 11-19).
The PAS_SELC block is used for this purpose. The set command is read in and the setpoint value is extracted
in this block. Afterwards, it is forwarded to the TR_CHECK block.
Sheet 3
On Sheet 3 (see Figure 11-20), the current transformer indication is read in and the comparison with the
setpoint value is made. The sequence is started via the PAS_STATE block. The PAS_INDIC block reads out
the transformer indication, whilst the comparison is performed via the PAS_CMPTC block. The scheduled
value and the actual value are evaluated here. Depending on the tap position, additional blocks are activated
with the output signals (TR_DOWN, TR_UP) or the switching sequence is terminated.
The switching conditions are checked when the CHECK TAP status becomes active. Depending on the
switching condition met, the STEP UP status (on Sheet 5) or the STEP DOWN status (on Sheet 4) is
activated or the command is terminated:
• POSITIVE: SETPOINT = ACTUAL reached or
• NEGATIVE: ERROR DURING SWITCHING SEQUENCE.
Sheet 4
The logic for stepping down the transformer tap is performed on Sheet 4 (see Figure 11-21) with the
STEP DOWN state. The STATE block is used for this purpose.
Two switching conditions (transitions) exist in the STEP DOWN state: CMD OK and CMD_ERROR. A TRANS
block is used for each switching condition.
If the STEP DOWN state becomes active, the STATE block performs the action which has been previously
parameterized on the ACTION input: The transformer tap is controlled via the OUT output.
The switching conditions are checked afterwards. Depending on the switching condition met, the
CHECK STEP state (on Sheet 3) is activated.
Sheet 5
The logic for stepping up a transformer tap is implemented with the STEP UP state. The STATE block is used
for this purpose.
Two switching conditions (transitions) exist in the STEP UP state: CMD OK and CMD_ERROR.
A TRANS block is used for each switching condition.
When the STEP UP state becomes active, the STATE block performs the action parameterized on the
ACTION input: The transformer tap is controlled via the OUT output.
The switching conditions are checked afterwards. Depending on the switching condition met, the
CHECK STEP state (on Sheet 3) is activated.
Trafo1.tif
Fig. 11-18 Command or indication preprocessing and control logic for the transformer tap
TRAFO2.tif
TRAFO3.tif
Fig. 11-20 Reading-in the current transformer indication and comparison with the step value;
logic for evaluation purposes
TRAFO4.tif
TRAFO5.tif
Contents
A.1.1 Cause
Table A-1
Data 0 Irrelevant
1 Spontaneous
2 Cyclic, periodic
3 Initialized/default
9 Request
10 Metered-value request
19 Command execution
25 Cancelation
26 Cancelation positive
27 Cancelation negative
34 Command feedback
Table A-1
Table A-2
0 Irrelevant
3 Remote control
10 DIGSI operation
Table A-3
0 No error
Table A-3
96 Interlock finding
97 Switchgear interlocking
98 Parameter error
A.1.4 Status
Table A-4
Value Meaning
Bit 3 Substituted
Bit 6 Invalid
Bit 7 Overflow
Table A-5
Value Meaning
Bit 0 --
Bit 1 --
Bit 2 --
Bit 3 --
Table A-6
1 Organizational message
2 Double-point indication
3 Single-point indication
4 Event indication
11 Organizational acknowledgement
12 Metered values
Table A-6
25 GI request
26 Re-store command
27 Organizational command
31 Sequence
Table A-7
0 Time irrelevant
Table A-8
3 Fault number
Table A-9
The diagnostic byte (DIAG output) of the PAS_COMMCP and PAS_SELC command blocks and all blocks of
the following PAS firmware block groups can have the decimal values listed in Table A-10:
• Special blocks
• Indication blocks
• Arithmetical blocks
• Measured-value and metered-value blocks
• Comparison blocks
• Sequence blocks
Table A-10
NOTE
PAS_FI block:
No indications in the input group
PAS_GROUPINDIC block:
No indication group on the input
PAS_DATA block:
Path incorrect / missing
PAS_UDIFF block:
The memory (value buffer) cannot be created
BusBarEmulation block:
Incorrect data type of the incoming indication(s)
NOTE
PAS_GROUPINDIC block:
The memory could not be allocated
PAS_DATA block:
Path incorrect / missing
PAS_UDIFF block:
The assigned times are not correct
NOTE
PAS_DATA block:
Error when writing to the file system
Table A-10
4 Timer event
NOTE
PAS_GROUPINDIC block:
The index on the SELECT input is outside the permissible range
PAS_DATA block:
Error when writing from the file system
PAS_UDIFF block:
Assigned times have changed during operation (internal reset executed)
5 Output error
NOTE
PAS_DATA block:
Pointer to PAS information incorrect
NOTE
PAS_FI block:
Incorrect data type in the input group
PAS_UDIFF block:
The RESET input is active or the measured value is invalid (internal reset executed)
11 Overflow (underflow)
13 Division by zero
Table A-11
Table A-11
Command - PAS_SELC
PAS_COMMCP
Table A-12
Numbers C
100 % absolute value CFC chart-in-chart technology
Analog value standardization 129 Compound block 53
100 % acquisition value CFC program
Analog value standardization 129 Setting the grid 31
Text blocks 29
Checking PAS Information 52
A
Command authorization 63
Additional information 265
Command blocks
Analog value processing
PAS_COMMCP 70
Analog value standardization 129
PAS_COMMCP_EX 74
Analog value standardization
PAS_CRCOM 63
100 % absolute value 129
PAS_SELC 77
100 % acquisition value 129
PAS_SELC_EX 80
Analog values 129
Command interlock 30
Bay and protection devices 129
Command output to the process 74
Measuring Ranges 129
Command Processing
Arithmetic 152
Commands to the process 62
Arithmetical blocks
Concept 62
Diagnosis 266
System-Internal Commands 62
PAS_ADD 153
Commands
PAS_ADDC 153
PD structure 46
PAS_DIV 154
Comparison blocks
PAS_MUL 154
Diagnosis 266
PAS_MULC 154
Comparison of measured or metered values 159
PAS_SUB 153
Compilation
PAS_SUBC 153
of the project 34
Automation block
Compiling project data 33
Connecting 28
Components
Inserting 26
PD structure 258
Selecting 26
Compound block
Setting parameters 26
CFC chart-in-chart technology 53
Automation with SoftPLC
Configuration
POUs 40
Inputs and outputs 51
Task 40
Connection of a group indication with PAS_ORI 29
Converting
B Double-Point to Single-Point Indications 91
Basic configuration steps 18 Creating
Bay and protection devices PAS information 164
Analog value standardization 129 Creating a new CFC program 23
Bit pattern comparison SICAM PAS SoftPLC UI 24
PAS_CMPB 112 Creating group indications 104, 123, 204
PAS_CMPBC 112 CTRL_MUX
BOOL 47 Function 215
BusBarEmulation Inputs 216
Function 213 Outputs 216
Inputs 214 PAS Standard Library 215
Outputs 214 Cyclic pulse mode
PAS Standard Library 213 PAS_TIMERSW 182
BYTE 48
D Examples
Data Type Command derivation 68
Module 268 Command interlock 30
Protocol Type Table 268 Connection of a group indication with PAS_ORI 29
SICAM PAS PD structure 268 Issuing a switching command 73
Use 268 Maximum current input 151
Data types PAS_ACQ 138
BOOL 47 PAS_ANDI 88, 93, 100
BYTE 48 PAS_CMPB 117
DWORD 48 PAS_CMPT 111
INTEGER 49 PAS_COMMCP 121
REAL 49 PAS_CRI 88, 111, 117
SICAM PAS 50 PAS_DELAYI 103
STRING 50 PAS_INDIC 121
TIME 49 PAS_INVER 100
WORD 48 PAS_LIMU 144
Delay mode PAS_ORI 100
PAS_TIMERSW 183 PAS_TSP 93
Derive Persistent command 69
Commands 63 Soft PLC-internal command 32
Describing FB_SELC_PERS user block 178 Switchgear interlocking 121
Describing PersistentInteger user block 176 Switchgear interlocking Busbar feeder 230
Determining the maximum of measured or metered Switching sequences in the SoftPLC 233
values 148 Transformer switching 250
Determining the minimum of measured or metered
values 148 F
DIAG output 266 Fatal errors 52
Diagnostic information 266 FB_DATA
DWORD 48 Function 217
Inputs 218
E Outputs 218
Editor window with CFC program PAS Standard Library 217
Margin bars 28 Saving data persistently 217
Error processing FB_GROUPI
Error 52 Function 219
Fatal errors 52 Inputs 220
Warnings 52 Outputs 220
PAS Standard Library 219
FB_NGCGROUPI
Function 221
Inputs 222
Outputs 222
PAS Standard Library 221
Functions 152
G
Group indication
AND operations 95, 200
OR operations 95, 201
I
Identification number 264
PAS_CRCOM PAS_INDIC
Command authorization 63 Error processing 120
Command derivation 68 Example 121
Create command 64 Function 118
Derive command 63, 64 Inputs 119
Examples 68 Interlocks 118
Function 63 Outputs 119
Inputs 65 PAS_INVER
Outputs 67 Error processing 100
Persistent command 69 Example 100
PAS_CRI Function 98
Creation of indications 85, 89 Inputs 99
Error processing 88 Inverting indications 98
Example 88, 111, 117 Outputs 99
Function 85, 89 PAS_LIML
Inputs 86 Error processing 143
Outputs 87 Function 140
PAS_DATA Inputs 142
Function 180 Limit value monitoring 139
Saving data persistently 180 Lower limit monitoring 140
PAS_DELAYI Outputs 143
Error processing 103 PAS_LIMU
Example 103 Error processing 143
Filter indications 101 Example 144
Function 101 Function 140
Inputs 102 Inputs 142
Outputs 103 Limit value monitoring 139
PAS_DIV Monitor upper limit value 140
Division of measured or metered values 154 Outputs 143
Error processing 158 PAS_MUL
Function 153 Error processing 158
Inputs 156, 158 Function 153
Measured-value / metered-value 152 Inputs 155
Outputs 156, 158 Measured-value / metered-value 152
PAS_FI Multiplication of measured or metered values 154
Inputs 90 Outputs 155
Outputs 90 PAS_MULC
PAS_GETTIME Error processing 158
Error processing 190 Function 153
Function 189 Inputs 157
Generating a time stamp 189 Measured-value / metered-value 152
Inputs 190 Multiplication of a measured or metered value with a
Outputs 190 constant 154
PAS_GROUPI Outputs 157
Creating group indications 104, 123 PAS_MUXTEL
Function 104, 123 Error processing 175
Inputs 105 Function 174
Outputs 105 Inputs 175
PAS_GROUPI_EX 204 Multiplexer for input 174
Creating group indications 204 Outputs 175
Function 204 PAS_NLC
Inputs 205 Error processing 134
Outputs 205 Function 130
PAS_GROUPINDIC Inputs 133
Inputs 124 Non-linear characteristic 130
Outputs 124 Outputs 134
PAS_NRP PAS_SUBC
Error processing 150 Error processing 158
Function 148 Function 153
Inputs 149 Inputs 156, 158
Outputs 150 Measured-value / metered-value 152
Slave pointer function 148 Outputs 156, 158
PAS_ORI Subtraction of measured or metered values 153
Error processing 97 PAS_TIMERSW
Example 100 Cyclic pulse mode 182
Function 95 Delay mode 183
Inputs 96 Error processing 185
Logical link of indications 94 Function 182
OR operation for group indication 95 Inputs 184
Outputs 96 Outputs 184
PAS_ORI_EX Start/ResetTimer mode 183
Error processing 203 Synchronized pulse mode 183
Function 200 Timer for software level 182
Inputs 202 PAS_TIMES
Logical linking of indications 200 Error processing 188
OR operation for group indication 201 Function 186
Outputs 202 Inputs 187
PAS_SASC Outputs 188
Creating PAS information 164 Time block 186
Error processing 167 PAS_TRANS 195
Function 164 Error processing 197
Inputs 165 Function 195
Outputs 167 Inputs 196
PAS_SASS Outputs 196
Error processing 170 Transition (e. g. Petrinetz model) 195
Function 168 PAS_TSP
Inputs 169 Converting double-point to single-point
Outputs 169 indications 91
Splitting PAS information 168 Error processing 93
PAS_SELC Example 93
DIAG output 266 Function 91
Error processing 79 Inputs 92
Function 77 Outputs 92
Inputs 78 PAS_UDIFF 206
Marker command for the SoftPLC 77 Control signals for circuit breakers 206
Outputs 79 Function 206
PAS_SELC_EX Inputs 208
Error processing 82 Outputs 209
Function 80 pasglob.POU 22
Inputs 81 PD component
Marker command for the SoftPLC 80 Additional cause 260
Outputs 82 Cause 258
PAS_STATE 192 Extended status 262
Error processing 194 Initiator category 259
Function 192 Status 262
Inputs 193 PD structure
Outputs 193 Additional information 265
State (e. g. Petrinetz model) 192 Commands 46
PAS_SUB Components 44, 258
Error processing 158 Filtering, breakdown 46
Function 153 Identification number 264
Inputs 156, 158 Indications 46
Measured-value / metered-value 152 Measured values and metered values 46
Outputs 156, 158 Pointers 46
Subtraction of measured or metered values 153 Process data structure 258
Type of time 264
Value type 263
Using
PAS Standard Library 212
Using SFC
Prerequisite 36
Using ST, SFC, STL
Initializing SICAM PAS firmware blocks 35
V
Value type 263
W
Warnings 52
WORD 48
www.siemens.com/energy/poweracademy 3