safety-oriented automation of platform screen doors€¦ · platform screen doors (psds) up to 280...

http://support.automation.siemens.com/WW/view/en/109477186

Description of application 09/2015

Safety-oriented automation of

platform screen doors with SIDOOR ATE530S PROFINET EC door drive and S7-1500 CPU via TIA Portal

http://support.automation.siemens.com/WW/view/en/109477186

Warranty and liability

SIDOOR PSD Automatisierung Entry ID: 109477186, V1.0, 09/2015 2

S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Warranty and liability

Note The application examples are non-binding and do not claim to be complete regarding configuration and equipment as well as all eventualities. The application examples to not represent customer-specific solutions but are merely to serve as an aid for typical tasks. You are responsible for proper operation of the described products. These application examples do not release you from the obligation of a safe approach during application, installation, operation and maintenance. By using these application examples, you accept the fact that we are not liable for any damages beyond the scope of the described liability provision. We reserve the right to make changes to these application examples at any time without prior notice. In case of deviations between the proposals in this application example and other Siemens publications, such as catalogs, the content of the other documentation has priority.

We are not liable for information contained in this document. Our liability for damages resulting from using the examples, notes, programs, configuration and performance data, etc. described in this application example regardless of the legal background is excluded unless required by law, e.g. in cases of willful misconduct, gross negligence, personal injury or death, failure to achieve guaranteed characteristics, fraudulent concealment of a defect or in case of breach of fundamental contractual obligations. The damages in case of a breach of fundamental contractual obligations, however, is limited to the foreseeable damages typical of the contract, unless intention or gross negligence are present or in case of mandatory liability due to injuries to life, body or health. A change in the burden of proof to your disadvantage is not associated with this provision. Distribution or reproduction of these application examples or excerpts thereof is not permitted unless expressly granted by Siemens Industry Sector.

Security informati

on

Siemens provides products and solutions with industrial security functions that support the safe operation of plants, solutions, machines, equipment and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens’ products and solutions undergo continuous development. Siemens recommends strongly that you regularly check for product updates.

For the safe operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be considered. You can find more information about industrial security at http://www.siemens.com/industrialsecurity.

To stay informed about product updates as they occur, sign up for a product-specific newsletter. You can find more information on this at http://support.automation.siemens.com.

http://www.siemens.com/industrialsecurity

http://support.automation.siemens.com/

Table of contents


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Table of contents Gewährleistung und Haftung ...................................................................................... 2

1 Aufgabe............................................................................................................... 4 2 Hard- und Software-Komponenten .................................................................. 8

2.1 Gültigkeit............................................................................................... 8 2.2 Verwendete Komponenten ................................................................... 8

3 Installation und Inbetriebnahme .................................................................... 10

4 Lösung .............................................................................................................. 12

4.1 Übersicht ............................................................................................ 12 4.2 Geräte und Netzwerk ......................................................................... 12 4.3 Programmstruktur ............................................................................... 15 4.4 Programmbausteine ........................................................................... 16 4.4.1 OB1 - Main ......................................................................................... 16 4.4.2 FC - PSD_APPLICATION .................................................................. 16 4.4.3 FB - PSD_CNTRL .............................................................................. 17 4.4.4 FB - SIDOOR_PN_DCU_CNTRL ...................................................... 21 4.4.5 FC - PSD_UPDATE_INPUT_SIGNALS ............................................. 26 4.4.6 FC - PSD_UPDATE_OUTPUT_SIGNALS ......................................... 27 4.4.7 FC - DCU_DECODE_EVENT_LIST .................................................. 28 4.5 PLC-Variablen .................................................................................... 29 4.6 PLC-Datentypen ................................................................................. 30 4.6.1 UDT - DCU_CMD_DAT ...................................................................... 30 4.6.2 UDT - DCU_EVENT_DAT .................................................................. 30 4.6.3 UDT - PSD_CONDITION_MONITOR_DAT ....................................... 30 4.6.4 UDT - PSD_FAULT_MONITOR_DAT ................................................ 31 4.6.5 UDT - PSD_INPUT_SIGNALS_DAT .................................................. 32 4.6.6 UDT - PSD_OUTPUT_SIGNALS_DAT .............................................. 32 4.6.7 UDT - PSD_STATUS_MONITOR_DAT ............................................. 33 4.6.8 UDT - SIDOOR_CDAT ....................................................................... 34 4.6.9 UDT - SIDOOR_SDAT ....................................................................... 35 4.6.10 UDT - SIDOOR_PLST_ENTRY ......................................................... 37

5 Literaturhinweise ............................................................................................. 38 6 Ansprechpartner .............................................................................................. 38

7 Historie.............................................................................................................. 38

1 Task


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

1 Task Introduction

The SIDOOR ATE530S door control device is an "intelligent" door drive with which platform screen doors (PSDs) up to 280 kg can be operated safety oriented and according to custom specifications. The EC motor technology used ensures high reliability and is maintenance-free. Platforms on the one hand form a potential danger for passengers and train drivers and on the other hand act as restrictors to the logistic flows in rail transportation. These and further problems can be solved by means of partitions between the platform and the track bed. The corresponding platform screen doors then ensure safe and rapid boarding and alighting of the passengers. Siemens has presented a new control and drive solution that can be realized without great engineering effort. For fast and efficient integration of the SIDOOR ATE530S unit door controller with PROFINET interface in the railway operation's control system, the platform automation is demonstrated using a S7-1500 CPU and the TIA Portal engineering framework in this application example. The PROFINET module integrated in the SIDOOR ATE530S enables standardized and certified connection to PROFINET IO systems. The SIDOOR IO device hereby satisfies the requirements of a PROFINET IO application according to conformance classes C (CC-C). The configuration (content and structure) of the cyclic process data / user data largely corresponds to the specifications for the cyclic data exchange via PROFIBUS ("variable-speed drives" PROFIBUS profile). This ensures that users can use the same standardized mechanisms to access the process data (control/status words and setpoints/actual values) and parameters of a device. The SIDOOR controller ATE530S disposes of an extensive safety package. The safety functions fulfill the requirements according to EN 62061 for use up to and including SIL 2 (Safety Integrity Level) as well as according to DIN EN ISO 13849-1 Cat 2 PL d (Performance Level). This allows the main requirements for functional safety to be implemented simply and economically. The scope of the safety functions includes: • Safe stopping process • Safe force output • Safe speed observance • Safe monitoring of the rotor position • Safe reading in of digital control signals

1 Task


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Additional features of the SIDOOR ATE530s platform screen doors' controller are: • Integration in TIA Portal using certified GSD files and the function blocks

provided • Fully automatic learn run with automatic calculation of friction, door width and

mass. • Custom energy limitation • Automatic overload protection for control unit and motor • Adjustable output of an unlocking sequence • Flexible anti-vandalism function • Secure control signals according to Safety Integrity Level 2 (SIL2) and

Performance Level d (PLd) • Individually configurable obstruction behavior and dynamic obstruction

detection • Control unit for intelligent switching between offline mode, service mode and

platform mode (remote) • Flexible and configurable input signal logic • Support of end position sensors (DCOPS) • Door widths between 35 cm and 5 m • Retentive event history

1 Task


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

System concept The following figure shows the main components of the automation task:

Figure 1-1 Platform system concept

Main components of the automation task: • Safety-oriented signaling and controlling • Synchronization and management of drive and control parameters • Diagnostics management • Monitoring and troubleshooting • Data management and preparation • Configuration

1 Task


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Objective of the application The application described here sketches the use of already provided function blocks "PSD_CNTRL" and "SIDOOR_PN_DCU_CNTRL" for S7-1500 CPU in the TIA Portal. The use of the help functions "PSD_UPDATE_INPUT_SIGNALS", "PSD_UPDATE_OUTPUT_SIGNALS" and "DCU_DECODE_EVENT_LIST" is also described. The focus of this description of application does not include cyclic processing of control and status data, the configuration and commissioning of a SIDOOR controller. For more information on these topics, refer to the compact operating instructions \9\ and the system manual \3\.

Advantages The solution presented here was optimized, structured and implemented in an easily extendible manner according to the criteria. It aims to demonstrate as many examples as possible concerning the automation of the SIDOOR ATE530S platform screen doors' controller. • Optimized by symbolic access • Structuring by corresponding data types • Easy to expand thanks to its modular configuration and meaningful groupings

Data exchange The exchange of user data between SIMATIC and the SIDOOR controller is divided into two areas: • Parameter area (PKW)

The PKW area handles the parameter transfer. This involves, for example, reading and writing parameter values.

• Process data area (PZD) The PZD area involves all signals, control words and setpoints, as well as status words and actual values required for the automation.

The contents of the parameter and process data area are defined by the SIDOOR controller.

2 Hardware and software components


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

2 Hardware and software components 2.1 Validity

This application applies to: • TIA Portal V13 SP1 • S7-1500 CPU

2.2 Components used

This application example with two PSD systems was created with the following components.

Required hardware components for sample configuration Table 2-1 Standard hardware components

Components Order number Note

SIDOOR

SIDOOR ATE530S 6FB1231-3BM10-7AT0

SIDOOR MED280 6FB1203-0AT12-7DA0 EC motor, max. 280 kg door weight

SIDOOR Transformer 6FB1112-0AT20-2TR0 Optional: direct voltage supply provided by customer

S7-1500 System

CPU 1516-3 PN/DP 6ES7 516-3AN00-0AB0 Optional other S7-1500 CPU

DI 16/DQ 16x24VDC 6ES7 523-1BL00-0AA0 Or similar

S7 MEMORY CARD, 2 MB 6ES7954-8LB01-0AA0 Optional: more memory

Distributed I/O

ET200SP IM 155-6 PN ST 6ES7 155-6AU00-0BN0

Optional: other distributed I/O components DI 16x24VDC ST 6ES7 131-6BH00-0BA0

DQ 4x24VDC/2A ST or DQ 4x24VDC/0,5A ST

6ES7 132-6BD20-0BA0 6ES7 132-6BH00-0BA0

Miscellaneous

IE FC RJ45 Plug 180 4X2 6GK1 901-1BB11-2AB0 Connector with axial outgoing cable (180°) for connection of SIDOOR control devices to the PROFINET bus cable

IE FC TP Standard Cable GP 6XV1878-2A PROFINET cables

2 Hardware and software components


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Optional SIDOOR hardware components Table 2-2 Optional SIDOOR hardware components

Components Note

SIDOOR motor mounting bracket

For information about this, refer to the SIDOOR system manual \3\.

SIDOOR motor holder

SIDOOR rubber-metal anti-vibration fastening

SIDOOR deflector pulley

SIDOOR deflector unit

SIDOOR door clutch holder

SIDOOR toothed belt

Note The example project was created with the hardware components listed here. Alternatively, other functionally equivalent components can be used. A different parameter assignment or wiring of components may possibly be required for this.

Software components Table 2-3 Standard software components

Target system Components Quantity Order number Note

S7 – 1500 SIMATIC STEP 7 Professional V13 SP1

1 6ES7822-1xx03-xxxx 1) Floating license

1) The order number depends on the type of license ( (license agreement, update service, floating license etc.). For the fully qualified order number, contact your Siemens sales partner or select the required software / license in the Siemens Industry Mall \1\.

Example files and projects The following list includes all files and projects that are used in this example. Table 2-4 Files and projects

Components Note

ATE530S PROFINET GSD file \8\

109477186_ATE530S_PSD_APP(de).pdf This document, description of application

For TIA Portal Version V13 SP1

PlatformScreenDoor_1500_V13_SP1.zip STEP 7 project Example project

PlatformScreenDoor_LIB_V13_SP1.zip STEP 7 library Function blocks and data types

3 Installation and commissioning


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

3 Installation and commissioning The SIDOOR controller shall be commissioned according to the supplied compact operating instructions, see \9\. • Installing the SIDOOR controller and distributed I/O • Connecting the MED280 EC motor • Connecting digital signals • Performing learn run • Wiring PROFINET connectors • PROFINET node naming

WARNING

Risk of injury

Adhere to the installation steps described in the operating instructions and all safety instructions.

Node naming Assign the PROFINET name "ate530s_1" to the first SIDOOR and the name "ate530s_2" accordingly to the second SIDOOR. Follow the exact same procedure for the distributed I/O, for the first ET200SP use the name "et200sp_1", for the second the name "et200sp_2" Use a configuration tool, such as TIA Portal, to do this. The device name is not "case-sensitive". The following IP addresses are used in the sample project: Table 3-1 IP addresses and device names

Components Device name IP address

S7 CPU 1516-3 PLC_1 192.168.0.1

ET-200SP et200sp_1 192.168.0.2

ET-200SP et200sp_2 192.168.0.4

SIDOOR ate530s_1 192.168.0.3

SIDOOR ate530s_2 192.168.0.5

PG/PC - 192.168.0.110

The subnet mask is always "255.255.255.0". No router address is configured.

3 Installation and commissioning


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Topology-based naming In addition the device name can be assigned by the IO Controller on the basis of the topology. Prerequisite is that the topology is structured as planned and that all the devices involved fulfill at least Class B (supporting of LLDP and SNMP). In addition the new device has to have the factory settings (IP address = 0.0.0.0 and device name = "").

Note PROFINET option <Replacing an IO device without exchangeable medium>

Subject to certain conditions, IO devices can also receive their device names without the insertion of an exchangeable medium (such as memory card) or without a programming device. For this purpose, the IO controller uses Ethernet mechanisms (LLDP protocol; Link Layer Discovery Protocol) to analyze the relationships between the individual IO devices and the IO controller. From these relationships, the IO controller detects which IO device was replaced and assigns the configured device name to it.

PROFINET option <Permit overwriting of PROFINET device name>

With S7-1500 CPUs as of firmware version V1.5, you can overwrite PROFINET device names of IO devices during the startup of the CPU. This option reduces the effort during automatic commissioning, for example, when replacing a device.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4 Solution 4.1 Overview

Limitation This application contains no description: • The general drive functions of the SIDOOR controller • The SIMATIC S7-CPU Basic knowledge of these topics is assumed or can be found in the corresponding manuals. Refer to SIDOOR system manual \3\.

Basic knowledge Basic knowledge about configuring PROFINET systems with SIMATIC S7 controllers and the TIA Portal engineering system is assumed. Information and important instructions on installing the SIDOOR controller is available in the SIDOOR ATE530S operating instructions \9\.

4.2 Devices and network Figure 4-1 Hardware configuration – Network view

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Module names The names of the modules are defined as follows: Table 4-1 Hardware configuration – Module names

Module Type Name

PLC_1 DI 16/DQ 16x24VDC/0.5A BA PLC_1_DI16_DQ16_1

et200sp_1 DI 16x24VDC ST et200sp_1_DI16_1

DQ 4x24VDC/2A ST et200sp_1_DQ16_1

et200sp_1 DI 16x24VDC ST et200sp_1_DI16_1

DQ 4x24VDC/2A ST et200sp_1_DQ16_1

ate530s_1 22-byte IO ATE530S_1_IO

ate530s_2 22-byte IO ATE530S_2_IO

Module Configuration: The system functions DPRD_DAT and DPWR_DAT are used to update the process data. These instructions ensure that the data of a DP standard slave are read and written consistently. The I/O addresses of the module "DI 16x24VDC ST", "DQ 4x24VDC/2A ST" and "22 bytes EA" are configured as follows in this project: Figure 4-2 Module configuration DI 16x24VDC ST (ET200SP IM 155-6 PN ST)

Figure 4-3 Module configuration DQ 4x24VDC/2A ST (ET200SP IM 155-6 PN ST)

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Figure 4-4 Module configuration 22-byte IO (SIDOOR ATE530S)

Note All other modules use the standard configuration to automatically update the process image.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.3 Program structure

The figure belows describes the program structure of the application example. Only the relevant blocks are deliberately listed. Additional information on the specific blocks is available in the section Program blocks to .

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.4 Program blocks

Note You can individually change the numbers of the described function blocks.

4.4.1 OB1 - Main

The organization block OB1 is used to control the global digital output signals ENABLE, /ENABLE and OPEN. The PLC tags DCUs_Enable, DCUs_Open are used for this purpose. The function PSD_APPLICATION is also called in OB1 to control the configured door systems. As an additional function, OB1 provides the option of activating a cyclic opening and closing of door systems. This function can be easily enabled with the PLC tag EnableCycleRun .

4.4.2 FC - PSD_APPLICATION

The function PSD_APPLICATION is used to call all functions and function blocks in logical order per door system. To begin with, the function PSD_UPDATE_INPUT_SIGNALS is called to read all inputs signals of the door system's distributed I/O. In the next step, the function block PSD_CNTRL is called for parameter assignment, control and monitoring of the door system. After the function block has been called, the function PSD_UPDATE_OUTPUT_SIGNALS is called to update the output signals.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.4.3 FB - PSD_CNTRL

Concept The function block PSD_CNTRL is used for the parameter assignment, control and monitoring of the door system. The function block implements the control logic of the platform screen door (PSD) and processes both the SIDOOR control signals and the signals of the platform control system and the control center. Figure 4-5 PSD_CNTRL concept

Block interface To begin with the block verifies in each call the validity of the digital input signals InputSignals. If the data of the digital input signals is marked as invalid, automatic door mode is enabled and an isolation of the door system is disabled. For the description of the data type PSD_INPUT_SIGNALS_DAT, refer to UDT - PSD_INPUT_SIGNALS_DAT. Prepared faults/warnings, system conditions and status messages of the addressed system are provided via the output structures Faults, Conditions and Status. The function block PSD_CNTRL is controlled via the command interface DCUCmd. The additionally required status information from the platform's or platform screen door's sensors and control elements is made available to the block logic via the input structure InputSignals. Figure 4-6 FB - PSD_CNTRL

Table 4-2 Parameter FB - PSD_CNTRL

Parameters Declaration Data type Description

SIDOOR_ADDR INPUT HW_SUBMODULE Hardware identifier of the SIDOOR controller's "22-byte I/O" submodule.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed


DCUCmd INPUT UDT - DCU_CMD_DAT Source area for the door command to be transferred

InputSignals INPUT PSD_INPUT_SIGNALS_DAT Source area for the data of the digital input signals.

DisableClosingSounder INPUT Bool DisableClosingSounder = 1: Disables the signal for acoustic/visual signaling when door is closing.

LCPActive INPUT Bool LCPActive = 1: The global digital output signs are set by a local control panel. The PLC's digital outputs are invalid.

OutputSignals OUTPUT PSD_OUTPUT_SIGNALS_DAT Source area for the data of the digital output signals.

Faults OUTPUT PSD_FAULT_MONITOR_DAT Destination area for the fault monitoring data.

Conditions OUTPUT PSD_CONDITION_MONITOR_DAT Destination area for the state monitoring data.

Status OUTPUT PSD_STATUS_MONITOR_DAT Destination area for the status monitoring data.

ERROR OUTPUT Word Error code (corresponds to Table 4-3 Error information FB - SIDOOR_PN_DCU_CNTRL).

EXTNERR OUTPUT Word Detailed information on the error code.

LoadCustomDCUParams IN_OUT Bool LoadCustomDCUParams = 1: Request to write the customer-specific parameter set. The value is automatically reset to 0 after the parameter set has been written.

FaultAck IN_OUT Bool FaultAck = 1: Acknowledgment of a pending fault. The value is reset after the door control unit accepts the fault acknowledgment.

More information on specific data types is available at PLC data types.

FB error information The function block PSD_CNTRL calls the SIDOOR communication block SIDOOR_PN_DCU_CNTRL as multi-instance and forwards its errors via the output parameters ERROR and EXTNERR. No additional error codes are defined.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Intension The logic that is implemented in the function block is the basis/pattern for a user-specific development. As many functions as possible of the SIDOOR controller are therefore described using a representative example.

Control unit The activation of the control unit for the SIDOOR controller is one of the main components of the logic of the function block PSD_CNTRL. In the case of a pending isolation command (DCUCmd.Inhibit), the logic automatically sets the control unit to the state S3:READY_TO_OPERATE. In the case of a command such as Learn run (DCUCmd.StartLearnRun) or Open (DCUCmd.Open) the control unit is automatically switched to the state S4:S4:OPERATING. The controlled SIDOOR controller is automatically enabled, i.e. set to the state S3:READY_TO_OPERATE or S4:S4:OPERATING, if the following conditions are met: • LCP in Automatic mode • Enable request DCUCmd.Enable active • Controller not in ERM mode • Controller requests PLC control To detect errors during activation and incomplete evaluation of the status messages of the SIDOOR controller, the fault Faults.OperatingFailed is set if the control unit of the SIDOOR controller does not switch within 2s from S1:SWITCH_ON_DISABLED state to S2:READY_TO_SWITCH_ON state.

Fault acknowledgement A sample logic for acknowledging a pending fault on the SIDOOR controller is implemented in the function block PSD_CNTRL, see Output Faults.DCUFault and InOut Flag FaultAck.

Signal logic and troubleshooting The faults of the structure UDT - PSD_FAULT_MONITOR_DAT are derived, by way of example, via the implemented logic from the status information of the SIDOOR controller and the platform. This is done both time-driven and event-driven according to the fault.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Application-specific parameter-assignment and cyclic parameter query The function block PSD_CNTRL contains a finite state machine that processes the sample parameter job lists sWriteParamList, sReadParamList and sReadEventList in an event-driven manner. These lists are UDT - SIDOOR_PLST_ENTRY type and can be dynamically extended, modified, moved (to another data block) or centralized.

Note A breakdown into various list is possible but not necessary.

Each individual entry of a parameter job list defines the specific job type . As a result, both read and write jobs can be combined in a list.

The parameter job lists are transferred as point to the communication block FB - SIDOOR_PN_DCU_CNTRL and can therefore be moved to any other data blocks.

Information and further details about the corresponding parameters are available in the "Parameters" section of the system manual \3\. sWriteParamList: This list contains eight parameter write entries that are executed via the rising edge at input LoadCustomDCUParams. All, for example, application-specific parameters that are to be changed in the SIDOOR controller during a commissioning can be entered there. In the application example, the following parameters are changed via the list sWriteParamList: (1) p90 = 1 (Disable door command for service buttons) (2) p1220 = 7 (Configuration of unlocking sequence) (3) p1221 = 250 (On delay door command open/learn run) (4) p1222 = 750 (On period signal UNLOCK0) (5) p1223 = 750 (On period signal UNLOCK1) (6) p1224 = 0 (On delay signal UNLOCK1) (7) p3660 = 12 (Slow end distance open) (8) p3663 = 200 (Slow end distance close) sReadParamList: The sReadParamList list contains 5 parameter read jobs that are updated and evaluated every 30s (defined via the constants TIME_PARAM_READ). (1) p2100[22] (Motor temperature) (2) p2100[23] (Temperature of the controller) (3) p2150[0] (Firmware Version - Major) (4) p2150[1] (Firmware Version - Minor) (5) p2150[2] (Firmware Version - Build/Revision) sReadEventList: Event history for faults and warnings of SIDOOR controller are read out and decoded cyclically every 30s with the help function FC - DCU_DECODE_EVENT_LIST using the sReadEventList (defined via the constant TIME_PARAM_READ). The events are written in the array sEventDataList; the first eight fields contain the faults and the last 8 fields contain the warnings.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.4.4 FB - SIDOOR_PN_DCU_CNTRL

Description Parameter jobs are not individually created at the function blocks, but instead combined in a parameter job list. The complete parameter job list is transferred to the function block via a pointer and automatically processed step by step after this. The figure below shows the described concept.

Figure 4-7 Concept SIDOOR communication module

Operating principle The SIDOOR function block takes over the data processing of exactly one SIDOOR controller. Therefore, the block must be called with one data instance for each SIDOOR bus node. The selected SIDOOR bus node is localized by specifying a HW address identifier. During each calling of the function block the control data is transferred to the controller according to the structure UDT - SIDOOR_CDAT and the current status data updated according to the structure UDT - SIDOOR_SDAT . In addition, the availability of the SIDOOR bus node is checked and the node diagnostics data is updated. Parameter jobs are processed acyclically over several call cycles by the SIDOOR function block. The inputs PKW_PLST, PKW_TIMEOUT and PKW_BACKUP are evaluated only in combination with a rising edge at the input parameter PKW_REQ. Therefore, all "PKW" parameters can be set to 0 or NIL if the parameter channel is to be inactive or not used.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

In the case of rising edge at PKW_REQ, the parameter job list referenced at PKW_PLST is checked. If the list is valid, PKW_CURRLSTID is reset and the processing starts with the first parameter job in the list. When a job from the list is completed, the result is entered directly in the list (FAILED, ACK_DIV and REPORT). If a job was executed, the output PKW_CURRLSTID is incremented. The parameter job list is processed asynchronously and requires several cycles (the duration depends on the length of the list, the block call cycle and the cycle time of the SIDOOR internal bus). The output PKW_REQ remains active as long as processing is in progress. The PKW_REQ output is automatically reset when a communication or diagnostics error occurs during the processing of the job list or when the processing of the list is completed. An active job can be canceled at any time by resetting the input PKW_REQ (the output PKW_CURRLSTID indicates the ID of the last successfully completed job of the parameter job list).

Note After a job, the parameter channel is automatically reset by an empty job. The user does not have to execute this.

The FB can be called in any cycle. However, note that the parameter channel is processed step-by-step. Exactly one step of the parameter job processing is executed with each block call.

1. Checking and starting of the parameter job data according to the current list position.

2. Waiting for feedback from the addressed node. 3. Evaluating of the feedback and enabling of the job interface.

The timeout per parameter list job is limited via the input parameter PKW_TIMEOUT. Depending on the job, the SIDOOR controller requires at least 30ms for the processing (incl. feedback) of a parameter job.

Response in case of a fault If the communication or the block is faulty (ERROR ≠ 0000hex and ≠ 0500hex), no parameter job is accepted. The REPORT and FAILED fields of the parameter job list remain unchanged. All SIDOOR control data (CData) are rejected and all fields of the SIDOOR status data (SData) are set to 0.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

FB error information If an error or a warning occurs during the processing of the function block, the output parameter ERROR contains one of the following error codes. Table 4-3 Error information FB - SIDOOR_PN_DCU_CNTRL

Error code* (W#16#...)

Explanation

0000 Without error, all parameters are valid

0001 Internal block execution was disturbed

0003 Area referenced with PKW_PLST is not Byte type

0004 Field size referenced via PKW_PLST is invalid

0005 Destination area referenced with PKW_PLST is not in a data or instance data block

0006 Block referenced with PKW_PLST is write protected

0010 Error in calling the SFC117 GET_DIAG EXTNERR contains den error code from SFC117

0040 Error in calling the SFC14 DPRD_DAT EXTNERR contains den error code from SFC14

0050 Error in calling the SFC15 DPWR_DAT EXTNERR contains den error code from SFC15

0100 Job timeout, the specified timeout (PKW_TIMEOUT) was exceeded unanswered parameter job

0200 Response cannot be assigned, contains a deviating/unequal parameter number

0400 PKW_AK (Task ID) Unknown – job canceled

0500 Warning: At least one of the list's parameter jobs could not be executed by the node, EXTNERR contains the exact number of the parameter jobs that could not be executed

2000 A diagnostics interrupt is pending

* The error codes can be displayed as integer or hexadecimal values in the program editor.

AK parameter job identifier Table 4-4 Parameter request/job identifier

Job identifier Description Access

0 No job / empty job

1 Request/read PWE parameter value

2 Change/write PWE parameter value 16-bit

3 Change/write PWE parameter value 32-bit

4 Request PBE (parameter description element) *[1]

5 Change PBE (parameter description element) *[1]

6 Request/read PWE parameter value *[2] Array

7 Change/write PWE parameter value *[2] Array, 16-bit

8 Change/write PWE parameter value *[2] Array, 32-bit

9 Request/read number of array elements

*[1] The element number used is transferred in the IND array subindex. *[2] The position in the array is stated in the IND array subindex.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

PBE – Parameter description Refer to SIDOOR system manual \3\. The notation of the parameter description (PBE) states the element number of the parameter description in the IND array subindex.

Response error code If parameter orders cannot be executed, the SIDOOR controller sends the response ID "Order not executable", and transfers the corresponding error ID in the parameter value (PWE). In this case, the FAILED bit of the corresponding parameter job is set. Table 4-5 Error IDs cannot be executed for job

Error ID Description

0 Impermissible parameter ID

1 Parameter value cannot be changed.

2 Parameter limits not observed

3 Sub-index outside the array

4 Parameter is not an array

5 Parameter type is invalid (mismatch word and double word)

102 Communication channel too small for the required response

104 Invalid value, parameter allows only certain values.

106 Request not observed or task not supported.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

Interface Figure 4-8 FB - SIDOOR_PN_DCU_CNTRL

Table 4-6 Parameter FB - SIDOOR_PN_DCU_CNTRL


LADDR INPUT HW_SUBMODULE Hardware identifier of the SIDOOR controller's "22-byte I/O" submodule.

PKW_PLST INPUT Any Pointer to the source area of the parameter job list (array of type SIDOOR_PLST_ENTRY). The pointer must be Byte type and must reference only data or instance data blocks. When job starts (with rising edge at PKW_REQ) the value is buffered inside the block.

PKW_TIMEOUT INPUT Time Maximum processing time per parameter job, before the current parameter job is terminated with a timeout error (default: 500 ms).

PLST_BACKUP INPUT Bool ATTENTION: PLST_BACKUP = 1 this option is used to enable the Backup mode of the function block. In Backup mode, the PWE field of the current job is overwritten with the read parameter value if the read jobs are successful the REPORT and PWE fields are synchronized.

CData INPUT SIDOOR_CDAT Source area of the SIDOOR control data, see UDT - SIDOOR_CDAT.

ERROR OUTPUT Word FB error information

EXTNERR OUTPUT Word Extended FB error information

PKW_CURRLSTID OUTPUT Int List position of the last, successfully processed parameter job (0 if none were processed).

SData OUTPUT SIDOOR_SDAT Destination area of the SIDOOR status data, see UDT - SIDOOR_SDAT.

PKW_REQ IN_OUT Bool PKW_REQ=1 starts the processing of the referenced parameter job list. PKW_REQ=1 terminates the current processing of the referenced parameter job list. Is automatically reset when the processing is completed or an error occurs during processing.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.4.5 FC - PSD_UPDATE_INPUT_SIGNALS

In this application example, the digital control signs of the "Interconnect Board" are read in via the the distributed I/O (ET200SP) for each platform screen door, see Figure 1-1 Platform System Concept. The function PSD_UPDATE_INPUT_SIGNALS reads the process data from the addressed digital input module (DI 16x24VDC ST- 6ES7 131-6BH00-0BA0) and returns a structure of type UDT - PSD_INPUT_SIGNALS_DAT. For this purpose each of the digital input models is to be assigned as follows: Table 4-7 Channel assignment for distributed I/O (digital inputs)

Channel Local signal Channel Local signal

a.0 Automatic mode a.1 Isolate

a.2 Manual mode a.3 Open

a.4 Close a.5 Unlock 1

a.6 Unlock 2 a.7 Closed 1

b.0 Closed 2 b.1 Emergency exit 1 closed

b.2 Emergency exit 1 locked b.3 Emergency exit 2 closed

b.4 Emergency exit 2 locked b.5 -

b.6 - b.7 -

Figure 4-9 FC - PSD_UPDATE_INPUT_SIGNALS

Table 4-8 Parameter FC - PSD_UPDATE_INPUT_SIGNALS


DP_INPUTS_ADDR INPUT HW_SUBMODULE Hardware ID of the digital input module (DI 16x24VDC ST).

InputSignals OUTPUT PSD_INPUT_SIGNALS_DAT Destination area for the decoded input data of the digital input module.

ERROR OUTPUT Word Error code

EXTNERR OUTPUT Word Detailed information on the error code

FC error information If an error or a warning occurs while the function is being executed, the o parameter ERROR contains one of the following error codes. Table 4-9 Error codes FC - PSD_UPDATE_INPUT_SIGNALS


Explanation

0000 No error has occurred.

0040 An error was detecting during read access to the addressed module. Error in calling the SFC14 DPRD_DAT EXTNERR contains the error code from SFC14


4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.4.6 FC - PSD_UPDATE_OUTPUT_SIGNALS

In this application example, the digital control signs of the "Interconnect Board" are read in via the the distributed I/O (ET200SP) for each platform screen door, see Figure 1-1 Platform System Concept. The function PSD_UPDATE_OUTPUT_SIGNALS writes data of type UDT - PSD_OUTPUT_SIGNALS_DAT to the process image from the addressed digital output module (DQ 4x24VDC ST – 6ES7 132-6BD20-0BA0 / 6ES7 132-6BH00-0BA0). For this purpose each of the digital output models is to be assigned as follows: Table 4-10 Channel assignment for distributed I/O (digital outputs)

Channel Local signal Channel Local signal

0 Signaling: Door opens 1 Signaling: Door closes

2 Signaling: Ready to depart 3 -

Figure 4-10 FC - PSD_UPDATE_OUTPUT_SIGNALS

Table 4-11 Parameter FC - PSD_UPDATE_OUTPUT_SIGNALS


DP_OUPUTS_ADDR INPUT HW_SUBMODULE Hardware ID of the digital output module (DQ 4x24VDC ST).

OutputSignals INPUT PSD_OUTPUT_SIGNALS_DAT Source area for the data to be written to the task output group.

ERROR OUTPUT Word Error code

EXTNERR OUTPUT Word Detailed information on the error code

FC error information If an error or a warning occurs while the function is being executed, the o parameter ERROR contains one of the following error codes. Table 4-12 Error codes FC - PSD_UPDATE_OUTPUT_SIGNALS


Explanation

0000 No error has occurred.

0050 An error occurred during write access to the addressed module. Error in calling the SFC15 DPWR_DAT EXTNERR contains the error code from SFC15


4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.4.7 FC - DCU_DECODE_EVENT_LIST

Description All the system faults and warnings are stored retentively in an event list in the SIDOOR controller so that all the events can still be called up chronologically even after a power failure. Each event has a time stamp based on the system start of the SIDOOR controller.

32-bit events list entry

24 bits 8 bits

Seconds since the event entry was added. 0 s if the event entry was added before the last system start. Event code

The function DCU_DECODE_EVENT_LIST decodes a parameter read job element of the type UDT - SIDOOR_PLST_ENTRY in an element of the type UDT - DCU_EVENT_DAT. The function automatically checks the job status and returns an empty DCU_EVENT_DAT in case of a fault (all data fields are hereby 0 and the status code field contains the ASCI character 0x20). Figure 4-11 FC - DCU_DECODE_EVENT_LIST

Table 4-13 Parameter FC - DCU_DECODE_EVENT_LIST


EventParam INPUT SIDOOR_PLST_ENTRY Source area for the data of an parameter job list entry which is to be decoded in a SIDOOR event list entry.

EventData OUTPUT DCU_EVENT_DAT Destination area for the data of the decoded SIDOOR event list entry.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.5 PLC tags The use and interconnection of the following PLC tags is only an example and can be adjusted or extended according to the target application. Table 4-14 PLC tags

Tag Data type Description Address

Platform

DCUs_Enable Bool Global enable signal for all platform screen doors.

M3.0

DCUs_Open Bool Global open Signal for all platform screen doors.

M3.1

LCP_Active Bool The global digital output signals are set by a local control panel. The PLC's digital outputs are invalid local control panel is active.

M3.7

LCP_Enable Bool Enable signal from local control panel M4.5

LCP_Open Bool Open signal from local control panel M4.6

DisableClosingSounder Bool Disables the signal for acoustic/visual signaling when door is closing.

M4.7

Platform screen door 1

DCU_1_Inhibit Bool Platform screen door 1 is set to inhibit. M5.0

DCU_1_StartLearnRun Bool Requests a learn run for platform screen door 1 (requirement must be active for around three seconds at the start of the learn run).

M5.2

Platform screen door 2

DCU_1_Inhibit Bool Platform screen door 2 is set to inhibit. M5.1

DCU_2_StartLearnRun Bool Requests a learn run for platform screen door 2 (requirement must be active for around three seconds at the start of the learn run).

M5.3

Commissioning / test

EnableCycleRun Bool Enables cyclic test run via global digital signals. Attention: Sets "DCUs_Enable" signal and toggles the "DCUs_Open" signal every 7s.

M5.5

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6 PLC data types

4.6.1 UDT - DCU_CMD_DAT

The following table shows the data elements of the PLC data type "DCU_CMD_DAT" and their descriptions: Table 4-15 Structure UDT - DCU_CMD_DAT

Element Data type

Description

Enable Bool Enable = 1: Activation of the enable signal for controlling the door.

Open Bool Open = 1: Activation of the signal for opening the door. Otherwise the door will be closed.

Inhibit Bool Inhibit = 1: Activation to inhibit any controlling of the door.

StartLearnRun Bool StartLearnRun = 1: A positive edge signal of at least three seconds start the learn run of the door control unit. The enable signal "Enable" must be set.

4.6.2 UDT - DCU_EVENT_DAT

The following table shows the data elements of the PLC data type "DCU_EVENT_DAT" and their descriptions: Table 4-16 Structure UDT - DCU_EVENT_DAT

Element Data type Description

Days Int Number of day after system start since the event occurred.

Hours Int Number of hours after system start since the event occurred.

Minutes Int Number of minutes after system start since the event occurred.

Seconds Int Number of seconds after system start since the event occurred.

StatusCode Char Event status code

4.6.3 UDT - PSD_CONDITION_MONITOR_DAT

The following table shows the data elements of the PLC data type "PSD_CONDITION_MONITOR_DAT" and their descriptions: Table 4-17 Structure UDT - PSD_CONDITION_MONITOR_DAT

Element Data type

Description

OpeningBlockCnt USInt Number of obstructions in the opening direction.

ClosingBlockCnt USInt Number of obstructions in the closing direction.

OpenTimeExceedsLimit Bool OpenTimeExceedsLimit = 1: Opening time > 3.5 s

CloseTimeExceedsLimit Bool CloseTimeExceedsLimit = 1: Closing time > 3.5 s

MotorTemp Real Motor temperature

DCUTemp Real Control unit temperature

OpenProfileExceedsLimit Bool OpenProfileExceedsLimit = 1: Limits of the opening profile are exceeded

CloseProfileExceedsLimit Bool CloseProfileExceedsLimit = 1: Limits of the closing profile are exceeded

VandalismProtectionActive Bool VandalismProtectionActive = 1: Continuous door monitoring was enabled.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6.4 UDT - PSD_FAULT_MONITOR_DAT

The following table shows the data elements of the PLC data type "PSD_FAULT_MONITOR_DAT" and their descriptions: Table 4-18 Structure UDT - PSD_FAULT_MONITOR_DAT

Element Data type

Description

EnableFault Bool EnableFault = 1: Illegal state of safe ENABLE signal of door control unit is active.

OpenFault Bool OpenFault = 1: The OPEN signal of the door control unit was enabled without valid ENABLE signal.

EnableCmdFault Bool EnableCmdFault = 1: The Remote-Enable command failed.

OpenCmdFault Bool OpenCmdFault = 1: The Remote-Open command failed.

DoorFailedToOpen Bool DoorFailedToOpen = 1: It could not be opened within a defined period.

DoorFailedToClose Bool DoorFailedToClose = 1: It could not be closed within a defined period.

ERMFault Bool ERMFault = 1: The safe digital input of emergency unlocking on the SIDOOR device is faulty.

ERMInhibitFault Bool ERMInhibitFault = 1: After the off delay of the emergency unlocking there was no door motion despite a valid enable or open/close signal.

CommFaul Bool CommFaul = 1: Faulty PROFINET communication

OperatingFailed Bool OperatingFailed =1: The door control unit could not switch to the "ReadyToOperate" state within the defined time.

LearnRunFault Bool LearnRunFault = 1: Error detected during learn run

DCUFault Bool DCUFault = 1: Fault detected in the door control unit. An acknowledgment of the fault is required.

DCUWarning Bool DCUWarning = 1: Warning detected in the door control unit. An acknowledgment of the warning is not required.

HomingError Bool HomingError = 1: The door control unit could not switch to normal mode after POR.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6.5 UDT - PSD_INPUT_SIGNALS_DAT

The following table shows the data elements of the PLC data type "PSD_INPUT_SIGNALS_DAT" and their descriptions. Table 4-19 Structure UDT - PSD_INPUT_SIGNALS_DAT

Element Data type

Description

DataValid Bool DataValid =1: All elements in the data type are valid:

AutoModeActive Bool AutoModeActive = 1: Automatic mode of door system is enabled.

Isolated Bool Isolated =1: Door system is isolated from the entire system.

ManualMode Bool ManualMode = 1: Manual mode of door system is enabled.

OpenSignal Bool OpenSignal =1: Door-opening signal is enabled.

CloseSignal Bool CloseSignal =1: Door-closing signal is enabled.

Unlocked1 Bool Unlocked1 = 1: Unlocking sensor 1 enabled for door leaf.

Unlocked2 Bool Unlocked2 = 1: Unlocking sensor 2 enabled for door leaf.

Closed1 Bool Closed = 1: End position sensor 1 enabled for closed position.

Closed2 Bool Closed = 1: End position sensor 2 enabled for closed position.

EmerDoor1Closed Bool EmerDoor1Closed = 1: Emergency door 1 closed.

EmerDoor1Locked Bool EmerDoor1Locked = 1: Emergency door 1 locked.

EmerDoor2Closed Bool EmerDoor2Closed = 1: Emergency door 2 closed.

EmerDoor2Locked Bool EmerDoor2Locked = 1: Emergency door 2 locked.

4.6.6 UDT - PSD_OUTPUT_SIGNALS_DAT

The following table shows the data elements of the PLC data type "PSD_OUTPUT_SIGNALS_DAT" and their descriptions. Table 4-20 Structure UDT - PSD_OUTPUT_SIGNALS_DAT

Element Data type

Description

ClosingSounder Bool ClosingSounder = 1: Signal for acoustic/visual signaling when door is closing. The signal has the value 1 until the door is closed.

OpeningLight Bool OpeningLight = 1: Signal for acoustic/visual signaling when door is opening. The signal has the value 1 until the door is closed.

ReadyToDepart Bool This signal is not currently used and can be freely used.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6.7 UDT - PSD_STATUS_MONITOR_DAT

The following table shows the data elements of the PLC data type "PSD_STATUS_MONITOR_DAT" and their descriptions. Table 4-21 Structure UDT - PSD_STATUS_MONITOR_DAT


UnlockOutputSet Bool UnlockOutputSet = 1: The SIDOOR device has set the digital output for door unlocking.

DoorFullyOpen Bool DoorFullyOpen = 1: The door has reached Open position and is fully open.

DoorObstructed Bool DoorObstructed =1: The door was obstructed in opening or closing direction.

ERMActive Bool ERMActive = 1: The safe digital input of emergency unlocking on the SIDOOR device was enabled.

OpenCmd Bool OpenCmd = 1: The digital input for opening the door on the SIDOOR device was enabled.

EnableCmd Bool EnableCmd = 1: The safe digital input for enabling the door on the SIDOOR device was enabled.

AutoMode Bool AutoMode = 1: The digital input for reading in the automatic mode at the distributed I/O was enabled.

IsolateMode Bool IsolateMode = 1: The digital input for reading in the isolation mode at the distributed I/O was enabled.

ManualMode Bool ManualMode = 1: The digital input for reading in the manual mode at the distributed I/O was enabled.

DoorClosed Bool DoorClosed =1: The door has reached closed position and is fully closed.

DoorClosing Bool DoorClosing = 1: The door travels from open position to closed position.

DoorOpening Bool DoorOpening = 1: The door travels from closed position to open position.

DateSet Bool DateSet = 1: The open and closed positions were determined by SIDOOR devices.

DoorInhibit Bool DoorInhibit = 1: Alarm to inhibit a door from opening.

RemoteEnableCmd Bool RemoteEnableCmd = 1: Remote-enable signal to the SIDOOR device is enabled.

RemoteOpenCmd Bool RemoteOpenCmd = 1: Remote-open signal to the SIDOOR device is enabled.

LearnRunComplete Bool LearnRunComplete = 1: Confirmation from SIDOOR device that the learn run was completed successfully.

SoftwareVersionNumber Array[0..2] of Word

Software version of SIDOOR device built on major version, minor version and build version.

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6.8 UDT - SIDOOR_CDAT

The data type SIDOOR_CDAT maps the process data structure of the SIDOOR control data. For information about this, refer to the SIDOOR system manual \3\ TSW0-1 (technology control words). Table 4-22 Structure UDT - SIDOOR_CDAT


CrlW Struct Control word 1 (STW1)

ON_OFF1 Bool ON_OFF1 = 1 Switch drive ready to operate (master switched on and voltage ready) ON_OFF1 = 0 Not ready to switch-on (master switched off and voltage off) switch-off according to defined ramp → corresponds to stop Note: The positive edge is decisive (0 → 1).

NoOFF3 Bool NoOFF3 = 1 OFF 3 command is canceled NoOFF3 = 0 Fast stop of the drive, halt motor, i.e. stop

EnableOperation Bool EnableOperation = 1 Enable operation, execution of the door commands (evaluation of technology control words) EnableOperation = 0 No execution of the door commands

AckFault Bool AckFault = 1 Acknowledge fault AckFault = 0 No meaning Note: The positive edge is decisive (0 → 1).

CtrlFromPLC Bool Control via PLC PLC control (IO controller) Process data are marked as valid, and are thus accepted and effective CtrlFromPLC = 0 No PLC (IO controller) control process data invalid, local operation, possible signs-of-life are excluded from this (master monitoring) Note: First set to bit to 1 when control has been requested from IO device (ZSW1 Bit 9 = 1)

DCMD Byte Door command / drive order (enumerative)

DCMDExten Struct Extension / modification of the door commands

SlowActive Bool Slow door profile

SpecialActive Bool Special mode

DCOPSActive Bool Door Closed / Opened Position Sensor

DRSActive Bool Reversing function

DESTPos Word Position specification in [mm] (only valid in combination with specific drive order)

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6.9 UDT - SIDOOR_SDAT

The data type SIDOOR_SDAT maps the process data structure of the SIDOOR status data. Refer to SIDOOR system manual \3\ TZW0-5 (Technology status words). Table 4-23 Structure UDT - SIDOOR_SDAT


StatW Struct Status word (StatW)

ReadyToSwitchOn Bool Ready to switch-on

ReadyToOperate Bool Ready to operate

OperationEnabled Bool Enable operation

Fault Bool Fault (fault present)

NoOFF3 Bool No OFF 3 (no fast stop)

SwitchOnInhibit Bool Switch-on inhibit

Warning Bool Warning (warning active)

PLCCtrlRequested Bool PLC control requested

CmdDiscrepancy Bool Command discrepancy

DStat Byte Current door state (enumerative)

DMode Byte Current door mode (enumerative)

WaitCmd Bool WaitCmd = 1The system suppresses the current door command and waits for a door command change.

MotMode Bool MotMode = 1 Motor energized.

ERM Bool ERM = 1 Emergency unlocking mode active, system is freewheeling and motor de-energized.

DReverse Bool DReverse = 1 Door reverses, the controlled direction of movement is inverted.

FINHIBCLS Byte Deviation of the inhibiting force in the closing direction against the friction determined in the last learn run as a percentage (enumerative).

FINHIBOP Byte Deviation of the inhibiting force in the opening direction against the friction determined in the last learn run as a percentage (enumerative).

DBlk Struct Obstruction of the door.

BlkOpeningActive Bool BlkOpeningActive = 1 Obstruction in the opening direction was detected.

BlkClosingActive Bool BlkClosingActive = 1 Obstruction in the closing direction was detected.

BlkStat Bool BlkStat = 1 Configured response to a detected obstruction is active (e.g. door reversed).

StatCode Byte Current status code of the operating status display (signal contains the ASCII code of the character for operating state display)

DIn Struct Digital inputs

InputActive_0 Bool InputActive_0 = 1 Input 0 active (DIN0)




4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed



SDIn Struct Status of safe digital input signals

SDIn0_Active Bool SDIn0_Active = 1 Output safe FBLOCK SAND0 is active

SDIn1_Active Bool SFIn1_Active = 1 Output of safe FBLOCK SAND1 is active

SDInFault Struct Error status of safe digital input signals

SDIn0_Active Bool SDIn0_Active = 1 safe FBLOCK SAND0 in "Fault"

SDIn1_Active Bool SDIn1_Active = 1 safe FBLOCK SAND1 in "Fault"

SFIn Struct Status of safe frequency-based input signals

SFIn0_Active Bool SFIn1_Active = 1 Output of safe FBLOCK FRQ0 is active

SFIn1_Active Bool SFIn1_Active = 1 Output of safe FBLOCK FRQ1 is active

SFInFault Struct Error status of safe frequency-based input signals

SFIn0_Failed Bool SFIn0_Failed = 1 safe FBLOCK FRQ0 in "Fault"

SFIn1_Failed Bool SFIn1_Failed = 1 safe FBLOCK FRQ1 in "fault"

DOut Struct Digital outputs

OutputActive_0 Bool OutputActive_0 = 1 Output 0 active (DQ0)

OutputActive_1 Bool OutputActive_1 = 1 Output 1 active (DQ1)

SysLoad Byte Current total system load in [%] (comprised from motor and control unit together)

DPos Byte Door position in % (note: The value is only valid in normal mode. The door positions 100% and 0% can only be reached in combination with the "Open" and "Close" door commands. The door positions 99% and 1% correspond to fully open and fully closed without an active door command. Values between 99% and 1% specify the door position as a percentage. If no valid position value is available, 127 is transferred (> 100%).

VMon1 Word Variable monitoring value 1 (configured via parameter p4700).

VMon2 Word Variable monitoring value 2 (configured via parameter p4701).

4 Solution


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

4.6.10 UDT - SIDOOR_PLST_ENTRY

The data type SIDOOR_PLST_ENTRY maps the structure of a parameter list entry. After the parameter job has been processed via the elements provided by AK, NUM, IND and PWE, the elements FAILED, ACK_DIV and REPORT are written by the function block SIDOOR_PN_DCU_CNTRL. Table 4-24 Structure UDT - SIDOOR_PLST_ENTRY


AK Byte Parameter job identifier, see AK – parameter job identifier.

NUM Int Parameter number (ID)

IND Byte Field index

PWE DInt Parameter value (only for write jobs AK=2,3,5,7,8 relevant)

FAILED Bool FAILED = 1 Parameter job not executable by node, REPORT element contain the corresponding response error code, see Response error code.

ACK_DIV Bool Acknowledgment value in the REPORT element deviates from job value PWE (with write job AK=2,3,5,7,8 only)

REPORT DInt For read job (AK=1,4,6,9) read parameter value For write job (AK=2,3,5,7,8) written parameter value (Acknowledgment) For job error (FAILED=TRUE) Response error code

5 Literature references


S

iem

ens

AG 2

015

All r

ight

s re

serv

ed

5 Literature references Topic Title

\1\ Siemens Industry online support

http://support.automation.siemens.com

\2\ Download page of the entry

https://support.industry.siemens.com/cs/en/en/view/109477186

\3\ SIDOOR system manual

http://support.automation.siemens.com/WW/view/de/109477185

\5\ TIA-Portal SP1 https://support.industry.siemens.com/cs/ww/en/view/109311724 \7\ SIMATIC S7-1500 http://support.automation.siemens.com/WW/view/de/59191792 \8\ ATE530S

PROFINET GSD file


\9\ Compact operating instructions


6 Contacts Siemens AG Digital Factory Division P.O. Box 23 55 90713 Fürth Germany E-mail: [email protected]

7 History Version Date Change

V1.0 09/2015 First edition

http://support.automation.siemens.com/

https://support.industry.siemens.com/cs/de/de/view/109477186


https://support.industry.siemens.com/cs/ww/en/view/109311724




mailto:[email protected]

safety-oriented automation of platform screen doors€¦ · platform screen doors (psds) up to 280...

Documents