pss-range modular and compact pss -...

Programmable control systems PSS®

PSS-RangeModular and compact PSS

ST System Description – Item No. 18 587-09

��

�� !��

��"#��$%"#��&$"#��'()"#��"#�� *'"#�� "#��+$ "#� ��,- ��"#� ��*.*"# ��'*%��"#��"�� /��

PSS-Range: ST System Description 1

Contents

Introduction 1-1

Definition of symbols 1-2

Overview 2-1

PSS-range 2-1Failsafe section 2-1Standard section 2-2Hardware 2-2Modular PSS 2-2Compact PSS 2-3Configuration and programming 2-4

Safety 3-1

Safety guidelines 3-1

Structure (hardware) 4-1

Compact controller 4-1Modular controller 4-1Power supply 4-2Battery 4-2CPU 4-3Memory 4-3PG interface 4-6User interface 4-6Timer 4-7

32-bit timer 4-8Counters 4-8CPU display 4-8Selector switch 4-9

PSS-Range: ST System Description2

Contents

Error stack button 4-9Input/output modules 4-10

Programming 5-1

Programming model 5-1Creating a project 5-3Program transfer 5-4Addressing 5-5Organisation blocks 5-6Standard function blocks 5-7

Standard function block SB254 5-7

Operation 6-1

Communication with the periphery 6-1Direct periphery access 6-1Periphery access via process images 6-2Program cycle 6-3Blocks which are executed once 6-3Blocks which are executed cyclically 6-4Scan time and the block run times 6-6Self-test 6-7Registered hardware 6-7Start adresses of word modules 6-7

Offset für freie Adressierung 6-9Actual configuration 6-10Hardware registry test 6-11Output on the CPU display 6-12Adjusting the system time of the safety system 6-13Select FS data block 6-14Communication with the FS section 6-15

PSS-Range: ST System Description 3

User interface in the ST section 6-18Forming networks 6-19

3rd generation controller networks: 6-191st and 2nd generation controller networks 6-20

Handshaking 6-20Communication protocol 6-21

Data transfer without protocol 6-21Transfer with ISI protocol 6-22

Configuration of the user interface 6-25Interface configuration DB (DB006) 6-26Example 6-29

Sending via the user interface 6-30Send-DB 6-31Example 6-32

Receive via the user interface 6-33Receive-DB 6-34Example 6-35

Operating states and changes 6-36Operating statuses 6-37Change in operating status 6-38

Commissioning 7-1

Initial commissioning 7-1Recommissioning 7-2Changing the configuration or the user program 7-3General reset 7-3

Fault diagnostics and rectification 8-1

Error management 8-1Minor errors 8-2Fatal errors in the ST section 8-3Fatal errors in the FS section 8-4Error stack 8-5Display of errors as plain text 8-7

PSS-Range: ST System Description4

Contents

Display of errors on the CPU display 8-8Display on 1st and 2nd generation controllers 8-8Display on 3rd generation controllers 8-10Evaluation of the error parameters 8-15

Diagnostics 8-21Control/force variables 8-21Display of variables 8-22Dynamic program display 8-23

Appendix 9-1

System data blocks 9-1DB000 9-1DB004 9-8DB005 9-8DB006 9-9DB007 9-11DB008 9-12DB009 9-13Operating system calls with SB254 9-14Changes in the documentation 9-15

Index 10-1

PSS-Range: ST System Description 1-1

This System Description forms part of the PSS system manual. It explainshow the standard section of the PSS-range of programmable safetysystems functions and operates. This description is divided into thefollowing chapters:

1 Introduction

2 OverviewProvides information about the most important features of a safetysystem.

3 SafetyContains safety guidelines.

4 Structure (hardware)Explains the structure of the hardware and the functions of theindividual system units.

5 ProgrammingDescribes the programming and the addressing for the safetysystems.

6 OperationExplains the PSS system processes and the changes which can bemade by the operator.

7 CommissioningExplains the procedure during initial commissioning and after a reset,e.g. after a fault.

8 Fault diagnostics and correctionExplains how fault messages are evaluated and how faults can berectified.

9 AppendixContains the assignment of the system data blocks and an overviewof the operating system calls with SB254.

10 Index

Introduction

1-2

Introduction

PSS-Range: ST System Description

Definition of symbols

Information in this manual that is of particular importance can be identifiedas follows:

DANGER!

This warning must be heeded! It warns of a hazardous situation whichposes an immediate threat of serious injury or death and indicatespreventive measures that can be taken.

WARNING!

This warning must be heeded! It warns of a hazardous situation whichcould lead to serious injury or death and indicates preventive measuresthat can be taken.

CAUTION!

This refers to a hazard that can lead to a less serious or minor injury plusmaterial damage, and also provides information on preventive measuresthat can be taken.

NOTICEThis describes a situation in which the unit(s) could be damaged and alsoprovides information on preventive measures that can be taken.

INFORMATIONThis gives advice on applications and provides information on specialfeatures, as well as highlighting areas within the text that are of particularimportance.


PSS-range

The PSS-range comprises modular and compact programmable safetysystems.The programmable safety systems from the PSS-range are suitable foruse in safety circuits in plants and machinery. The safe status of thesecircuits is brought about by shutting down the energy supply.Each programmable safety system incorporates a failsafe section (FSsection) and a non-failsafe - or standard - section (ST section) into a singleunit.

Overview

��

��

�� !"#

��$�%��

Fig. 2-1: Functions of the FS section and the ST section

Failsafe section

The failsafe section (FS section) processes all of the safety-relevant tasksand is designed with multi-channel diversity. Each channel has its ownmicroprocessor which processes the FS user program. If the microproces-sors are not identical, the controller will immediately switch to a safe condi-tion and switch off all the outputs.The FS user program is created and then, once taken into operation,approved by a body for official approval, such as the BG or TÜV, or by thecompany’s internal test/quality control department.The FS section and the ST section communicate without feedback. Thismeans that errors in the user program of the ST section will have no effecton the FS section and vice versa.

2-2

Overview


Standard section

The standard section (ST section) processes all non-safety-relevant tasksand operates in the same way as a conventional PLC (e.g. P10 from Pilz).It has a single-channel structure.A separate ST user program is created for the ST section. It can run inde-pendently of the FS user program.The FS section and the ST section communicate without feedback. Thismeans that errors in the ST user program will have no effect on the FSsection and vice versa.

Hardware

Modular PSS

The basic system of a modular safety system comprises a module rack, apower supply and a CPU. Various periphery modules can be plugged ontothe module rack. Depending on the design of the module rack, both FSand ST modules can be plugged in.The FS and ST modules communicate via separate buses (backboardbus) with the CPU module.

Fig. 2-2: Example of a PSS 3000 layout (from left to right): Power supply, CPU, 4 FSmodules and 5 ST modules


Fig. 2-3: PSS 3074 with power supply, CPU and periphery (example)

��

�

��

��

��

��

��

��

��

�

��

��

��

��

��

��

��

�

��

��

�

��

��

�

��

��

�

��

��

�

��

��

�

��

�� !

��

��

��

��

��

��

�

��

��

�

��

��

�

��

��

�

��

��"��"��"��"��

�

��

��

��

��

Compact PSS

On the compact PSS, the power supply, CPU and periphery modules arefixed in a housing.

2-4

Overview


Configuration and programming

A PSS-range safety system needs to be configured and programmed foroperation. The data are combined into a so-called project. This project iscreated and maintained using the system software PSS WIN-PRO.The computer on which the PSS WIN-PRO system software is installed isreferred to as the programming device.

Programming can be performed in three different programming languages:the text-oriented programming language Instruction List (IL), plus thegraphical programming languages Function Block Diagram (FBD) andLadder Diagram (LD).


Safety guidelines

Refer to the safety guidelines in the operating manual for the safety systemused.

WARNING!The standard part of a safety system must only be used for non-safety-relevant applications.

Safety

3-2

Safety


Notes


Compact controller

A compact controller combines the following units in a single housing:

• Bus

• CPU (1)

• Power supply (2)

• Input and output modules (3)

Structure (hardware)

Fig. 4-1: Layout of a compact controller using the PSS 3056 system as an example

&

'

(

'

Fig. 4-2: Layout of a modular controller using the PSS 3000 system as an example

1

52 3 4

Modular controller

The modular safety systems are composed of the following units:

• Module rack (1)

• Power supply (2)

• CPU (3)

• Central input and output modules for the FS section (4) and ST section(5)


4-2 PSS-Range: ST System Description

The base unit consists of a base module rack, power supply and CPU.Input and output modules are required to input and output data.There are different base module racks. On some base module racks youcan use only FS modules or only ST modules, whereas on other basemodule racks you can use a combination of both FS and ST modules.

Two additional expansion module racks for ST modules can be connectedto a series PSS 3000 base module rack. This provides an additional 16slots for ST modules.The expansion module racks are connected via expansion modules. Theexpansion module for the base module rack is called PSS EPBM, the onefor the expansion module rack PSS EPEM.

For accurate information about the module racks please refer to the "Instal-lation Manual" of the modular safety system and the descriptions of themodule racks.

Power supply

The power supply provides the internal supply voltage to the CPU and bus.Power supplies are available for different supply voltages, e.g. 230 V ACand 24 V DC.The power supply on modular safety systems must always occupy the firstslot on the rack.

Battery

The battery acts as a buffer for the CPU memories.On modular programmable control systems, the battery is located withinthe power supply. If the CPU or power supply is removed from the modulerack, the data will be retained in the memory for one day.

On PSS with an FS operating system version >= 70, the unit can also beoperated without a battery. Operation without a battery results in thefollowing restrictions:

• FS section: Remanant data blocks cannot be used.

• ST section: A general reset is performed each time the section switchesfrom STOP-RUN.


• Each time the PSS is restarted (voltage switched off and then on again),the system time is reset to zero.

A setting must be configured to determine whether the unit is to beoperated with or without a battery; this is done under the “Basic Settings”tab in PSS WIN-PRO’s PSS Configurator. If the “Operate PSS withoutbattery” option is selected, the unit will operate without a battery,irrespective of whether or not a battery is available.

CPU

The CPU is the safety system’s central processing unit. It controls the inputand output modules, and processes and stores the FS and ST user pro-gram. The CPU has different operating elements and interfaces, e.g.:

• 4-digit display

• LEDs for operating mode and mains voltage

• 3-position switch for selecting the operating mode of the ST section (STselector switch)

• Button for scrolling through the error stack

• 2-position switch for selecting the operating mode of the FS section (FSselector switch)

• Serial programming device interface or Ethernet-2 interface

• User interface

In the CPU the FS user program is processed by independent micropro-cessors. One of these computers also processes the ST section. Thiscomputer has its own bus system for communicating with the inputs/out-puts on the central ST I/O modules.

Memory

The CPU makes available the following memories for the ST section:

• Program memory

• Data memory

Some memories are non-volatile. Non-volatile means that data is retainedin the event of a power failure.



Program memoryThe microprocessor which processes the ST user program has a separatememory for the ST user program. Depending on which operations areused in the user program and how many data blocks are used, theprogram memory can store between 4,000 and 5,000 operations. Thirdgeneration systems can have up to 10,000 operations. The programmemory is checked by CRC and is non-volatile.

Data memoryVariable data such as set data, error messages and system data arestored in the data memory. The size of the data memory will depend on thesafety system used.The data memory is divided into data blocks which each have a maximumof 1,024 memory cells. Each memory cell has a length of 16 bits and iscalled a data word (DW). Bit 0 ... 7 of the data word is referred to as theright data byte (DR) and bit 8 ... 15 as the left data byte (DL).

There are two types of data blocks:

• Read-only data blockscan only be read by the user program, data is non-volatile

• Read/write data blockscan both be read and written to, data is non-volatile (Exception: whenPSS is operated without a battery)

The data memory is divided in a similar manner:

• Read-only data memoryIt is stored in the program memory and contains the read only datablocks

• Read/write data memoryContains the read/write data blocks.

PSS operated without a battery:Values are pre-assigned to the read/write data blocks duringprogramming. The system operates with these values once the userprogram has been downloaded to the programmable control system; thevalues can also be overwritten by the user program. If the user programis stopped and restarted, a general reset is performed and any valuesthat have been modified will be lost. The user program will restart withthe values entered during programming.


PSS operated with a battery:Values are pre-assigned to the read/write data blocks during program-ming. Once the user program has been transferred to the safety system,these values are then used and can also be overwritten by the userprogram. If the user program is stopped and restarted, it continues withthe values which have already been changed. As the memory is non-volatile, changed values are retained even if the safety system isswitched off, and they are reused when the safety system is restarted.In order to ensure that it is possible to restore the ST section to itsoriginal status (general reset), a copy of every read/write data block issaved in the program memory directly after the transfer of the userprogram to the safety system. During a general reset, the values fromthis copy are pre-assigned to the read/write data blocks.



PG interface

The communications between the programming device (PG) and thesafety system take place via a PG interface.

• Serial PG interfaceEach safety system has a serial PG interface.Depending on the type of safety system being used, the PG interface isdesigned either as an RS-485 or as a combined RS-232/RS-485 inter-face.Depending on the design of the PG interface on the safety system, itmay be necessary to use a PAP interface adapter to connect theprogramming device with the safety system (see chapter 5, "Programtransfer").

• Ethernet-2 interface as PG interfaceIf a safety system has an ETH-2 interface, then this interface can also beused as the PG interface (see operating manual of the compact safetysystem or the module with Ethernet-2 interface).

User interface

The user interface can be used for communication between the safetysystem and other devices (refer also to the chapter "Operation", section"User interface ST section").

Depending on the type of safety system, the user interface is designedeither as an RS-232 or as a combined RS-232/RS-485 interface. Thefollowing data are defined in the default setting:

• Transmission rate: 9600 bit/s

• Parity: Even

• Stop bit: 1

• Data bit: 8

• Handshaking: On

• Timeout time when receiving: 15 ms

• Timeout time when sending: 5,000 ms


The standard settings are defined in data block DB006. The data block canbe edited, and the user interface can be configured with other data. Datablocks DB007 and DB008 are used as the send and receive buffers.The user interface is operated with the standard function block SB254,FUNK = 0 ... 11 (see chapter "Operation", section "User interface STsection").

Timer

The ST section is equipped with 64 timers: T000 ... T063.The timers are used to create switch-on delaysThe switch-on delay arises as follows:

Time = Time value x Time base

Time value: Any value in the range 1 ... 32767

Time base: 0 corresponds to 50 ms1 corresponds to 100 ms2 corresponds to 1 s3 corresponds to 10 s4 corresponds to 1 min

Example: Time should be 8 sTime base: 2, time value: 8Time = 1 s x 8 = 8 s

The ST section has read access to the timers T064 ... T127 of the FSsection.



32-bit timer

Safety systems with an FS operating system version ≥ 38 have a32-bit timer.The timer is a consecutive timer, on which the bit changes at 1 ms intervals.The timer has a data width of 32 bits.The current timer status at the time of the call is returned for every operatingsystem call SB254, FUNK = 151.

For information on application of the SB254 please refer to the section"Standard function block SB254" in chapter "Programming".

Counters

The ST section has over 64 counters: Z000 ... Z063.Each counter consists of a counter word and a status bit. The counter wordcan assume values between -32768 and 32767. If the value of the counterword is > 0, then the status bit assumes the value 1.

The ST section has read access to the counters Z064 ... Z127 of the FSsection.

CPU display

The 4-digit hexadecimal display is used to output error messages (seechapter 8) or user messages (see chapter 6, section "Output on the CPUdisplay").

Block

SB254

DB001

Input

FUNK = 151

Output

ERG = 4

ERG = 16

DW200

DW201

Key

Poll 32-bit timer

Function performed without error

Error during call of the SB254,FUNK = 151

Low-order word of timer status

Higher-order word of timer status


AUTO PG

SPS ST

PG

AUTO PG

SPS ST

PG

AUTO PG

SPS ST

PG

Program starts up automatically.The programming device has read and write access.

Program starts up automatically.The programming device is only granted read access.

The program has stopped.The programming device has read and write access.

Selector switch

The programmable safety system is equipped with two selector switches:

• ST selector switch3-position selector switch for the standard section

• FS selector switch2-position selector switch for the failsafe section (see FS System De-scription)

The ST selector switch has the following functions:

Error stack button

Error messages are saved in an error stack. The current error message isalways displayed on the CPU display. To display the previous error mes-sage, press the error stack button (see chapter 8, section "Display oferrors on the CPU display").



Input/output modules

There are a variety of central input/output modules available for communi-cation between the safety system and the plant or machine.

• Digital input module with 32 inputs

• Output module with 32 single-pole 2 A outputs

• Input/output module with 16 inputs and 16 outputs

and others

5-1PSS-Range: ST System Description

Programming model

It is necessary to create a so-called "project” in order to operate aPSS-range programmable safety system. All the necessary files are com-bined within this project. The project is created and maintained usingPSS WIN-PRO.

Programming

Fig. 5-1: Programming model

��

��

(,

� � ��0,�12 3

,� ��0,

,

�,

0,

2,

��

��

2 ��

(,

� � ��0,�1 %3

,

�,

0,

2,

��

��

%��

��

��

5-2

Programming


The project consists of the PSS configuration, the diagnostic configurationand one project section each for the safety system’s FS and ST section.If only one section of the PSS is being used, only the correspondingproject section will be processed. The other project section is available, butremains unchanged.

The project section includes the actual program that is transmitted to thePSS plus the allocation table.

Symbols can be assigned to the operands in the allocation table, for exam-ple the symbol "START" to the operand "E02.08".

For the sake of clarity, the program is divided into blocks. There are fivedifferent types of blocks:

• Organisation blocks (OB), which form the interface between the userprogram and the operating system

• Program blocks (PB), which contain fundamental and plant-specificfunctions

• Function blocks (FB), which are made up of functions for specific indi-vidual tasks

• Standard function blocks (SB), which carry out standardised functions

• Data blocks (DB), which contain fixed or variable data

The PSS configuration contains all of the key settings for the safetysystem.

• Basic settings (e.g. PSS type, scan time, ...)

• Registered hardware

• Test pulse configuration

• Alarm configuration for PSS and SafetyBUS p

• Configuration of word modules

• Definition of password for the FS section

The PSS configuration is generated using the PSS configurator on PSSWIN-PRO. The data are stored in system data blocks.


PSS WIN-PRO (from Version 1.3.1) can be used to create a diagnosticconfiguration for a PSS with an FS operating system version ≥ 47. Thisdiagnostic configuration enables detailed PSS event messages.

If the PSS is to be connected to a SafetyBUS p network, a SafetyBUS pconfiguration will have to be generated for this network. This will containinformation on the structure of the network and all the connected devices.The data for the SafetyBUS p configuration are stored in the projects of allthe programmable safety systems connected to SafetyBUS p.The SafetyBUS p configuration is generated using the SafetyBUS pconfigurator on PSS WIN-PRO.

Creating a project

Steps to take to create a project:

• Create project

• Create PSS configuration

The following steps are identical for the FS and ST project sections. Theymust be performed for both project sections.

• Create an allocation table

• Program the blocks

• Link the programAfter the project has been created, the FS program and the ST programneed to be linked. The programming is checked in the process.If any errors are found, these will need to be rectified and the linkingprocess performed again. The program cannot be transferred to theprogrammable safety system until it has been linked without error.

• Transfer the programSee next section

INFORMATIONCreating projects is covered in detail in the online help of PSS WIN-PRO.

5-4

Programming


Program transfer

Fig. 5-2: Program transfer via the serial PG interface

#$%&'%#

�(��

��

��

��

�� )��

#$%&'%#

Interface adapter(e.g. PSS CONV RS 232/485)

The linked program is transferred to the safety system by activating amenu item in the system software (PG). To do this, the programmingdevice must be connected to the safety system.

The connection can be established via the serial PG interface of the safetysystem or, if available, via the ETH-2 interface. If the connection is estab-lished via the serial PG interface, then, depending on its design (RS-485interface or combined RS-232/RS-485 interface), you may require anadditional PAP interface adapter. To set up the connection via an ETH-2interface, please refer to the operating manual of the compact safety sys-tem or the module with Ethernet-2 interface.

The ST user program is transferred block by block to the safety system.The transfer starts with a so-called preliminary telegram which containsthe name of the project. The remaining blocks are transferred once anerror-free response to the telegram has been received from the safetysystem.To prevent manipulations, the program must be linked before it is trans-ferred, and it can only be read back in its linked form from the safety sys-tem. Amendments can only be made to the original program, not the linkedversion.

Interface adapter(e.g. PSS CONV RS 232/485)


Addressing

The address of a central module results from its slot. Each slot is thendivided further into two sub-slots.With the modular safety systems, the first sub-slot usually corresponds tothe first two plugs and the second sub-slot to the 3rd and 4th plugs on themodule.

The way in which the slots and sub-slots are arranged on compact safetysystems varies from system to system. Details for each case can be foundin the operating manual of the relevant compact controller.

Each slot is allocated a slot number. The digital inputs and outputs areaddressed through the slot number and a bit number. The two entries areseparated by a full stop.

On modular safety systems the first two slots are always occupied by thepower supply and the CPU. Subsequent numbering starts from 0.

Fig. 5-3: Addressing of slots using the PSS 3000 and PSS 3100 as examples

0

1

2

3

4

5

6

7

8

9

10 12

13

14

15

1016

17

0 1 2 3 4 5 6 7 8

11PS CPU

PSS 3100

PSS 3000

Slots

Sub-slots

Sub-slots

5-6

Programming


Example: Bit 8 of the module in slot 3 is to beaddressed.

Address: 3.8

Modules which have more than 32 bits are called word modules. The wordmodules of the ST section are freely addressable, i.e. the addresses canbe chosen from the range 0 ... 16383. The "Programming Manual” of thePSS WIN-PRO system software contains a detailed description of freeaddressing.

Organisation blocks

The functions of the organisation blocks (OB) are set by the operatingsystem. Each user program must contain the cycle organisation blockOB001, which among other things, manages the program cycle. Theblocks of the user program are called up in the cycle OB. All other organi-sation blocks are reserved for specific applications, but they do not neces-sarily have to be used.

INFORMATIONThe "PSS WIN-PRO Programming Manual" contains information aboutwhich organisation blocks there are and what their functions are.


Standard function blocks

Standard function blocks (SB) contain the standard functions which areshared by several machines or plants. Standard function blocks are dividedinto two groups:

• Available SBsSB002 ... 199 are freely available. They can be used for any functions.Exception: SB003, SB007, SB011, SB015 and SB041 are reserved.

• Pre-defined/reserved SBsSB001, SB003, SB007, SB011, SB015, SB041, SB200 ... SB255 arepre-defined and are supplied by Pilz.

The pre-defined standard function blocks are tested and approved bythe relevant approval bodies (e.g. BG, TÜV). To prevent any changes frombeing made at a later date they are encrypted to level 2, which means thatalthough they can be called up they cannot be edited. The dynamic pro-gram display of these modules in PSS WIN-PRO’s online mode is alsounavailable.The pre-defined standard function blocks are described in detail in the"PSS WIN-PRO Programming Manual".

Standard function block SB254

The standard function block SB254 is used for communications betweenthe ST section and the operating system. It is used for the so-called oper-ating system calls.

The standard function block can be called up via the operation "CAL" or"CALC" in the user program. It has the following layout:

SB 254 StBsCall

W FUNK ERG W

5-8

Programming


The function of the block is defined by the input parameter "FUNK". De-pending on the function, additional parameters may be required. These arespecified in data block DB004, DB006 or DB007. The output parameter"ERG" reports whether the function has been executed correctly. In theevent of an error message the data block DB000, DB006, DB007 orDB008 will contain the error cause.

Proceed as follows to use the standard function block:

• Enter the parameters in DB004, DB006 or DB007 (depending on the"FUNK" function).

• Call up SB254

• At the input parameter "FUNK", enter the number of the function.

• Allocate an operand to the output parameter "ERG", e.g. a flag word.

• Poll the content of the flag word. If it contains a code for an error mes-sage, call up data block DB000, DB006, DB007 or DB008 (depending onthe "FUNK" function). There you will find the reason for the error.

INFORMATIONSome of the functions of the SB254 are described in this System Descrip-tion (refer to the overview in the Appendix). There are also further functionsfor special applications (e.g. operation of the Interbus interface). These aredescribed in the corresponding manuals and operating manuals.


Communication with the periphery

The CPU can communicate in two ways with the periphery:

• direct periphery access

• periphery access via process images

Direct periphery access

• ... to input/output modulesThe process of reading the signal states of the inputs or setting the out-puts can be triggered with special operations in the user program.Access to the inputs/outputs is made immediately, irrespective of thecycle.The operands for a direct periphery access are called "Periphery wordPW" or "Periphery byte PB". "Load" or "Store" are available as opera-tions.

INFORMATION- In order for a status of an input which has been read directly to be

transferred to the process image, the "Save" operation of the inputbyte/word must be executed after the "Load" operation of the peripherybyte/word.Example:L PB2.08T EB2.08

- If direct access is made to an output (example: T PB2.08), then theprocess image is automatically updated.

• ... to word modulesST word modules can only be accessed with the aid of the direct periph-ery access. The operands are called "XW". "Load" or "Store" are avail-able as operations.

The direct access has the advantage that signals shorter than the scantime can also be processed. The user program can scan the inputs andoutputs several times during the program cycle and always receives thecurrent status.

Operation

6-2

Operation


Periphery access via process images

Communications usually take place via the process images.In the ST section there is a process image for bit modules.In the process image there is an area in which the states of the inputs aresaved and an area in which the states of the outputs are saved:

• PIIMemory area for the input states

• PIOMemory area for the output states

The input states are read in at the start of a program cycle and saved inthe process image for the PII inputs. Afterwards the user program is calledup and run with the values in the process image. The generated PIIprocess image is sent to the outputs after the user program is completed.

Access to the process images is via operations such as "Load" or "Trans-fer". The operands are called for example "E" and "AB".

The advantage of communicating with the periphery via process images isthat the states of the inputs and outputs remain unchanged during a pro-gram cycle. In addition, the access time to the process image is less thanthe time taken for direct periphery access.

INFORMATIONThere is no process image for ST word modules. ST word modules areonly accessed through direct periphery access.


Program cycle

Before the safety system starts with the cyclic processing of the FS andST user program, a reset block and a start-up block are executed once.The time required by the safety system to process the FS and ST userprogram once is referred to as the scan time.The FS and ST user programs are processed independently of each other,i.e. if for example the FS section is in the STOP condition, then only the STuser program is processed.

Fig. 6-1: Program cycle

Blocks which are executed once

RESET blockThe RESET block is run through once when the safety system is switchedon. During this time the CPU display shows "❚❚❚❚".In the reset block the safety system performs a self-test of the hardwareand software. After completion of the test the microprocessors areinitialised and synchronised. The safety system is then in the STOPcondition and the display shows "0000".Duration: approximately 30 s, on 3rd generation PSS: 10 s

STOP-RUN transitionDepending on the setting of the FS selector switch, the FS section willeither switch automatically to RUN, or it will wait to do this until the FSselector switch is operated. The same is true for the ST section.

Start-up blockAs soon as the FS section changes to RUN, the start-up block is executedfor it. The same is true for the ST section.

��)�

� �# � �� !�#*"

!��

��

� �+��)�� !�+��)�� !�#

!"#�� !

,��

!"#��-��

# ��

6-4

Operation


The start-up blocks for the FS section and the ST section can be executedat the same time. If either section is still in the STOP condition, then onlythe start-up for the other section is executed. The start-up of the othersection is integrated into the cycle later on.

FS start-up: The system checks the FS user program and the structure ofthe internal administration tables. Afterwards the configuration test iscarried out, the modules are tested and the start-up OB is called up.

ST start-up: The system checks the ST user program and the structure ofthe internal administration tables. Afterwards the configuration test isperformed (only if the option "Configuration test" is selected in the PSSconfigurator of the system software), the modules are tested and the start-up OB or the general reset OB is called up. If the “Operate PSS withoutbattery” option has been selected when programming the PSS in thesystem software’s PSS Configurator, a general reset will be performed oneach start-up.

Combined duration of FS and ST start-up: approx. 2 s

Blocks which are executed cyclically

FS-PII (read block for PII and XW-PII of the FS section)The process of reading in the process image for the inputs and processimage for the read segments of the FS section is described in detail in theFS system description.Duration: a few ms, on 3rd generation PSS: 0.2 ms

FS block run time (execution of the FS user program)The FS user program is started after successful alignment of the read invalues. For safety reasons all of the microprocessors process the userprogram of the FS section. At the end of the program anothersynchronisation of the microprocessors takes place.The duration of the FS user program varies as it usually comprises variousprogram parts, and a different number of these program parts is runthrough in any given cycle.Duration: max. 100 ms for FS and ST user program together, depends onthe program


ST-PII (read block for the PII of the ST section)The process image for the inputs of the ST section is read in.Duration: a few ms, on 3rd generation PSS: 0.1 ms

ST block run time (execution of the ST user program)The ST user program is executed. The program of the ST section is onlyprocessed by one microprocessor.The duration of the ST user program varies as it usually comprises variousprogram parts, and a different number of these program parts is runthrough in any given cycle.Duration: max. 100 ms for FS and ST user program together, depends onthe program

FS and ST-PIO (output block for PIO and XW-PIO of the FS sectionand PIO of the ST section)The process images for the outputs created during execution of the FS andST user programs are output.The process of outputting of the process image for the outputs and theprocess image for the output segments of the FS section is described indetail in the FS system description.Duration: 0.3 ms

Test slicesA test block is processed at the end of a cycle. All of the tests on thesystem are divided into slices with a duration of 1 ms. The operatingsystem automatically performs one test slice in each test block.The number of test slices can be influenced by the user via an operatingsystem call in the FS section.

Waiting period for minimum scan time (optional)A waiting period can be inserted in order to keep the scan time constant,i.e. to ensure a minimum scan time. During this waiting period theoperating system will run test slices.The length of the waiting period results from the selected minimum scantime. The minimum scan time is defined in the PSS configurator of the

6-6

Operation


system software (PG). It is comprised of:

FS block run time+ ST block run time+ Operating system run time for ‘Read PII’, ‘Output PIO’

and a test slice+ Time for additional test slices+ Waiting period_______________________________________________ = Minimum scan time

The minimum scan time must be less than or equal to 100 ms.

Scan time and the block run times

The minimum scan time and the FS and ST block run times are pre-assigned in the FS section (see FS system description).

If no FS user program is loaded into the safety system, then the maximumscan time is automatically 100 ms. It is not possible to pre-assign aminimum scan time.

If a value of 0 is entered for the ST block run time in the FS section, thenthe ST section is not called up.

If the ST block run time is exceeded, then the ST section changes to theSTOP condition.FS alarms can interrupt the ST user program. The processing time for thealarms is part of the FS block run time.In the event of an error in the alarm processing, the ST section isinterrupted and not continued until the next cycle, i.e. in this cycle there isno output of the process image for the outputs, and in the next cycle thereis no reading in of the process image for the inputs in the ST section.


Self-test

The self-test is performed in the FS section, see FS system description.

Registered hardware

The controller automatically detects all bit modules. However, it needs tobe told which slots are occupied by word modules. As word modules arefreely addressable, the start address also needs to be entered for eachword module.

Start adresses of word modules

The start address for the word modules can be entered in the PSSconfigurator of the PSS WIN-PRO system software (see PSS WIN-PROOnline Help). The PSS configurator then enters the start addresses at thecorrect points in the DB005.The start addresses can also be entered in the DB005 in the OB020 (start-up OB, see PSS WIN-PRO programming manual) or OB022 (general resetOB, see PSS WIN-PRO programming manual).

Assignment of the DB005:

Data word

DW000

DW001

.

.

.

DW008

DW009

DW010

.

.

.

DW023

Start address for module on

Slot 0

Slot 1

.

.

. .

Slot 8 (base or expansion module rack)

Slot 9 (expansion module rack)


.

.

.


6-8

Operation


The start addresses must be entered in the format "F" (16-bit fixed pointnumber).

Start address requirements:

• The start address is the address through which the first input or output on amodule is addressed. The second input or output contains the address =start address + 1 etc.

• The start address must be an integer multiple of the number of addressesthat the module requires.

Example: Module with 8 addressesPermitted start addresses: 0, 8, 16, 24, 32, .... (decimal)

• Permitted address range: 0 ... 16383 (decimal)

• The modules’ address ranges are not permitted to overlap

Example:Addressing the PSS AIO module on a PSS 3000

The module occupies 8 addresses. The start address must therefore bedivisible by 8. 4096 (decimal) would be possible, for example.Analogue inputs are addressed with an offset of 0 ... 5 and analogueoutputs are addressed with an offset of 6 and 7.

Start address: 4096 decimal

Module addresses:XW4096 1st InputXW4097 2nd InputXW4098 3rd InputXW4099 4rd InputXW4100 5rd InputXW4101 6rd Input

XW4102 1st OutputXW4103 2nd Output


Offset for free addressing

To be able to perform the programming mostly independent of the startaddress, the operating system call up SB254, FUNK = 180 has beenintroduced since the FS operating system version 38. This operatingsystem call up specifies the start address as offset. Then the addressing isperformed as if the start address was 0. The offset is valid until a differentblock is called, or until the end of the block.

Block

SB254

DB004

Entry

FUNK = 180

DW200

Output

ERG = 1

ERG = 16

Key



Error calling up SB254,FUNK = 180 (start address trans-ferred in DW200 was greater than16383)

Start address of the word module

For information on the application of SB254 please refer to the section“Standard function block SB254” in chapter "Programming".

6-10

Operation


Actual configuration

The controller automatically detects the actual configuration, i.e. which STmodules are occupying which slots on the module rack. The results arekept in DB000.The slots are numbered from 0 ... 8 on the base module rack. If one or twoexpansion module racks is/are connected, then the numbering is 0 ... 7 onthe base module rack, 8 ... 15 on the first expansion module rack and16 ... 23 on the second expansion module rack.

A code is assigned to each module (refer to the description of the module).This code is located in the data words DW020 ... 043 of DB000:

The code is displayed in hexadecimal format.

INFORMATIONThe actual configuration only shows the ST modules, not the FS modules.

Data word

DW0020

DW0021

.

.

.

DW0043

Assignment

Actual configuration: Code for module on slot 0


.

.

. .



Hardware registry test

During the hardware registry test, the actual hardware is compared withthe registered hardware. The registered hardware must be specified inDB004, DW0020 ... 0043.If a configuration error is found, then "S-05" is shown on the CPU display,error OB OB023 is processed and then the ST section changes to a STOPcondition. If OB023 is not available, the ST section will immediately switchto a STOP condition.

The hardware registry test in the ST section is an option. It can beexecuted during the ST start-up (STOP - RUN transition) and/or cyclically.

You can configure whether and when the hardware registry test should beperformed in the PSS configurator of the PSS WIN-PRO system software(see PSS WIN-PRO Online Help), or you can enter this information inDB004.

Assignment of the DB004:

Data word

DW0018

DW0019

DW0020

DW0021

.

.

.

DW0043

Assignment

Cyclic configuration test0 = switched on1 = switched off (default setting)

Configuration test during start-up0 = switched on (default setting)1 = switched off

Registered hardware: Code for module on slot 0


.

.

. .


The information must be given in hexadecimal format.

6-12

Operation


Block

SB254

DB004

Input

FUNK = 32

DW200 = 0000H

...FFFF

H

Output

ERG = 1

Key

Output on the CPU display


0000H ... FFFE

H: Hexadecimal

number which is to be output on theCPU displayFFFF

H: Clear CPU display, it is not

possible to clear FS error messages

Output on the CPU display

Hexadecimal numbers can be output on the display of the CPU. Theoperating system call SB254, FUNK = 32 is used to do this.

INFORMATIONError messages from the system are displayed as the top priority.

The number currently displayed on the CPU display is saved in data blocksDB000, DW0015. The message type is encoded in DW0014.


Block

SB254

DB004

Input

FUNK = 12

DW200DW201, DLDW201, DRDW202, DLDW202, DRDW203, DLDW203, DR

Output

ERG = 1ERG = 16

Key

Set System Time

Function performed without errorValue in one of the data wordsDB004, DW200 ... DW203 wasinvalid, the system time remainsunchanged

0 ... 99: Year1 ... 12: Month1 ... 31: Day0 ... 23: Hour0 ... 59: Minute0 ... 59: Second0

Adjusting the system time of the safety system

The real-time clock of the safety system can be adjusted using the PSSWIN-PRO system software (see Online Help) or via the operating systemcall SB254, FUNK = 12.The real-time clock is reset every time SB254, FUNK=12 is called up, andthe current time is copied to the data block DB000, DW000 ... DW003.

6-14

Operation


Block

SB254

DB004

Input

FUNK = 36

DW200

Output

ERG = 1

Key

Select FS data block


1 ... 255: Data block number

Select FS data block

A data block needs to be selected before its data words can be accessed.The "Select data block" operation is available in all programminglanguages for selecting the ST data blocks. Operating system call SB254,FUNK = 36 is used to select FS data blocks.After selecting an FS data block, the ST section has read access to thisDB. If the FS data block which is to be selected does not exist, then the STsection switches to a STOP condition.

INFORMATIONFS data blocks can only be selected if the FS section is in RUN mode. Thiscan be checked with the aid of the FS status flags (see section"Communication with the ST section").


Communication with the FS section

Various flags are available for communication between the FS section andthe ST section:

• Communication flagsM100.00 ... 104.31M105.00 ... 109.31 (only on PSS with operating system ≥ 43)The communication flags can be written to and read by the ST userprogram. The FS section only has read-access to these flags. The flagsare available to the user for free use.

• Fixed flags

The fixed flags have a fixed status. They are often used to set the RLOto "1" or "0". To do this, the corresponding flag is loaded with the "Load"operation.The FS section and the ST section only have read access.

• Arithmetic flags

Arithmetic flags are used by the operating system during arithmeticoperations. The FS section and the ST section only have read access.

Flag

M111.00

M111.01

M111.02

M111.03

Description

Carry= 1 if the carry flag has been set by an arithmetic operation

Overflow= 1 if the overflow flag has been set by an arithmetic operation

Zero= 1 if the zero flag has been set by an arithmetic operation

Sign= 1 if the sign flag has been set by an arithmetic operation

Flag

M110.00

M110.01

Description

FALSE (RLO-0)Flag content is always = 0

TRUE (RLO-1)Flag content is always = 1

6-16

Operation


• FS status flags

Flag

M113.00

M113.01

M113.02

M113.03

M113.04

M113.05

M113.06

M113.08

Description

= 0 if status of FS section is STOP= 1 if status of FS section is RUN, only set after the first cycle

= 0 if status of FS section is "No error"= 1 if status of FS section is "Error"

= 1 if FS section has been stopped by a STOP operation

= 1 after start-up (STOP > RUN) of the FS section, onlyactive for one cycle

= 1 after restart (OFF > RUN) of the FS section, only active forone cycle

= 1, if SafetyBUS p 0 is in a RUN condition

= 1, if SafetyBUS p 1 is in a RUN condition

= 1 if the remanent DBs in the FS section have been reset;flag must be reset through SB255, FUNK = 50. Provided theflag is set, the remanent DBs will be reset each time the PSSis cold/warm started. The flag is non-volatile.

FS status flags provide information about the status of the FS section.The FS section and the ST section only have read access.


• ST status flags

ST status flags provide information about the status of the ST section.The FS section and the ST section only have read access.

INFORMATIONThe FS section cannot access the operands of the ST section. Communi-cation is only possible via the above flags.The ST section can obtain read access to the process images of the inputsand outputs (PII and PIO, but not XW-PII and XW-PIO), the flags, the datablocks, the timers and counters of the FS section.

Flag

M112.00

M112.01

M112.02

M112.03

M112.04

M112.05

Description

= 0 if status of ST section is STOP= 1 if status of ST section is RUN, only set after the first cycle

= 0 if status of ST section is "No error"= 1 if status of ST section is "Error"

= 1 if ST section has been stopped by a STOP operation

= 1 after start-up (STOP > RUN) of the ST section, onlyactive for one cycle

= 1 after restart (OFF > RUN) of the ST section, only active forone cycle

= 1 if a general reset was performed in the ST section, onlyactive for one cycle

6-18

Operation


User interface in the ST section

The user interface (refer also to the chapter "Structure", section "Userinterface") can be used either in the FS section or in the ST section forcommunication with other devices. The section which accesses the userinterface first obtains the access rights. If the user interface has alreadybeen configured for the FS section, then it cannot be used by the ST sec-tion again until a general reset is performed in the ST section and thepower supply to the PSS is switched off and back on again.

Networks can be formed with a maximum of 32 subscribers with the aid ofthe user interface, see section "Forming networks". The transfer can takeplace without a protocol or with an ISI protocol, see section "Communica-tion protocol". "Handshaking" can be used during the transfer - see section"Handshaking".

Access from the ST section to the user interface is provided with the aid ofthe following functions of the SB254:

FUNK

000

001

002

004

005

006

008

010

011

Description

Status poll for the configuration

Configure

Acknowledge configuration error

Status poll for sending

Send

Acknowledge send error

Status poll for receiving

Acknowledge receive error

Acknowledge receipt


Forming networks

Using the ISI protocol (see section "Communication protocol"), it is possi-ble to form a network with a maximum of 32 subscribers (one Master and31 Slaves) and a maximum cable run of 1,200 m.

3rd generation controller networks:

All 3rd generation controllers have a terminating resistor which can beactivated via the terminating switch RT (USER). The terminating resistor isactivated when the switch is pressed.

In a network the terminating resistor must be activated at the Master andat the end device. The terminating resistor must be deactivated on all otherdevices.

Fig. 6-2: 3rd generation controller networks

��

��

��

��

��

6-20

Operation


1st and 2nd generation controller networks

In order to form a network using 1st and 2nd generation controllers, you willneed to use a PAP interface adapter (RS 232 -> RS 485).

��

��

��

��

��

��

��

Fig. 6-3: 1st and 2nd generation controller network

Handshaking

The interface has the following handshake signals:

• RTS

• CTS

• DTR

• DSR

During data transfers without handshaking the input signals DSR andCTS are not taken into account. The output signals DTR and RTS areused.

During data transfers with handshaking the output signals DTR and RTSare used to control the partner, and the input signals CTS and DTS areused for synchronisation with the partner. The signals have the followingmeaning:

• DTR output signalThe output signal signals to the partner when the user interface is readyto receive data:- DTR = 1: User interface ready to receive- DTR = 0: User interface not ready to receive, either because the

receive buffer is full or because the received data are being processed(see Assignment of the interface configuration-DB DB006, DW012).


• RTS output signalThe output signal reports when the user interface is ready to send:- RTS = 0: Rest condition- RTS = 1: RTS is reset to 0 immediately before the start of each send

cycle, during sending and after completion of sending.The output signal generally switches interface adapters to send mode.

• DSR input signal:The input signal reports when the partner is ready to receive data. Thesafety system interrogates the status of this input before a send cyclestarts:- DSR = 1: start send process- DSR = 0: Partner not ready to receive, delay send process until

DSR = 1.

• CTS input signal:This input signal is generally used by an interface converter to signalwhether it has switched to send mode. The safety system interrogatesthe status of this input before a send cycle starts:- CTS = 1: Start send process- CTS = 0: Partner not ready to receive, delay send process until

CTS = 1.

Communication protocol

Data transfer without protocol

During a transfer without protocol, the data which are to be sent are outputwithout change from the send buffer via the interface.The received data are written block by block without change to the receivebuffer. Expiry of the receive timeout time signals the end of a block.The receive timeout time is an aid which can be used to detect the end ofa data block during a data transfer without protocol. A timer is started whena character is received. Each further character which is received re-triggers this timer. The interface interprets it as the end of a data block Ifthe timer expires, and writes the received data to the receive buffer. Thetimeout time is configurable (see Assignment of the interface configuration-DB DB006, DW010). Output signal DTR is set to 0 when the data blockend is detected.

6-22

Operation


Transfer with ISI protocol

During a transfer with ISI protocol, the data in the send buffer are given aprotocol framework:

LF (0A hex.)

Slave address ID

Data length low

Data length high

First data (DR)...last data (DL)

CRC

CR (0D hex.)

Start of telegram

Slave address: 1 ... 31, ID field: 0 ...3

No. of data bytes, Low Byte

No. of data bytes, High Byte

max 2,042 bytes.

Checksum

End of telegram

Telegramheader

Data

End oftelegram

Fig. 6-4: ISI protocol

A received protocol is checked for protocol errors. Error-free telegrams arewritten to the receive buffer once the protocol framework has been re-moved.The ISI protocol operates in accordance with the Master-Slave principle.Only one of the subscribers must be defined as the master. After everysend command from the Master the addressed slave must answer withinthe defined timeout time (see Assignment of the interface configuration-DBDB006, DW009). A slave will only send data on request.

Calculation of the checksum CRC:CRC = 0 - (ID byte of the Slave address

+ Data length low+ Data length high+ Sum of all data bytes)

The first databyte is located in DR003.


Please note the following when sending data with the ISI protocol:

• The value "3" must be entered in data block DB006, data word DW005(8 data bits, see section "Configuration of the user interface").

• If the safety system is a Slave:- If a telegram cannot be sent because the Master is not ready to receive

then the Master will request the answer again (no send error).- Data word DW003 from data block DB007 is the first send data,

DW002 is reserved for the Slave address (see section "Sending via theuser interface").

- Only change the send buffer (DB007) after a telegram has been re-ceived from the Master. If the Master requests the last telegram againbecause errors were encountered during receipt, then thesafety system automatically repeats the telegram which is in the sendbuffer.

• If the safety system is a Master:- The Slave address must be entered in data word DW002 of data block

DB007, data word DW003 contains the first send data (see section"Sending via the user interface").

- The send process is not complete until the addressed Slave has an-swered and the receipt of the answer or a send error has been ac-knowledged. If the answer from the Slave has not been acknowledged,then the status poll SB254, FUNK = 4 returns ERG = 2 as a result (seesection "Sending via the user interface"). A receive status poll needs tobe performed in order to establish whether or not the Slave isresponding.

- If the slave does not answer without errors within the timeout time, thenthe safety system repeats the telegram 3 times. If the Slave still doesnot answer without errors, then the safety system reports a receiveerror.

ID handling

• If the safety system is the Master:After the interface has been configured the telegram is sent with ID = 0.After an error-free answer from the slave the ID byte for this slave isincreased by 1. If ID = 3 and the answer to a telegram is error-free, thenthe ID byte for this Slave is reset to 1.

6-24

Operation


If a Slave does not answer without errors, then the safety system repeatsthe telegram 3 times with the same ID byte. If there is also no responseto the repetition, then the ID byte for this Slave is set to 0. ID = 0 for thenext telegram sent to this slave.

• If the safety system is a slave:An addressed slave always answers with the received ID byte. If the IDbyte remains the same between two received telegrams, then this is arepetition request for the last sent telegram. The safety system automati-cally responds to the repetition request. If ID-Byte = 0, then the Slave isrequested to perform an initialisation.


Configuration of the user interface

The user interface is configured with default values at every STOP-RUNtransition of the ST section, i.e. the interface configuration-DB (DB006) isinitialised with the default values. In order to configure the interface withuser-specific values, it needs to be reconfigured at every STOP-RUNtransition, e.g. during the start-up OB or the general reset OB.The receive DB (DB008) and the send DB (DB007) are deleted duringconfiguration.

The configuration can be performed with the aid of the following threeoperating system calls.

Block

SB254

Input

FUNK = 000

Output

ERG = 1

ERG = 2

ERG = 16

ERG = 32

Key

Configuration status poll

Interface ready for operation

Interface currently being configured

Configuration error

Acknowledgement is processed

Block

SB254

Input

FUNK = 001

Output

ERG = 1

ERG = 2

ERG = 16

ERG = 32

Key

Configure



Configuration error


Block

SB254

Input

FUNK = 002

Output

ERG = 1

ERG = 2

ERG = 16

ERG = 32

Key

Acknowledge configuration error



Configuration error


6-26

Operation


Interface configuration DB (DB006)

The interface data are entered in the interface configuration-DB.

PropertiesLength: at least 13 data wordsAccess right: Read/Write

Assignment

DW000 Reserved

DW001 Fault detected if SB254, FUNK = 000, 001 or 002 reports aconfiguration error (ERG = 16).0002

H ... 000C

H: Number of the faulty data word in the DB006

FFF0H: Interface is assigned to the FS section

DW001 can only be read.

DW002 Transmission rate

* only on 3rd generation PSS

DW003 Parity bit

Value

0

1

2

3

4

5

6

7

8*

Transmission rate in bit/s

150

300

600

1,200

2,400

4,800

9,600

19,200

38,400

Default value

Value

0

1

2

Parity bit

None

Odd

Even Default value


DW004 Number of stop bits

DW005 Number of data bits

DW006 Handshake

DW007 ISI protocol

DW008 CPU as Master or Slave (with ISI protocol only)

DW009 Timeout for Slave response (for ISI protocol only)

Value

0

1

Handshake

No

Yes Default value

Value

0

1

2

3

Number of data bits

5

6

7

8 Default value

Value

0

1

2

Stop bits

1

1.5

2

Default value

Value

0

1

ISI protocol

No

Yes

Default value

Value

0

1 ... 31

CPU as Master or Slave

Master

Slave, with correspondingaddress

Default value

Value

0

1 ...65535

Timeout

none

Timeout in ms

Default value

6-28

Operation


DW010 Receive timeout

DW011 Send timeout (only for transferwith handshaking)

DW012 DTR controllerThe receive-DB has enough space for 2,044 bytes. In order toprevent bytes from being lost, it is possible to stop the sendprocess before the receive-DB is full. The DTR control line is setto 0 to do this. DW012 contains the information how many bytesbefore 2,044 the send process is to be stopped.Value range: 0 ... 2,044, default value: 3

Example: DW012 = 5, i.e. after 2,039 Bytes DTR = 0 is set, as aresult of which the partner is requested to terminate the sendprocess.

Value

15

1 ...65,535

Timeout

15 ms

Timeout in ms

Default value

Value

0

5,000

1 ...65,535

Timeout

infinite

5,000 ms

Timeout in ms

Default value


Example

Call up SB255, FUNK = 000 and evaluate ERG. The configuration mustonly be performed if ERG = 1 or ERG = 16.

ERG = 1

or

ERG = 16 The interface can be configured.

Assign the desired values to DB006 (interface configuration-DB).

Call up SB254, FUNK = 001 and evaluate ERG:ERG = 2 while the configuration is running.If ERG = 1 then the configuration was successful.If ERG = 16 then an error has occurred during configuration.DW001 of DB006 contains the fault identifier. The error must berectified and acknowledged with SB254, FUNK = 002,or a new configuration command (SB254, FUNK = 001) needsto be issued. ERG = 32 during the processing of the acknowl-edgement. Once the processing has finished, ERG = 1.

ERG = 2 Interface is currently being configured.

ERG = 32 Acknowledgement is processed.

6-30

Operation


Sending via the user interface

The process of sending data via the user interface takes place with the aidof the following operating system calls.

Block

SB254

Input

FUNK = 004

Output

ERG = 1

ERG = 2

ERG = 16

ERG = 32

Key

Send status poll


Data are being sent

Send errors


Block

SB254

Input

FUNK = 005

Output

ERG = 1

ERG = 2

ERG = 16

ERG = 32

Key

Send


Data are being sent

Send errors


Block

SB254

Input

FUNK = 006

Output

ERG = 1

ERG = 2

ERG = 16

ERG = 32

Key

Acknowledge send error


Data are being sent

Send errors



Send-DB

The data which are to be sent are entered in the send-DB (DB007).


Assignment

DW000 Number of bytes to be sent

DW001 Fault detected if SB254, FUNK = 004, 005 or 006 reports asend error (ERG = 16).0: Timeout exceeded on send (partner not ready to re-

ceive)16: Number of bytes to be sent is too high17: Send command currently not available, e.g. because a

telegram is just being sent.18: Interface not yet configuredFFF0

H: Interface is assigned to the FS section

FFFFH: No error

DW002 with ISI protocol: Slave address if the safety system is theMasterwithout ISI protocol: first send data word

DW003 ... 1023 Send dataSend sequence without ISI protocol:DR2 (2nd right data word), DL2 (2nd left data word), DR3,DL3, ....Send sequence with ISI protocol:DR3, DL3, DR4, DL4, ...

6-32

Operation


Example

SB255, call up FUNK = 004 and evaluate ERG. It is only permissible tosave new send data in the send-DB (DB007) if ERG = 1 or ERG = 16.

ERG = 1

or

ERG = 16 Data can be sent.

Assign values to DB007 (send-DB).

Call up SB254, FUNK = 005 and evaluate the ERG:During sending, ERG = 2.If ERG = 1, then the data have been sent successfully.If ERG = 16, then an error has occurred during sending. DW001of DB007 contains the fault identifier. The error must be rectifiedand acknowledged with SB254, FUNK = 006, or a new sendcommand (SB254, FUNK = 005) needs to be executed.ERG = 32 during the processing of the acknowledgement. Oncethe processing has finished, ERG = 1.

ERG = 2 Data are being sent

ERG = 32 Acknowledgement is processed


Receive via the user interface

The process of receiving data via the user interface takes place with theaid of the following operating system calls.

Block

SB254

Input

FUNK = 008

Output

ERG = 1

ERG = 2

ERG = 4

ERG = 8

ERG = 16

ERG = 32

Key

Receive status poll

No data received

Data are being received

Receive telegram is complete

Receipt acknowledgem.being processed

Receive errors


Block

SB254

Input

FUNK = 010

Output

ERG = 1

ERG = 2

ERG = 4

ERG = 8

ERG = 16

ERG = 32

Key

Acknowledge receive error

No data received




Receive errors


Block

SB254

Input

FUNK = 011

Output

ERG = 1

ERG = 2

ERG = 4

ERG = 8

ERG = 16

ERG = 32

Key

Acknowledge receipt

No data received




Receive errors


6-34

Operation


Receive-DB

The received data are entered in the receive-DB (DB008).


Assignment

DW000 Number of bytes receivedDW001 Error detected if SB254, FUNK = 008, 010 or 011 re-

ports a receive error (ERG = 16).0: Send timeout exceeded (for ISI protocol only)1: Parity error2: Receive "Break"3: Stop bit error8: Overflow error; characters have been lost, e.g. because

the last telegram received was not acknowledgedquickly enough.

9: Number of the receive-DB10: Slave not answering in time (for ISI protocol only)11: Number of received bytes incorrect (for ISI protocol

only)12: CRC error (for ISI protocol only)13: ID error (for ISI protocol only)14: Incorrect Slave answering (for ISI protocol only)15: End identifier missing or end of telegram contains too

few characters (for ISI protocol only)17: Command not permitted at this time18: Interface not yet configured19: Telegram header contains too few characters (for ISI

protocol only)FFF0H: Interface is assigned to the FS sectionFFFFH: No error

DW002 with ISI protocol: not relevantwithout ISI protocol: first received data word

DW003...1023 Receive dataSend sequence without ISI protocol:DR2 (2nd right data word), DL2 (2nd left data word), DR3,


DL3, ....Receive sequence with ISI protocol:DR3, DL3, DR4, DL4, ...

Example

Call SB255, FUNK = 008 and evaluate ERG.

ERG = 1 The interface is not receiving any data.

ERG = 2 Data are currently being received. The data are saved in thereceive-DB (DB008).

ERG = 4 All data have been received in full. A telegram is complete if nomore characters are received within the receive timeout. This isdetected during the next cycle change or during the next statuspoll.Now the received data can be processed in the receive-DB(DB008).The data need to be read out from the receive-DB, and theirreceipt needs to be acknowledged with SB254, FUNK = 011.During processing or receipt acknowledgement ERG = 8; aftererror-free acknowledgement ERG = 1.

If an error occurs while receiving, then ERG = 16. DW001 of DB008 con-tains the error identifier. The error must be rectified and acknowledged withSB254, FUNK = 10 or FUNK = 11. ERG = 32 during the processing of theacknowledgement. Once the processing has finished, ERG = 1.A regular status poll needs to be performed with SB254, FUNK = 8 toenable the user program to detect whether data have been received viathe interface.

If the safety system is the Master, then any exceeding of the send timeoutis reported as a receive error. The receive status must be polled whilewaiting for the answer from the slave. The next telegram cannot be sentuntil the receipt or receive error has been acknowledged.If the safety system is a Slave, then faulty telegrams or telegrams whichare not addressed to the selected Slave address are discarded by theoperating system without warning. Repetition requests (ID byte isunchanged) are automatically answered by the safety system.

6-36

Operation


Operating states and changes

$�%��

# �$�%��

�

��

�

�� !"�#�$��%&''�

�� $��(� ��!"�#�$��)'''��*'''�

+

�� ,��-"�. ��!"�#�$��&��

/"��

��

��0�1 ��

�1

��0��#��"��$��/��,�2��

��

��0�1 ��

�1��

��0�1 ��

�1

��$��/��,�2��

�� 03

,��"��%�#��

��

$��

��,, ��!"�#�$��4��&''��%&''�

5

,��"��#��

Fig. 6-5: Operating states of ST section


This section describes the operating states that can be assumed by the STsection of the safety system, which changes in status can take place, whathappens while the status change is happening and what you can do totrigger a status change.

The numbers identify status changes which are described on the nextpages.

Operating statuses

Status "ST-STOP"

• The ST user program is not processed and all ST outputs are switchedoff (safe condition).

• Processing of the FS user program continues unchanged.

• All of the functions of the system software (PG) are available.

• "ST RUN" LED: Off

• CPU display: Error class of the error "S-xx" (if any FS errors are alsoentered in the error stack, then these are displayed as the top priority "F-xx")

Status "ST-RUN"

• The ST user program is processed.


• All of the functions of the system software (PG) are available(Exceptions: transfer or delete program).

• "ST RUN" LED: On

• CPU display: "0000" or "F-xx"

Status "ST Fatal Error"

• The ST section is out of service, all outputs are switched off.


• No communication with the programming device is possible.

• "ST RUN" LED: flashing

• CPU display: Error identifier "S-80" (if any FS errors are also entered inthe error stack, then these are displayed as the top priority "F-xx")

6-38

Operation


Status "Fatal Error"

• FS and ST section are inoperative, all outputs are switched off (safecondition).


• "ST RUN" LED: any status

• CPU display: Fault detection "*xxx" or "+xxx"

Change in operating status

Switch on voltage ➀The following happens after the voltage is switched on:

• All of the outputs of the ST modules are switched off.

• The system time (real-time clock) is read out and the current time isentered in DB000. Exception: If the “Operate PSS without battery” optionhas been selected when programming the PSS in the system software’sPSS Configurator, the system time is set to zero.

• ST status flag M112.04 = 1 (this only remains set for one cycle), all otherST status flags are set to 0.

• The system checks whether the contents of the read/write data memorywere changed while the safety system was switched off (memory is"corrupted"); if "yes" then a general reset is performed (see chapter"Commissioning").If the “Operate PSS without battery” option has been selected whenprogramming the PSS in the system software’s PSS Configurator, ageneral reset will be performed in each case.

• The communication flags are set to 0.

• The PIO and the PII of the FS section are assigned the value 0.

• The dynamic program display is switched off.

• The variable display is shut down.

• The ST section switches to a STOP condition.


Status change from ST-STOP to ST-RUN (start-up) ➁This change takes place automatically after switching on if the ST selectorswitch is in the position "PLC" or "AUTO PG".

If the ST section is in STOP mode and no ST error is present, then youcan proceed as follows to return to RUN mode:

• Set the ST selector switch from "PG" to "PLC" or "AUTO PG", or

• start the ST section with the aid of the system software.

If the ST section is in STOP mode due to an error which has occurred (ifno FS error "F-xx" is present, then the CPU display shows: "S-xx") thenyou will need to proceed as follows to return to the RUN condition:

• Read out the error stack (see chapter "Fault diagnostics and correction",section "Error stack").

• If necessary use the dynamic program display (system software) tosearch for the error.

• Rectify the error.

• Start the ST section (move the ST selector switch from the "PG" settingto the "PLC" or "AUTO PG" setting, or start the ST section with the aid ofthe system software).

The following happens during the changeover of the ST section fromSTOP to RUN:

• If expansion modules are being used, the system checks whether thevoltage supply to the expansion modules is still intact. If after a time of 3s has elapsed, no supply voltage is present then the ST section remainsin STOP mode.

• The ST user program is checked.

• ST timers are stopped and reset to 0.

• ST counters are reset to 0.

• The PIO and the PII of the ST section are assigned the value 0.

• The user interface is initialised using the default values.

• The actual configuration is entered in DB000.

• Status flags- M112.00 = 1 (only set after the first cycle)- M112.01 = 0- M112.02 = 0- M112.03 = 1 (only remains set for one cycle)

6-40

Operation


• A general reset is triggered and M112.05 = 1 is set (M112.05 only re-mains set for one cycle) if one of the following conditions is met:- OB022 is present in the user program.- With the error stack button pressed, the ST selector switch was moved

from the "PG" setting to "PLC" or "AUTO PG".- The contents of the read/write data memory were changed while the

safety system was switched off (memory has become "corrupted").- if the “Operate PSS without battery” option has been selected when

programming the PSS in the system software’s PSS Configurator

• If present, the general reset-OB (OB022) or start-up-OB (OB020) isexecuted.

• The hardware registry test (if configured) is executed.

• Word modules are initialised.

• During the first STOP-RUN transition after the transfer of the ST programto the safety system: DBs of the ST section are initialised using thevalues specified in the system software (PG).

Status change from ST-RUN to ST-STOP ➂Reasons:

• The ST selector switch was set to "PG" or

• the STOP function was called up in the system software (PG), or

• the STOP operation was called up in the ST user program, or

• a minor error has occurred.Minor errors include:- Error in the user program- Battery error

The corresponding error organisation block is called up on errors belong-ing to error classes S-04, S-05, S-21, S-22, S-23, S-24 or S-26. If theerror organisation block is not present, then the ST section changes to aSTOP condition, otherwise the error organisation block is executed andthe ST section remains in RUN mode. (Refer to the PSS WIN-PROProgramming Manual for more information about "Error organisationblocks").

During this change of status the following happens:


• The ST user program is stopped.


• The PIO of the ST section is assigned the value 0.

• Status flag M112.00 = 0

• After a STOP on account of a STOP operation in the ST user program:Status flag M112.02 = 1

• After a STOP on account of a minor error:Status flag M112.01 = 1

• The STOP organisation block OB024 is called up.The OB024 is called up every time the system changes into the STOPcondition. OB024 is only available for PSS with an operating systemversion ≥ 43.(Refer to the PSS WIN-PRO programming manual for more informationabout "STOP organisation blocks").

• After a STOP on account of execution of the stop function in the systemsoftware or actuation of the FS selector switch:First the STOP organisation block OB128 is called up, followed by theSTOP organisation block OB024 (Refer to the PSS WIN-PRO program-ming manual for more information about "STOP organisation blocks").

Status change from ST-RUN or ST-STOP to "Fatal Error" ➃Reason: A fatal error has occurred in the FS section.Fatal errors can include:• Major system defect

• Error during self-test


• All the outputs are shut down.

• The FS and ST user programs are stopped.

Status change from "Fatal error" to ST-RUN ➄It is not possible for the user to rectify the error. If the PSS is in this state,then the only option is to:

• Note the conditions under which the error occurred.

• Write down the displayed fault detection.

• Switch the PSS off and back on again and then read out the error stack(see chapter "Fault diagnostics and rectification", section "Error stack").

• Contact Pilz.

6-42

Operation


Status change from ST-RUN or ST-STOP to "ST Fatal Error" ➅Reason: A fatal error has occurred in the ST section, i.e. there is a majordefect in the ST section.




• Status flags M112.00 = 0 and M112.01 = 1

Status change from "ST Fatal Error" to ST-RUN ➆Proceed as follows to return to the RUN condition:



• Switch the PSS off and back on again and then read out the error stack(see section "Error stack").

• Contact Pilz.

Safety System: ST System Description 7-1

Initial commissioning

Hardware requirements

• Supply voltage connected to PSS(modular PSS: see power supply operating manual; compact PSS: seePSS operating manual)

• Supply voltage for inputs and outputs connected(modular PSS: see I/O modules operating manual; compact PSS: seePSS operating manual)

• For modular PSS: Correct module rack configuration(first slot must be occupied by the power supply and the second by theCPU module)

Software requirements

• Configuration data (slot configuration, start addresses of the word mod-ules etc.) entered in the PSS configurator of the system software arecorrect.

• Executable user program is available in a linked form (see "Link" in theonline help of the system software).

Initial commissioning procedure

• Set the ST selector switch to the "PG" or "Auto PG" setting. Set the STselector switch to "AUTO PG" if you wish the ST section to start auto-matically after downloading the program. If you wish to start the STsection yourself, set the ST selector switch to "PG".

• Switch on the power supply (position "I")Reaction: "Power" LED on the power supply and the CPU module

light up.CPU carries out a self-test, CPU display shows: "❚❚❚❚"

• If the self-test is successful, the CPU display will show: "0000"

• Transfer program (see online help of the system software)

• If the ST selector switch is set to "AUTO PG", then the ST section willstart automatically. If the ST selector switch is set to "PG", set it to "PLC"or start the ST section with the aid of the system software.The program is executed. The "ST RUN" LED comes on.

If a configuration error is indicated, this may also have been caused by theregistered hardware entered in the PSS during the function test (at Pilz).

Commissioning

7-2

Commissioning

Safety System: ST System Description

The remedy in this case is to perform a general reset (set the ST selectorswitch to the "PG" setting, then press the "Error Stack" button and, at thesame time, set the ST selector switch back from "PG" to "PLC").

Error messages are described in chapter 8.

Recommissioning

If a hardware or software error occurs, there will be an error reaction fromthe safety system. The error will be shown on the CPU display (see Chap-ter 8 for details of error messages) and the "ST RUN" LED will either flashor go out. The following states are available:

• The "ST RUN" LED flashes and the CPU display shows "S-80" (if FSerrors are also entered in the error stack, then these are displayed as thetop priority "F-xx"): a fatal error has occurred in the ST section.

Recommissioning:- Note the conditions under which the error occurred.- Write down the displayed fault detection.- Switch the PSS off and back on again and then read out the error stack

(see section "Error stack").- Contact Pilz.

• The "ST RUN" LED goes out and the CPU display indicates an error("S-xx"; if any FS errors are also entered in the error stack, then theseare displayed as the top priority "F-xx"): a minor error has occurred.

Recommissioning:- Read out the error stack (see chapter "Fault diagnostics and correc-

tion", section "Error stack").- If necessary use the dynamic program display (system software) to

search for the error.- Rectify the error.- Start the ST section (move the ST selector switch from the "PG" setting

to the "PLC" or "AUTO PG" setting, or start the ST section with the aidof the system software).

• "RUN" LED any status, CPU display shows "+xxx" or "*xxx": a fatal errorhas occurred. The system is defective.The user will not be able to rectify the error. If the PSS is in this state,

Safety System: ST System Description 7-3

then the only option is to:- Note the conditions under which the error occurred.- Write down the displayed fault detection.- Switch the PSS off and back on again and then read out the error stack

(see chapter "Fault diagnostics and rectification", section "Error stack").- Contact Pilz.

Changing the configuration or the user program

Sequence:

• Enter the changes to the configuration, e.g. changed registered hard-ware, in the PSS configurator (see online help of the system software).

• If necessary change the user program (see online help of the systemsoftware)

• Re-link the program (see online help of the system software).

• Proceed as for the initial commissioning procedure

General reset

The ST section is reset during a general reset.

A general reset can be triggered both manually and automatically:

• Manual: with the error stack button pressed, move the ST selector switchfrom the "PG" setting to "PLC" or "AUTO PG".

• Automatic: if the OB022 is present in the user program during the STOP-RUN transition of the ST section.OB022 may contain user-specific initialisation settings which are exe-cuted in addition to the general reset initialisation.

• Automatic: if the content of the read/write data memory was changedwhile the safety system was switched off (memory is "corrupted").

• Automatic: if the “Operate PSS without battery” option has been selectedwhen programming the PSS in the system software’s PSS Configurator.

7-4

Commissioning

Safety System: ST System Description

The CPU carries out the following steps during a general reset:

• A message that a "general reset" is to be performed is entered in theerror stack (S-20, error number 14).

• All of the flags of the ST section are set to 0.

• ST timers are stopped and set to 0.

• ST counters are set to 0.

• General reset flag M112.05 = 1.

• The PIO and the PII of the ST section are assigned the value 0.


• The system time (real-time clock) is set to 00:00 (not on 3rd generationcontrollers)

• The current ST block run time and the maximum ST block run time inDB000 are set to 0.

• The actual configuration is entered in DB000 and DB004.

• The cyclic configuration test is switched off.

• The configuration test during start-up is switched on.

• Parameters for operating system calls (SB254) in DB004 are assignedthe value 0.

• The dynamic program display and the variable display are switched off.The tables are assigned the value 0.

• If a valid ST user program is present in the safety system, then the read/write data blocks are assigned the same values again that were enteredin the read/write data blocks during programming (see chapter "Structure(hardware)", section "Data memory").


Error management

The safety system continuously checks the hardware and software duringthe program cycle. If an error is discovered, the following sequence istriggered:

• The fault detection is displayed on the CPU display.

• The error is entered in the error stack.

• Execution of the error reaction.

The reaction of the safety system to an error depends on the severity ofthe error.

Fault diagnostics and rectification

Fig. 8-1: Change in operating status on account of an error

�"��

�� $�!"�#�$ ��!"�#�$��)'''��*'''�

�� ,��-"�. ��!"�#�$��&��

��03

��

$��

��,, ��!"�#�$��4��&''��%&''�

�� !"�#�$��%&''�

%��"��%��6�"��

%��"��6�"��

8-2



Minor errors

Possible causes

• Error in the user program

• Battery error

PSS reactionAn error OB is called up for some minor errors (see Programming Manualfor PSS WIN-PRO). A reaction to the error can be programmed in this errorOB. If an error OB is present, it is processed, and the ST section remainsin RUN mode. If no error OB is available, the ST section will switch to aSTOP condition.The following happens during the switch to the STOP condition:



• The PIO of the ST section is assigned the value 0.

• Status flags M112.00 = 0 and M112.01 = 1

The PSS operates as follows in the STOP condition:

• The ST user program is not processed and all ST outputs are switchedoff (safe condition).


• All of the functions of the system software (PG) are available.

• "ST RUN" LED: Off

• CPU display: Error class of the error "S-xx" (if any FS errors are alsoentered in the error stack, then these are displayed as the top priority "F-xx")

Remedy

• Read out the error stack (see section "Error stack").

• If necessary use the dynamic program display (system software) tosearch for the error.

• Rectify the error.

• Start the ST section (move the ST selector switch from the "PG" settingto the "PLC" or "AUTO PG" setting, or start the ST section with the aid ofthe system software).


Fatal errors in the ST section

Possible causes• Major defect in the ST section

ReactionThe ST section changes status to "ST Fatal Error". The following happensduring the switch to this status:



The PSS operates as follows in the "ST Fatal Error" condition:

• The ST section is inoperative, all outputs are switched off.



• "ST RUN" LED: flashing

• CPU display: Error identifier "S-80" (if any FS errors are also entered inthe error stack, then these are displayed as the top priority "F-xx")

RemedyIt is not possible for the user to rectify the error. If the ST section is in thisstate then the only option is to:




• Contact Pilz.

8-4



Fatal errors in the FS section

Possible causes• Major system defect

• Error during self-test

ReactionThe safety system changes to "Fatal Error". The following happens duringthe switch to this status:


• The FS and ST user programs are stopped.

The PSS operates as follows in the "Fatal Error" condition:

• FS and ST section are inoperative, all outputs are switched off (safecondition).


• "ST RUN" LED: any status

• CPU display: Fault detection "*xxx" or "+xxx"

RemedyIt is not possible for the user to rectify the error. If the PSS is in this state,then the only option is to:




• Contact Pilz.


DW

084

085

086

087

088

089 ... 092

093 ... 096

097 ... 100

101 ... 104

105 ... 108

109 ... 112

113 ... 116

117 ... 120

121 ... 124

125 ... 128

129 ... 132

133 ... 136

137 ... 140

141 ... 144

145 ... 148

Assignment

Indicator pointing to current error entry

1st Error entry:

Bit 0 ... 7: Error classBit 8: if = 1 => it is an FS-error

if = 0 => it is an ST-errorBit 9 ... 15: ID of the microprocessor

Bit 0 ... 6: Error numberBit 7: if = 1 then error parameters -1/-2 arepresent

Error parameter -1

Error parameter -2

2nd Error entry

3rd Error entry

4th Error entry

5th Error entry

6th Error entry

7th Error entry

8th Error entry

9th Error entry

10th Error entry

11th Error entry

12th Error entry

13th Error entry

14th Error entry

15th Error entry

16th Error entry

Error stack

The error stack can record a maximum of 16 error entries. In system datablock DB000 it occupies data words DW085 ... DW148. Each error entryoccupies 4 words.

8-6



As the error stack is organised as a ring memory, data words are accessedvia the indicator in DW084. The indicator always points to the data wordcontaining the error class of the current error entry.

If more than 16 errors occur, the first entry is overwritten. The error stackcontains errors from both the FS and ST sections.

What the entries mean• Error class

The error class tells you what type of error it is, e.g. errors of the errorclass "06" are in the FS section "module errors".

• Error numberAll of the errors within an error class are numbered. The error numberspecifies an error more accurately within an error class. Example: FSsection, error class "06", error number "73" means "module error", "shortcircuit between test pulse outputs and 24 V".

• Error parameter-1, Error parameter-2The error parameters contain additional information about an error. Thecontents of the error parameter depend on the type of error.

The "error list" in the "PSS System Manual" describes the informationbehind an error entry. The errors can however also be displayed as plaintext messages, i.e. with descriptive text (see section "Display of errors asplain text").

INFORMATIONMessages are also entered in the error stack which are not error mes-sages. Instead, these are information messages intended for the user.These messages neither have an influence on the operating status nor theprogram cycle. This could for example be the information that a restart ofthe FS section was carried out (error class: F-20; error number: 01).


Display of errors as plain text

The display of errors as plain text, i.e. with a descriptive text, is possible forexample as follows:

• with the system softwareConnect the programming device and display the error stack of the PSSin the system software (PG) (see online help of the system software). Aplain text message is displayed for every error in the error stack. A rem-edy can be displayed for each error as required.

• with a text displayConnect a text display. If the FS section has changed to the STOP con-dition because of an error, then the ST section can read out the errorstack or the content of DB000, DW085 ... DW0148 and output a plaintext message to the text display. Standard function blocks from the "Errorevaluation" software package from Pilz can be used for this purpose.

8-8



Display of errors on the CPU display

If no error has occurred in the FS or ST section since the last change intoRUN, then the CPU display will show the following:

Any error which has occurred is displayed, e.g.:

The errors saved in the error stack can be displayed on the CPU display bypressing the "Error stack" button.

Display on 1st and 2nd generation controllers

Press and hold the error stack button. The data for the first entry in theerror stack are shown on the display in sequence, e.g.:

Release the error stack button again, then press and hold it again. Thedata for the next entry in the error stack are now displayed, e.g.:

0000

F-06

Error class (hexadecimally encoded)Entry number in error stack(hexadecimally encoded)ID for the FS/ST sectionF = error in FS sectionS = error in the ST section

Error class (hexadecimally encoded)ID for the error class

Error number (hexadecimally encoded)ID for the error number

F020

N=03

C=20


INFORMATIONIt depends on the error whether or not error parameters are displayed. Theway in which the error parameters should be interpreted also depends onthe error. The error parameters for every error are described in detail in the"Error list" in the "PSS System Manual". Help on the evaluation of the datain the error parameters can be found in the section "Evaluation of the errorparameters" in this chapter.

Error class (hexadecimally encoded)Entry number in error stack(hexadecimally encoded)ID for the FS/ST sectionF = error in FS sectionS = error in the ST section

Error class (hexadecimally encoded)ID for the error class


ID for "The first error parameter follows"

Error parameter -1

ID for "The second error parameter follows"

Error parameter -2

F106

N=07

C=06

AT

FFFE

PARA

0201

8-10



If you press and hold the error stack button again, then the data for thenext entry will be displayed. After the last entry in the error stack, thedisplay goes back to the first entry.

Display on 3rd generation controllers

Briefly press the error stack button.If the CPU display showed "0000" before the error stack button waspressed, the data for the first entry in the data stack will now be shown insequence on the display.If an error was displayed before the error stack button was pressed (e.g."F-06"), then the data for this error will be displayed in sequence, i.e. thedisplay starts with the entry of the last error which occurred, not with thefirst entry in the error stack.Example:

N-02

AT

0116

Entry number in error stack(hexadecimally encoded)ID for the entry number in the error stack

Error class (hexadecimally encoded)ID for the FS/ST sectionF = error in FS sectionS = error in the ST section


ID for "An error parameter follows"

Error parameter -1

F-06

ER02


The data display is repeated three times, then the rotation mode stops andthe CPU display reverts back to its initial status.If you wish to have the data for the next entry in the error stack displayedas well, then you should briefly press the error stack button while therotation mode is still running.In this way you can get the system to display the entire error stack.

To manually exit the rotation mode, press the error stack button for at least3 seconds.If the operating status changes while the rotation mode is active (e.g. dueto the operation of a selector switch on the PSS, or due to the FS sectionchanging to the STOP condition in response to an error), then the rotationmode is also stopped.

If an entry in the error stack has error parameters, the system displayserror parameter-1 first and then error parameter-2. The display isintroduced by means of an ID:

For some errors a range is indicated, e.g. the first and last defective inputof a module:

0318

TO

Address 3.18

ID for a range specification

Address 3.200320

PARA

AT

ID for "An error parameter follows"

8-12



INFORMATIONIt depends on the error whether or not error parameters are displayed. Theway in which the error parameters should be interpreted also depends onthe error. The error parameters for every error are described in detail in the"Error list" in the "PSS System Manual". Help on the evaluation of the datain the error parameters can be found in the section "Evaluation of the errorparameters" in this chapter.

On PSS with an FS operating system version ≥ 60, further information canbe called up after the final error entry.To do this, briefly press the error stack button while the final error entry isstill running in rotation mode.The ID “OrNo” is displayed, followed by the order number in rotation mode.If you press the error stack button again, the next ID will be displayed,followed by the data in rotation mode. This way you can call up all theinformation.

ID for “The PSS order number follows”

Order number, e.g. 301 200

ID for “The PSS serial number follows”

Serial number, e.g. 165 668

SrNo

0016

5668

OrNo

0030

1200


SubN

255.

255:

255.

240

ID for “The IP address of the Ethernet interfacefollows”1)

IP address, e.g. 169.254.060.001

ID for “The subnet mask of the Ethernet interfacefollows”1)

Subnet mask, e.g. 255.255.255.240

ID for “The IP address of the Router follows”1)

IP address, e.g. 169.254.060.001

ID for “The port for the Ethernet Configurator follows”1)

Port, e.g. 18080

R-IP

169.

254:

060.

001

ETH

0001

8080

IPAd

169.

254:

060.

001

8-14



ID for “The port for PSS WIN-PRO follows” 1)

Port, e.g. 1025

ID for “DHCP information follows” 1)

DHCP is activated

ID for “Versions follow”

FS operating system version, e.g. 60

SafetyBUS p bus version, e.g. 5

ST operating system version, e.g. 101

DHCP

ON

VERS

FS60

SB05

S101

PG

0000

1025

1) Only on PSS with Ethernet interface and an FS operating system version≥ 60. This information is only available if the network connection is active.This can take 1 to 2 minutes after a PSS cold start.


Evaluation of the error parameters

In order to evaluate the error parameters of an error, you will first need tolook at the "Error list" in the "PSS System Manual" to see what the contentof the error parameters is for the particular error (e.g. "Block" or "Slotnumber"). You can then interpret the display on the CPU according to thecontent.

Each error parameter corresponds to one data word in the error stack. Asthe CPU display has four digits, the error parameters are usually displayedas a hexadecimal number. The two left-hand digits on the display corres-pond to the left data byte (DL) and the two right-hand digits to the rightdata byte (DR).

Table for converting hexadecimal code into binary code:

Hexadecimal

0

1

2

3

4

5

6

7

Binary

0000

0001

0010

0011

0100

0101

0110

0111

Hexadecimal

8

9

A

B

C

D

E

F

Binary

1000

1001

1010

1011

1100

1101

1110

1111

Example: FFFB -> 1111 1111 1111 1011

8-16



The error parameters listed below require a special evaluation. All othererror parameters are numbers in hexadecimal format or, if specified expli-citly in the error list, numbers in decimal format.

Absolute address, decimal4-digit display, decimal code

• DL corresponds to the slot number

• DR contains the bit addressExample: The display "0318" corresponds to the address "3.18"

Absolute address, hexadecimal4-digit display, hexadecimal codeThe hexadecimal code on the display needs to be converted into binarycode.

• Bit 0 … 4: Bit section of address

• Bit 5 … 15: Slot numberExample: The conversion of the display "00B1" into binary code yields"0000 0000 1011 0001". The resulting address is "5.17".

Block4-digit display, hexadecimal code

• DL indicates the block type08 = DB10 = SB20 = PB40 = FB80 = OB

• DR contains the block number in hexadecimal code


Bit sequence2 or 4-digit display in hexadecimal codeThe hexadecimal code on the display needs to be converted into binarycode.

With 1st and 2nd generation controllers, the defective inputs/outputs onmodule and wiring errors are output as a bit sequence. Each bit in the bitsequence corresponds to one input/output on the module.Bit = 1 means that the corresponding input/output is error-free, and bit = 0means that the corresponding input/output is faulty.

��

��

&. &/ &' &( && &0 1 2 3 4 . / ' ( & 0

��+��%��)��)+��*5"��)��

'& '0 (1 (2 (3 (4 (. (/ (' (( (& (0 &1 &2 &3 &4

��+��%��$��)+��*5"��)��

3� 4� .� /� '� (� &� 0� 36 46 .6 /6 '6 (6 &6 06

��+��%��)��)+��)��*5"��)��

('� ((� (&� (0� &1� &2� &3� &4� ('6 ((6 (&6 (06 &16 &26 &36 &46

��+��%��$��)+��)��*5"��)��

In order to determine the absolute bit address, you also need to know theslot and sub-slot. These details can be found in error parameter-2.

8-18



Example table for a faulty bit on an upper sub-slot

Hexadecimalcode on theCPU display

FFFE

FFFD

FFFB

FFF7

FFEF

FFDF

FFBF

FF7F

FEFF

FDFF

FBFF

F7FF

EFFF

DFFF

BFFF

7FFF

Conversion tobinary code

1111 1111 1111 1110

1111 1111 1111 1101

1111 1111 1111 1011

1111 1111 1111 0111

1111 1111 1110 1111

1111 1111 1101 1111

1111 1111 1011 1111

1111 1111 0111 1111

1111 1110 1111 1111

1111 1101 1111 1111

1111 1011 1111 1111

1111 0111 1111 1111

1110 1111 1111 1111

1101 1111 1111 1111

1011 1111 1111 1111

0111 1111 1111 1111

Bit address

single-pole dual-pole

X.00 X.00+

X.01 X.01+

X.02 X.02+

X.03 X.03+

X.04 X.04+

X.05 X.05+

X.06 X.06+

X.07 X.07+

X.08 X.00-

X.09 X.01-

X.10 X.02-

X.11 X.03-

X.12 X.04-

X.13 X.05-

X.14 X.06-

X.15 X.07-


Example table for a faulty bit on a lower sub-slot

Hexadecimalcode on theCPU display

FFFE

FFFD

FFFB

FFF7

FFEF

FFDF

FFBF

FF7F

FEFF

FDFF

FBFF

F7FF

EFFF

DFFF

BFFF

7FFF

Conversion tobinary code

1111 1111 1111 1110

1111 1111 1111 1101

1111 1111 1111 1011

1111 1111 1111 0111

1111 1111 1110 1111

1111 1111 1101 1111

1111 1111 1011 1111

1111 1111 0111 1111

1111 1110 1111 1111

1111 1101 1111 1111

1111 1011 1111 1111

1111 0111 1111 1111

1110 1111 1111 1111

1101 1111 1111 1111

1011 1111 1111 1111

0111 1111 1111 1111

Bit address

single-pole dual-pole

X.16 X.16+

X.17 X.17+

X.18 X.18+

X.19 X.19+

X.20 X.20+

X.21 X.21+

X.22 X.22+

X.23 X.23+

X.24 X.16-

X.25 X.17-

X.26 X.18-

X.27 X.19-

X.28 X.20-

X.29 X.21-

X.30 X.22-

X.31 X.23-

INFORMATIONIf more than one input/output is faulty, then there will be a 0 at the relevantpositions.Example: "FAFB" corresponds to "1111 1010 1111 1011", i.e. the bits 10, 8and 2 are defective.

8-20



Error code2 or 4-digit display in hexadecimal codeThe error code is used by Pilz for fault diagnostics. The error code cannotbe evaluated by the user.

I/O group2-digit display, hexadecimal code

00 ... 1F = Hexadecimally coded number of the I/O group

FE = All I/O groups which are assigned to the LD

FF = All I/O groups

Item2-digit display in hexadecimal code

00 = Item 0, corresponds to I/OD A

FF = Item 1, corresponds to I/OD B

Sub-slot2-digit display, hexadecimal code

00 = Total module(for single-pole I/O modules: Bit addresses 0 ... 31;for two-pole I/O modules: Bit addresses 0+/- ... 23+/-)

01 = Upper sub-slot(for single-pole I/O modules: Bit addresses 0 ... 15;for two-pole I/O modules: Bit addresses 0+/- ... 7+/-)

02 = Lower sub-slot(for single-pole I/O modules: Bit addresses 16 ... 31;for two-pole I/O modules: Bit addresses 16+/- ... 23+/-)


Diagnostics

Various tools are available for fault diagnostics in the system software(PG):

• Displays of variables

• Dynamic program display

• Control/Force variables

Control/force variables

Here, to "force" means to set an input or an output to a fixed preset status,regardless of the user program.On the other hand, flags, data bytes and data words, timers and countersare set just once to the preset value, in other words, controlled. In contrastto the inputs and outputs they can be changed by the user program.

Information on how to control/force the variables can be found in the onlinehelp of the system software (PG).

Permitted for controlling/forcing:

Type

Inputs

Outputs

Data bytes/datawords(DB010 ... 255)

Flags

Timers

Counters

Words of wordmodules

Operand

E00.00 ... E23.31EB00.00 ... EB23.24EW00.00 ... EW23.16

A00.00 ... A23.31AB00.00 ... AB23.24AW00.00 ... AW23.16

DW0 ... DW1023DL0 ... DL1023DR0 ... DR1023

M00.00 ... M63.31

T00 ... T63

ZW00 ... ZW63

XW0 ... XW16383

Force

X

X

Control

X

X

X

X

X

8-22



Display of variables

In the system software (PG), the values of any operand(s) from one ormore blocks are displayed as part of the variables display. The system canalso display the absolute addresses of the safety system (e.g. inputs andoutputs).

Information on how to display the variables can be found in the online helpof the system software (PG).

Fig. 8-2: Display of variables in PSS WIN-PRO


Fig. 8-3: Dynamic program display in PSS WIN-PRO

Dynamic program display

When a block is shown in dynamic program display in the system software(PG), the contents of the indirect addresses, operands, RLO, accumulatorand auxiliary accumulator are shown next to the program code.

Information on how to perform the dynamic program display can be foundin the online help of the system software (PG).

8-24



Notes


System data blocks

Data blocks are available for communication between the ST user programor the system software (PG) and the operating system. The tables belowgive an overview of their assignment.

DB000

DB000 contains general program data. It cannot be changed from the userprogram.

INFORMATIONDB000 can only be read from the standard section.

Appendix

Data Word AssignmentFormat

KY

KY

KY

KY

KH

KH

KH

KH

KH

KH

KH

KH

KH

Current yearByte 1: 00Byte 2: 00 ... 99

Byte 1: Current month 01 ... 12Byte 2: Current day 01 ... 31

Byte 1: Current hour 00 ... 23Byte 2: Current minute 00 ... 59

Byte 1: Current second 00 ... 59Byte 2: free

FS operating system version

Hardware version

Reserved

Current scan time in ms

Max. scan time in ms since theFS section was last started

Current FS block run time in ms

Max. FS block run time in ms since theFS section was last started

Current ST block run time in ms

Max. ST block run time in ms since theST section was last started

000

001

002

003

004

005

006

007

008

009

010

011

012

9-2

Appendix


Duration of the self-test in ms

Indication of what is shown on the CPU display:0 = user data, see DW0151 = FS error ("F-xx")3 = ST error ("S-xx")

If DW014 = 0: User data (hexadecimal figure) fromthe CPU displayIf DW014 = 1: Error class of FS errorIf DW014 = 3: Error class of ST error

Reserved

Actual configuration of the ST sectionDW020: Code for module on slot 0...DW043: Code for module on slot 23

Reserved

Indicator pointing to current error entry

1st Error entry:

Bit 0 ... 7: Error classBit 8: if = 1 => it is an FS-error

if = 0 => it is an ST-errorBit 9 ... 15: ID of the microprocessor

Bit 0 ... 6: Error numberBit 7: if = 1 then error parameters -1/-2 arepresent

Error parameter -1

Error parameter -2

2nd error entry

3rd error entry

4th error entry

5th error entry

6th error entry

7th error entry

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

013

014

015

016 ... 019

020 ... 043

044 ... 083

084

085

086

087

088

089 ... 092

093 ... 096

097 ... 100

101 ... 104

105 ... 108

109 ... 112

DB000 continued




8th error entry

9th error entry

10th error entry

11th error entry

12th error entry

13th error entry

14th error entry

15th error entry

16th error entry

Internal software version, microprocessor A

Internal software version, microprocessor B

Internal software version, microprocessor C

Internal hardware version, microprocessor A

Internal hardware version, microprocessor B

Internal hardware version, microprocessor C

ST operating system version

Internal hardware version of the ST section

Operating system CRC sum

FS user program CRC sum

Short name of FS user program

Link date of FS user program: Year

Link date of FS user programDL: MonthDR: Day

Link date of FS user programDL: HourDR: Minute

Version of SafetyBUS p interface

Reserved

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KH

KC

KH

KY

KY

KH

-

113 ... 116

117 ... 120

121 ... 124

125 ... 128

129 ... 132

133 ... 136

137 ... 140

141 ... 144

145 ... 148

149

150

151

152

153

154

155

156

157 ... 163

164

165 ... 168

169

170

171

172

173 ... 176

DB000 continued

9-4

Appendix



DB000 continued

177

178 ... 179

180 ... 181

182 ... 183

184 ... 185

186

187

188

189

190 ... 195

196

197

198

199

200 ... 220

221 ... 239

KH

-

KH

KH

KH

KH

KH

KH

-

-

KY

KY

KY

KY

KH

-

SafetyBUS p bus version (SBp protocol)

Free

IP address of Ethernet interface1)

Subnet mask of Ethernet interface1)

IP address of Router1)

Port for the Ethernet Configurator1)

Port for PSS WIN-PRO1)

DHCP information1)

1 = DHCP is activated

Reserved

Free

YearByte 1: 00Byte 2: 00 ... 99

Byte 1: Month 01 ... 12Byte 2: Day 01 ... 31

Byte 1: Hour 00 ... 23Byte 2: Minute 00 ... 59

Byte 1: Second 00 ... 59Byte 2: Type of time details in DW 196 ... 199

0 = Relative time (time that has elapsedsince the programmable safety systemwas first switched on)1 = Absolute time (system time onthe programmable safety system)

Parameters for operating system calls in the STsection

Free


DB000 continued


240 ... 399 FS program downloads, resets of the remanentFS-DBs and changes to the system time arelogged in data words 240 to 399.2)

Each entry is 10 data words long. The most recententry is always in DW240 ... DW249 and movesolder entries to the following data words.

Entry for FS program download:1st DW CRC sum (KH)2nd - 5th DW Short name (KC)6th DW Link date, Bit 0 … 15 (KH)7th DW Link date, Bit 16 … 31 (KH)8th DW Download date, Bit 0 … 15 (KH)9th DW Download date, Bit 16 … 31 (KH)

Entry for change to system time:1st DW 0000 (KH)2nd DW 0001 (KH)3rd DW Old date, Bit 0 ... 15 (KH)4th DW Old date, Bit 16 ... 31 (KH)5th DW New date, Bit 0 ... 15 (KH)6th DW New date, Bit 16 ... 31 (KH)7th - 9th DW Free

Entry for resetting the remanent FS-DBs:1st DW 0000 (KH)2nd DW 0002 (KH)3rd DW Resolution (KH)

If = 1, manualIf = 2, automatic

4th DW Date, Bit 0 ... 15 (KH)5th DW Date, Bit 16 ... 31 (KH)6th - 9th DW Free

9-6

Appendix


DB000 continued


240 ... 249

250 ... 259

260 ... 269

270 ... 279

280 ... 289

290 ... 299

300 ... 309

310 ... 319

320 ... 329

330 ... 339

340 ... 349

350 ... 359

360 ... 369

370 ... 379

380 ... 389

390 ... 399

Date detailsTime details may be relative or absolute,depending on DW199, Byte 2.Absolute time details:Bit 0 ... 5: SecondBit 6 ... 11: MinuteBit 12 ... 15: MonthBit 16 ... 20: HourBit 21 ... 25: DayBit 26 ... 31: Year (maximum 63)

Relative time details:Bit 0 ... 5: SecondBit 6 ... 11: MinuteBit 12 ... 15: Day, upper 4 BitBit 16 ... 20: HourBit 21 ... 31: Day, lower 11 Bit

1st entry (most recent entry)

2nd entry

3rd entry

4th entry

5th entry

6th entry

7th entry

8th entry

9th entry

10th entry

11th entry

12th entry

13th entry

14th entry

15th entry

16th entry


DB000 continued


400

401

402

403

404

405

406

407

408 ... 423

424

425

426

427 ... 499

KY

KH

KH

KH

KH

KH

KH

KH

KC

KH

KY

KY

KH

Device version (identical to the information on thetype label)DL: Figure before the decimal pointDR: Figure after the decimal point

Reserved

Serial number (high word)

Serial number (low word)

Reserved

Order number (high word)

Order number (low word)

Reserved

Name of PLC in plain text

Device data CRC sum

Programming date of device dataDL: MonthDR: Day

Programming date of device dataDL: FreeDR: Year

Reserved for further device data

1) Only on PSS with Ethernet interface and an FS operating system version≥ 60. This information is only available if the network connection is active.2) Only on PSS with an FS operating system version ≥ 60.

9-8

Appendix



Reserved

Cyclic configuration test (ST section)0 = switched on1 = switched off

Configuration test during start-up (ST section)0 = switched on1 = switched off

Registered hardware of the ST sectionDW020: Code for module on slot 0...DW043: Code for module on slot 23:

Reserved

Parameters for operating system calls in the STsection

000 ... 017

018

019

020 ... 043

044 ... 199

200 ... 220

KH

KH

KH

KH

KH

KH


Start addresses (0 ... 16383) of the word modulesDW000: Word module on slot 0...DW023: Word module on slot 23

Reserved

000 ... 023

024 ... 063

KF

KH

DB004

DB004 contains general program data for the ST section.

DB005

DB005 contains data for the word modules.


000

001

002

003

004

005

006


KF

KF

KF

KF

KF

KF

KF

Reserved

Error identifiers in the event of configuration errorof the user interface0002H ... 000CH: Number of the faulty data word inDB006FFF0H: Interface is assigned to the FS section

Transmission rate in bit/s0 = 1501 = 3002 = 6003 = 1,2004 = 2,4005 = 4,8006 = 9,6007 = 19,2008 = 38,400 (only on 3rd generation PSS)

Parity bit0 = none1 = odd2 = even

No. of stop bits0 = 11 = 1.52 = 2

No. of data bits0 = 51 = 62 = 73 = 8

Handshake0 = no1 = yes

DB006

DB006 is the configuration DB for the user interface.

9-10

Appendix



007

008

009

010

011

012

KF

KF

KF

KF

KF

KF

ISI protocol0 = no1 = yes

CPU as Master or Slave (with ISI protocol only)0 = Master1 ... 31 = Slave, with corresponding address

Timeout for Slave answer (with ISI protocol only)0 = Master1 ... 65,535 = Timeout in ms

Timeout when receiving1 ... 65,535 = Timeout in ms

Timeout when sending (only for transmission withhandshake)0 = infinite1 ... 65,535 = Timeout in ms

DTR controller0 ... 2,044 = specifies how many bytes before 2044sending is due to be stopped

DB006 continued



Number of bytes to be sent

Error identifiers for send errors0: Timeout exceeded on send (partner not

ready to receive)16: Number of bytes to be sent is too high17: Send command currently not available,

e.g. because a telegram is just being sent.18: Interface not yet configuredFFF0

H: Interface is assigned to the FS section

FFFFH: No error

with ISI protocol: Slave address if the safetysystem is the Masterwithout ISI protocol: first send data word

Send dataSend sequence without ISI protocol: DR2, DL2,DR3, DL3, ....Send sequence with ISI protocol: DR3, DL3, DR4,DL4, ...

000

001

002

003 ...1023

KF

KF

KF

KF

DB007

DB007 is the send DB for the user interface.

9-12

Appendix



Number of bytes to be received

Error identifiers for receive errors0: Send timeout exceeded (for ISI protocol

only)1: Parity error2: Receive "Break"3: Stop bit error8: Overflow error; characters have been lost,

e.g. because the last telegram receivedwas not acknowledged quickly enough.

9: Number of the receive-DB10: Slave not answering in time (for ISI

protocol only)11: Number of received bytes incorrect (for ISI

protocol only)12: CRC error (for ISI protocol only)13: ID error (for ISI protocol only)14: Incorrect Slave answering (for ISI protocol

only)15: End identifier missing or end of telegram

contains too few characters (for ISIprotocol only)

17: Command not permitted at this time18: Interface not yet configured19: Telegram header contains too few charac-

ters (for ISI protocol only)FFF0H: Interface is assigned to the FS sectionFFFFH: No error

with ISI protocol: not relevantwithout ISI protocol: first received data word

Receive dataSend sequence without ISI protocol: DR2, DL2,DR3, DL3, ....Receive sequence with ISI protocol: DR3, DL3,DR4, DL4, ...

000

001

002

003 ...1023

KF

KF

KF

KF

DB008

DB006 is the receive DB for the user interface.



available for free use000 ... 063 KF

DB009

DB009 can be used as a remanent memory in the user program. Thecontent of the data module is retained after a general reset, it is not initial-ised.

9-14

Appendix


FUNK PageDescription

6-25

6-30

6-33

6-13

6-12

6-14

4-8

6-9

Configuration of the user interface

Sending via the user interface

Receiving via the user interface

Set System Time

Output of hexadecimal numbers to the CPUdisplay

Selection of FS data blocks

Poll 32-bit timer


012

456

81011

12

32

36

151

180

Operating system calls with SB254

INFORMATIONThere are also further functions for special applications (e.g. operation ofthe Interbus interface). These are described in the corresponding manualsand operating manuals.


Changes in the documentation

Changes in Version 18 586-06

The System Description was completely revised.


Old New Changepage page

4-6 4-6 SB254, FUNK = 151

5-1 5-1 New: Diagnostic configuration

- 6-9 SB254, FUNK = 180

6-16 6-16 New: FS status flag M113.07 and M113.08

8-12 8-12 New: PSS information that can be called up via theerror stack button

9-1 9-1 Layout of DB000: DW172 to DW399



- 4-3 New: Definition of "non-volatile"

6-24 6-24 FS status flag M113.07 deletedFS status flag M113.08 amended



4-2 4-2 New: Ability to operate PSS with an FSoperating system version >= 70 without a battery

9-16

Appendix


Notes


Index

AAccess rights 6-17Accumulator

display 8-23Addresses

display 8-22Addressing 5-5

free 5-6Alarms 6-6Allocation table 5-2Arithmetic flags 6-15Auxiliary accumulator

display 8-23

BBase module rack 4-2Battery 4-2Binary code 8-15Bit encoding 8-17Bit numbers 5-5Bit sequences 8-17Block run time 6-3

Definition of 6-6Blocks 5-2

Data blocks 5-2Interface configuration DB 6-26Receive-DB 6-34Send-DB 6-31

Function blocks 5-2Organisation blocks 5-2, 5-6

Error organisation blocks 8-2Program blocks 5-2Standard function blocks 5-2, 5-7

Bus 4-3

CCentral processing unit 4-3Channels 2-1Checksum calculation 6-22Clock 6-13Code

binary 8-15Error code 8-20hexadecimal 8-15

CommissioningRecommissioning 7-2

CommunicationFS - ST 6-15User interface 6-18

Communication flags 6-15Compact PSS 2-3, 4-1Configuration 5-2

Block run time 6-6changing 7-3Registered hardware 6-7Scan time 6-5Test 6-11

Configuration data blockUser interface 6-26

Configuration error 6-11Configurator 5-2Control

Counter 8-21Data words 8-21Flags 8-21Inputs 8-21Outputs 8-21Timer 8-21

ControllerCompact 2-3, 4-1Modular 2-2, 4-1

CounterDisplay status 8-22

Counter bit 4-8Counter word 4-8Counters 4-8

Control 8-21CPU 4-3CPU display 4-8

Error display 8-8CRC calculation 6-22CTS 6-21Cycle OB 5-6

DData blocks 4-4, 5-2

Interface configuration DB 6-26Read-only 4-4Read/write 4-4Receive-DB 6-34Select FS 6-14Send-DB 6-31System data blocks 9-1

Data memory 4-4

Index


Read-only 4-4Read/write 4-4

Data transfer 5-4with handshaking 6-20with ISI protocol 6-22without protocol 6-21

Data words 4-4Control 8-21Display status 8-22

DB000 9-1DB004 9-5, 9-6, 9-7DB005 9-8DB006 9-9DB007 9-11DB008 9-12DB009 9-13Diagnostic configuration 5-3Diagnostics 8-8, 8-21Display 4-8

Display 6-12Dynamic program display 8-23Error display 8-7, 8-8Error stack 8-8Variables 8-22

Diversity 2-1DL 4-4DR 4-4DSR 6-21DTR 6-20DW 4-4Dynamic program display 8-23

EError

fatal 8-3, 8-4Error class 8-6Error code 8-20Error list 8-6Error management 8-1Error number 8-6Error organisation blocks 8-2Error parameters 8-6Error stack 8-5

button 4-9displaying 8-8

Errorsdisplay 8-7displaying 8-8minor 8-2

Ethernet-2 interface 4-6Expansion module 4-2Expansion module rack 4-2

FFailsafe section 2-1Fatal error 6-37, 6-38FBD 2-4Fixed flags 6-15Flags

Arithmetic flags 6-15Communication flags 6-15Control 8-21Display status 8-22Fixed flags 6-15Status flags 6-16

ForceInputs 8-21Outputs 8-21

FS section 2-1FS selector switch 4-9Function Block Diagram 2-4Function blocks 5-2

GGeneral reset 4-5

HHandshaking 6-20Hardware registry test 6-11Hexadecimal code 8-15

IID handling 6-23IL 2-4Initial commissioning 7-1Input module 4-10Inputs

Display status 8-22Force 8-21Process image 6-2Reading in 6-1

Instruction List 2-4Interface adapter 5-4Interface configuration DB 6-26


InterfacesProgramming device interface 4-6RS 232 4-6RS 485 4-6User interface 4-6, 6-18

Configuring 6-25Handshaking 6-20Receive 6-33Send 6-30

ISI protocol 6-22Item 8-20

LLadder Diagram 2-4LD 2-4Linking 5-3

MMemory

Data memory 4-3Program memory 4-3

Message errors 8-6Messages

display 6-12Microprocessor 4-3Minimum scan time 6-5Modular PSS 2-2, 4-1Module

Addressing 5-5Module rack 4-2Modules

Input modules 4-10Output modules 4-10

NNetworks 6-19Non-volatile 4-3

OOB001 5-6Operating states 6-36

Fatal Error 6-38RUN 6-37ST Fatal Error 6-37STOP 6-37

Operating status change 6-36

Operating system calls 5-7, 9-14Organisation blocks 5-2, 5-6Output

Direct 6-1via process images 6-2

Output blockFS section 6-5ST section 6-5

Output module 4-10Outputs

Display status 8-22Force 8-21Process image 6-2Writing to 6-1

PParity bit 6-26PB 6-1Periphery access

Direct 6-1via process images 6-2

Periphery bytes 6-1Periphery modules - see Input/output modules 4-10Periphery words 6-1PG interface 4-6PII 6-2PIO 6-2Plain text messages 8-7Power supply 4-2Process image 6-2

Inputs 6-2Outputs 6-2

Program 5-1changing 7-3Start 4-9Stop 4-9Transfer 5-4

Program blocks 5-2, 6-3Program cycle 6-3Program display

Dynamic 8-23Accumulator 8-23Auxiliary accumulator 8-23Indirect addresses 8-23Inputs 8-23Outputs 8-23Result of logic operation 8-23Word operands 8-23

Index


Program memory 4-4Program scan time 6-3Program transfer 5-4Programming 5-1Programming adapter - see Interface adapter 5-4Programming device 2-4

Interface 4-6Programming languages 2-4Programming model 5-1Project 5-1

Create 5-3Protocol

ISI protocol 6-22PSS

Compact 2-3, 4-1Modular 2-2, 4-1

PSS configuration 5-2PSS configurator 5-2PSS WIN-PRO 2-4PW 6-1

RRead block

FS section 6-4ST section 6-5

Read-only 4-4Read-write 4-4Real-time 6-13Receive-DB 6-34Recommissioning 7-2Registered hardware 6-7Reset block 6-3Restart 4-4, 4-5Result of logic operation

Display 8-23RS 232 4-6RS 485 4-6RTS 6-21RUN 6-37

SSafety guidelines 2-1SafetyBUS p

Configuration 5-3SB254 5-7, 9-14

FUNK 000 6-25FUNK 001 6-25FUNK 002 6-25

FUNK 004 6-30FUNK 005 6-30FUNK 006 6-30FUNK 008 6-33FUNK 010 6-33FUNK 011 6-33FUNK 151 4-8FUNK 180 6-9

Scan time 6-3Definition of 6-6Minimum 6-5

Scan time block 6-5Selector switch 4-9Self-test 6-7Send-DB 6-31Slot 5-5Slot number 5-5ST section 2-2ST selector switch 4-9Standard function blocks 5-2, 5-7Standard section 2-2Start-up 6-3Start-up block 6-3Start-up procedure 4-9States 6-36

Fatal Error 6-38RUN 6-37ST Fatal Error 6-37STOP 6-37

Status change 6-36Status flags

FS section 6-16ST section 6-17

STOP 6-37Sub-slots 5-5Supply voltage 4-2System data 4-4System data blocks 9-1System error 8-3, 8-4System software 2-4

TTelegrams 6-22Test block 6-5Test slices 6-5Tests

Hardware registry test 6-11Self-test 6-7

Time base 4-7


Time value 4-7Timeout time 6-21Timer 4-7

Display status 8-22Timers

Control 8-21Times

Block run time 6-3Scan time 6-3

UUser interface 4-6, 6-18

Configuring 6-25Receive 6-33Send 6-30

User program 4-3, 5-1changing 7-3Cycle 6-3Errors 8-2

VVariable

Control 8-21Force 8-21

Variable display 8-22

WWord modules 6-7

Direct periphery access 6-1Word operands

Display 8-23Write protection 4-4

XXW 6-8

Index


Notes

•

• … • wwwwww.pilz.com

+49 711 3409-444

18

587-

09, 2

00

9-03

Prin

ted

in

Germ

an

y

© P

ilz G

mb

H &

Co

. K

G, 2

00

8

Pilz GmbH & Co. KG Felix-Wankel-Straße 273760 Ostfi ldern, GermanyTelephone: +49 711 3409-0Telefax: +49 711 3409-133E-Mail: [email protected]

Technical support

In many countries we are represented by our subsidiaries and sales partners.

Please refer to our homepage for further details or contact our headquarters.

pss-range modular and compact pss -...

Documents