Programmable valve terminals type 02 with control block SB 50 / SF 50 Manual

Transcription

1 Programmable valve terminals type 02 with control block SB 50 / SF 50 Manual SIMATIC Integrated

2 TN

3 VISB - 50 Authors: Translation: Editor: Layout: Typesetting: Uwe Gräff Siegfried Rechenberger Sturz, Reutlingen PV-IIP Festo KG, PV-IIP PV-IIP/Rb PN printed on 100% recycled paper 4th edition, December Festo AG & Co., D Esslingen 1 The copying, distribution and utilization of this document as well as the communication of its contents to others without expressed authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved, in particular the right to carry out patent, utility model or ornamental design registrations. E0n I

4 VISB - 50 Order No: Title: Designation: MANUAL P.BE-SB50-02-GB SIMATIC, STEP, SINEC and COROS are registered Trademarks of Siemens AG. II E0n

5 VISB - 50 Programmable valve terminals Many control tasks involving mainly pneumatic final control elements (cylinders, etc.) can be automated without the need for a control cabinet. An integral programmable controller with the command set and range of functions of SIMATIC mini controllers allows programming to be carried out easily using familiar tools. SIEMENS, the market leader in PLC technology, and FESTO, the market leader in pneumatics, have worked together to offer the market a perfect solution. PN E0n III

6 VISB - 50 Summary of parts Part 1 Basic principles of installation contains information which is not dependent on the type of valve terminal or on the node selected. Part 2a Valve terminal type 02 System description of valve terminal type 02, contains all necessary information specifically for this type of terminal. Part 2b Valve terminal type 03 System description of valve terminal type 03, contains all necessary information specifically for this type of terminal. Part 3 System description of SB 50 contains all relevant PLS information irrespective of the type of valve teminal. Part 4 Part 5 Part 6 System description SF 50 as master contains additional information required for using the PROFIBUS-DP. System description SF 50 as DP-Slave contains additional information required for using the SF 50/DP-Slave (SL50). Appendix contains additional information on commands, abbreviations, accessories, literature, etc. IV E0n

7 Programmable valve terminals with Control block SB 50 / SF 50 Part 1: Installation guidelines PN

8 PN is shown in: Manual Manual Manual

9 VISB User instructions 1.1 USER INSTRUCTIONS PN

10 VISB User instructions Contents 1.1 IMPORTANT USER INSTRUCTIONS Danger categories Pictograms Instructions for this manual

11 VISB User instructions 1.1 IMPORTANT USER INSTRUCTIONS Danger categories This description contains instructions concerning possible dangers that can occur when using the programmable valve terminal with the control block SB 50. A distinction is made between the following instructions: WARNING This means that physical or material damage can occur if these instructions are not observed. CAUTION This means that material damage can occur if these instructions are not observed. PLEASE NOTE This means that this instruction must also be observed

12 VISB User instructions Pictograms Pictograms and (graphical) symbols supplement the danger instructions and draw attention to the nature and consequences of the dangers. The following pictograms are used: Uncontrolled movement of loosened tubing. Uncontrolled movement of the connected actuators. High electric voltage or Undefined switching states of the electronic components which affect the connected circuits. Electrostatically vulnerable components. These will be damaged if their contact surfaces are touched. SIMATIC Integrated When the operating mode of the SB/SF 50 differs from the operating mode of the SIMATIC mini-pc, then the relevant section will be marked with this icon

13 VISB User instructions Instructions for this manual This manual uses the following product-specific abbreviations: Abbreviation Meaning Terminal or Programmable valve terminal valve terminal with control block SB 50 / SF 50 with/without electrical I/Os Node Control block SB / SF 50 I Input Q Output I/Q Input and/or output Specialist pneumatic, electronic and programming terms are explained in the glossary

14 VISB User instructions Programmable valve sensor terminals generally consist of the following components. Nodes with control block SB 50 or SF 50 In the case of type 02 valve terminals: sub-base corresponds to the number of valves In the case of type 03 valve terminals: - pneumatic modules - electrical modules PLEASE NOTE Information concerning the terminal types 02 and 03 can be found in sections 2a and 2b in this manual, depending on your order. The majority of the drawings in this manual are based on a valve terminal type 03 with four pneumatic terminal blocks and four input/output modules. Fig. 1/1: Standard configuration for the drawing

15 VISB System summary 1.2 SYSTEM SUMMARY PN

16 VISB System summary Contents 1.2 SYSTEM SUMMARY Programmable valve terminal Valve terminal in standalone operating mode (SB 50) Valve terminal in master operating mode (SF 50) Programming tools Programming software STEP Parameter software COM ET200 WINDOWS / COM PROFIBUS Terminal-summary Valve terminals with analogue modules Valve terminal with AS-i master Valve terminal in slave operating mode

17 VISB System summary 1.2 SYSTEM SUMMARY Programmable valve terminals The SB 50 control block includes a SIMATIC PLC therefore making the FESTO valve terminals types 02 and types 03 into programmable valve terminals. There are two forms for the control blocks: SB for valve terminal type 02 SB for valve terminal type 03 Independent automation tasks require the use of sensors. These can be directly connected to the valve terminal. Regardless of the type of valve terminal, there are various numbers of input modules available. In addition, electrical outputs are available. This means that independent automation tasks can be solved on-site. Advantages of the programmable valve terminal with control block SB 50 Built-in SIMATIC PLC Protection class IP 65 is fulfilled no control cabinet required Simple equipment layout with independent control on site Low wiring costs Pre-assembled valves Hard-wired valve solenoid coil Central exhaust Inspected unit Electrical inputs e.g. for sensors Electrical outputs, e.g. for electrical actuators Further advantages, depending on the type of valve terminal

18 VISB System summary The built-in PLC represents a SIMATIC with the command set for mini control systems. The programmable valve terminals can be operated with the following: Pushbutton panel (START/STOP) Keyboard with text display (OP5) For programming you will require a PC or one of the reliable programming tools PG685 to PG770 and the SIMATIC programming software STEP 5. The PC or programmer must be connected to the diagnostic interface of the control blocks. PLEASE NOTE The standard programming cable from Siemens can be used for the connection. When using a PC as a programming tool, an active interface convertor V.24 TTY is required. The following programming languages are available: CSF (control system function chart) LDR (Ladder diagram) STL (Statement List) The following two diagrams show a system summary: Valve terminal in standalone operating mode (SB 50) A valve terminal type 02 fitted with a control block SB 50-02, or a valve terminal type 03, fitted with a control block SB 50-03, forms the independently operating controller

19 SIEMENS PG 24VDC RUN STOP L2-DP FUSE BF VISB System summary Operation is implemented either by a control panel with keys, which is connected to the free inputs and outputs or by a control panel with COROS OP5, which is connected to the diagnostic interface of the control block. In this case, the OP5 is programmed via the software COM TEXT or PROTOOL/Lite. Operation + monitoring Valve terminal type 03 as independent controller Start/Stop buttons Control unit OP5 in housing STEP 5 COM PROFIBUS PROTOOL LITE Programmer PG PG770 Fig. 1/2: System structure with SB

20 VISB System summary Valve terminal in master operating mode (SB 50) A valve terminal type 02 fitted with a control block SF 50-02, or a valve terminal type 03, fitted with a control block SF 50-03, forms the central operating controller as the field bus master. Operation is implemented either by a control panel with keys, which is connected to the free inputs and outputs or by a control panel with OP5 or OP15, which is connected to the diagnostic interface of the control block. In this case, the OPx is programmed via the software COM TEXT or PROTOOL/Lite. Slaves of the PROFIBUS-DP can include: Field bus valve terminals with FB9/FB13, types and type 10 from Festo The decentralized peripherals of the SIMATIC ET 200 PROFIBUS-DP-slaves of other manufacturers A PG programmer or a PC should be used for programming. The programmers PG720/740/760 are fitted as standard with the MPI interface, which can be used for the PROFIBUS-DP-configuration. The interface component for the PROFIBUS-DP-configuration can be retro-fitted to the programmers PG730/750/770 or a PC

21 SIEMEN S PG RUN STOP L2-DP 24 VDC F U SE BF VISB System summary Operation and monitoring Interface construction Group Plug-in module Programmers PG720...PG770 STEP5 COM PROFIBUS PROTOOL LITE Start/Stop buttons Valve terminal type 03 as Master Control unit OP5 in housing PROFIBUS-DP Valve terminal type 03 with field bus nodes FB9 ET 200U Other slaves for SINEC L2-DP and/or PROFIBUS-DP Fig. 1/3: System structure with SF

22 VISB System summary Programmers The following programmers can be used for program generation in the SB 50 control block: PG685, PG710 (SB 50 only) PG PC with programming software STEP 5 Programming software STEP 5 STEP 5 STEP 5 is the programming language for application programms using the SIMATIC S5 automation unit and the FESTO valve terminals with built-in SIMATIC- PLC. The application programms can be displayed in CSF (Control system function chart) LDR (Ladder diagram) STL (Statement List) CSF I2.3 I4.3 I3.2 & >=1 Q 1.6 LDR I2.3 I4.3 Q1.6 ( ) I3.2 STL A I2.3 A I4.3 Q I3.2 = Q

23 VISB System summary COM PROFIBUS Parameter software COM ET 200 WINDOWS / COM PROFIBUS The addresses of the inputs and outputs of the decentralized peripheral devices are determined by means of the parameter software COM ET 200 WIN- DOWS / COM PROFIBUS. The plug-in module, which must be installed in the PG/PC, writes into the EE- PROM memory, which is integrated in the SIMATIC- PLC. The software Festo SF 50 Download can be used as an alternative to the interface component (see chapter 4.1)

24 PG SI EMENS RUN STOP L2-DP BF VISB System summary Terminal-summary The control blocks SB 50 and SF 50 can be operated with valve terminals type 02 and type 03. The control blocks SB 50 then allow independent control of the valve terminal. When the SF 50 control block is used as the master of a PROFIBUS-DP field bus system, extensive and complex systems can be controlled. Valve terminal type 02 Fig. 1/4: Example of a valve terminal type 02 with SF 50 - Component size 1/8 inch, 1/4 inch - 4 / 6 / 8 / 10 / 12 / 14 / 16 valves - Valve types: single solenoid, double pilot valve, mid-position valve open, blocked, exhausted - with or without separate supply of auxiliary pilot air - 2 inputs per valve location - 2 additional inputs - 2 additional electrical outputs

25 SIEMENS PG 24VDC RUN ST OP L2-DP F USE BF VISB System summary Valve terminal type 03 Fig. 1/5: Example of a valve terminal type 03 with SF 50 - Component size 4 mm (MIDI), 7 mm (MAXI) - Valve types: single solenoid, double pilot valve, mid-position valve open, blocked, exhausted - max. 26 valve coils - max. 64 outputs, including coils - max. 56 inputs - max. 12 electrical modules

26 VISB System summary Valve terminals with analogue modules In many automation tasks, analogue signals are used in addition to digital inputs and outputs. There are special analogue modules available for these tasks for the programmable valve terminals with SB 50 or SF 50/DP-Slave. These modules can be used to process analogue input signals such as setpoint specifications and actual value response as well as analogue outputs for actuation of final control elements. These analogue modules come in the following versions: Universal (with either current or voltage interface) - current-loop interface ma, cut-off frequency 116 Hz - voltage-loop interface V, cut-off frequency 116 Hz Proportional (adapted to the actuation of proportional valves; ma, cut-off frequency 100 Hz). Using a programmable valve terminal with analogue processing offers the following advantages: - preliminary processing of analogue signals directly on the process - proportional valves can easily be connected - short cables, therefore less interference

27 SIEMENS PG 24VDC RUN STOP L2-DP FUSE BF VISB System summary Valve terminals with analogue I/Os Operation and monitoring Programming (inc. analogue I/Os) Analogue modules Analogue I/Os proportional module Analogue I/Os universal module I P Proportional valve (e.g. MPPE, MPYE) Actuator with variable contact pressure or feed (speed) PN Fig. 1/6: System summary: Valve terminals with analogue modules

28 VISB System summary Valve terminal with AS-i master The pneumatic final control elements are centrally controlled in many machines and units. Using the actuator sensor interface allows simple installation of the digital final control elements on the programmable valve terminal with SF 50 and SF 50/DP-Slave. Using a programmable valve terminal with AS-i master offers the following advantages: - No restriction in using the SB 50 in standalone operating mode. - Easy-to-install connection of pneumatic final control elements and sensors in systems distributed over wide areas. - Scope for expansion. - Pneumatic installation adapts to the mechanical construction of the machine or system. - Tubing is kept short. - Simple configuration of AS-i-network with the addressing device

29 SIEMEN S PG 24VDC RUN STOP L2-DP FUSE BF VISB System summary Valve terminal with AS-i master Operation and monitoring Programming + Configuring (inc. AS-i) AS-i slave valve terminal type 03 AS-i slave I/O module 4I AS-i slave I/O module 2I2O max. 31 AS-i-bus slaves AS-iaddressing device Fig. 1/7: System summary: Valve terminal with AS-i master

30 VISB System summary Valve terminal in slave operating mode A valve terminal with an SF 50/DP-Slave connected to the field bus as a slave controls the operating units of the machine itself and communicates with a higherorder master via the field bus. When using the programmable valve terminal as a slave, the mechanical construction of a machine or a system can be simulated by distributing the PLCs (programmable logic controllers). All standalone modules or function units then have their own control programs with which subranges can be controlled. The use of programmable valve terminals as slaves offers the following advantages: - No restriction in using the SF 50 in standalone operating mode. - Modular construction of the system/machine is possible. - Function modules of the system or machine can be linked together individually. - User-friendly partial commissioning possible. - High system availability due to standalone subranges. - Local operation and monitoring is possible

31 VISB System summary Higher-order master PLC PC/I-PC Programmable valve terminals Local operation and monitoring (SF 50 as active DP-slave) Slave (active) valve terminal type 03 Slave (active) valve terminal type 02 Slave (active) valve terminal type 03 Fig. 1/8: System summary: Valve terminal in slave operating mode

32 VISB System summary

33 VISB System limits and planning aspects 1.3 SYSTEM LIMITS AND PLANNING ASPECTS PN

34 VISB System limits and planning aspects Contents 1.3 SYSTEM LIMITS AND PLANNING ASPECTS - System limits Planning aspects of valve terminals type Planning aspect 1 Common power supply for all outputs Planning aspect 2 Separate power supply for single high-voltage output modules Planning aspect 3 Possible combinations of I/O modules

35 VISB System limits and planning aspects 1.3 SYSTEM LIMITS AND PLANNING ASPECTS System limits The theoretical structure of a complete system with programmable valve terminals can appear as follows: SF 50 as master with up to 56 local inputs and 64 local outputs 16 field bus slaves as intelligent slaves or decentralized peripherals (e.g. field bus valve terminals) or SB 50 or SF 50/DP-Slave with up to 56 local inputs and 64 local outputs AS-i master with up to 31 AS-i slaves (max. 128 inputs and 128 outputs) Analogue input and output modules (max. 12 channels) Operating and monitoring units

36 VISB System limits and planning aspects In practice, the number of units, or inputs and outputs, mentioned above is limited by the size of the user memory ( kbyte) and the cycle time (3...5 ms/1 k statements). The number of controllable inputs and outputs is always dependent on the complexity of the control problem and the use of special peripherals, like e.g. human machine interface (HMI), which require additional user memory space. Guideline value for a rapid "average" application: approx. 300 I/Os (including HMI units) PLEASE NOTE The number of controllable inputs and outputs is always dependent on the complexity of the control task and the use of special peripheral equipment. For any larger applications, the memory requirement should be estimated on an individual basis

37 VISB System limits and planning aspects Planning aspects of valve terminals type 03 This chapter contains some advice on the following planning aspects for modular valve terminals: Planning aspect 1 Common voltage supply to all outputs; i.e. the EMERGENCY STOP function for all outputs is implemented via pin 2 of the node/adapter block (valves and electrical modules). Planning aspect 2 Separate voltage supplies for individual highvoltage output modules; i.e. the auxiliary power supply in combination with the high-voltage outputs enables operation independent of the EMER- GENCY STOP function. Planning aspect 3 Possible combinations of I/O modules. Instructions for planning the sequence in which I/O modules can be fitted and combined on a valve terminal

38 VISB System limits and planning aspects Planning aspect 1 Common voltage supply for all outputs With this aspect, all the components of the valve terminal are supplied with 24 V via pins 1 and 2 of the node/adapter blocks. Pin 1: 24 V (+/ 25 %), max. 2.2 A operating voltage for the internal electronics of the node and all I/O modules. 24V DC power supply to all inputs/ sensors (PNP and NPN). Pin 2: 24 V (+/ 10 %), max. 10 A operating voltage for the valves and electrical outputs. Please note that when the valves are switched off (e.g. during EMERGENCY STOP) all the electrical outputs will also be switched off

39 VISB System limits and planning aspects Electrical outputs Outputs of valves All outputs can be disconnected during EMERGENCY STOP Power supply for node/adapter block (Pin 1+2) with EMERGENCY STOP Fig 1/9: Common voltage supply of all outputs (example) Advantages: Easy installation: simply involves connecting up a power supply unit. All outputs on the valve terminal are switched off at the hardware level when EMERGENCY STOP is activated (failsafe). Disadvantages: It is not possible to implement a different EMER- GENCY STOP process with which certain electrical outputs remain active

40 VISB System limits and planning aspects Planning aspect 2 Separate voltage supply for single high-voltage output modules This involves fitting at least one module for a 24 V auxiliary power supply to the left side of the node. This module provides electrical isolation of the I/Os. The high-voltage output modules are fitted to the left side of the auxiliary power supply unit and are only supplied from their 24 V power source. A mixture of negative and positive switching high-voltage output modules can be fitted. Voltage supply via the node: Pin 1: 24 V (+/ 25 %), max. 2.2 A operating voltage for the internal electronics of the node and all I/O modules. 24V DC power supply to all inputs/sensors (PNP and NPN). Pin 2: 24 V (+/ 10 %), max. 10 A operating voltage for the valves and only for the electrical outputs (PNP; 0.5 A). Please note that when the valves are switched off, (e.g. during EMERGENCY STOP) only these electrical outputs will be switched off (PNP; 0.5 A). Voltage supply via the auxiliary power supply: Terminal 2: 24 V (+/ 25 %), max. 25 A operating voltage for all high-voltage outputs (PNP or NPN, 2 A) mounted to the left of the relevant auxiliary power supply (power supply ends with last highvoltage output module). Note: Due to the auxiliary power supply, the operating voltage of the high-voltage outputs is entirely separate from pin 2 on the node. The "normal" output modules (PNP; 0.5 A) fitted to the left of the last high-voltage output module are again supplied via pin 2 on the node

41 VISB System limits and planning aspects Advantages: Additional 25 A per auxiliary supply are available for loads with high current consumption (e.g. hydraulic valves). Modules with four high-voltage outputs (HC-OUTPUT, each with optional 2 A PNP or NPN): these can be supplied with power to the left of the auxiliary power supply. Electric high-voltage outputs to the left of the auxiliary power supply can remain active during EMERGENCY STOP. Several auxiliary power supplies per terminal are possible. Disadvantages: An auxiliary power supply unit occupies the space of one I/O module (max. 12 modules). If the high-voltage outputs to the left of the auxiliary power supply are also to be switched off during EMERGENCY STOP, it may be necessary to provide additional appropriate installations. Electrical outputs Electrical outputs Outputs valves Valves/electr. outputs can be disconnected when EMERGENCY STOP is activated Power supply for auxiliary power supply (without EMER- GENCY STOP) High-voltage outputs (without 4 EMERGENCY STOP) V 0 V PE Power supply for node/adapter block (Pin 1+2) with EMERGENCY STOP Fig. 1/10: Separate voltage supply to all outputs (example)

42 VISB System limits and planning aspects Planning aspect 3 Possible combinations of I/O modules A wide range of universal and special I/O modules is available for modular valve terminals and these can be combined in virtually any sequence. Take due account during the planning stage, or when converting the terminals, of the permitted combinations. This rule always applies: maximum of 12 electrical modules per terminal. This point applies to individual electrical modules: Digital PNP modules (4I, 8I and 4O) in any combination and in any position (5). Digital NPN input modules (4I, 8I) in any combination and in any position (5). Analogue I/O modules (PROP; UNIVERSAL) in any combination and in any position (4). Auxiliary power supply units: always fitted to any position (3). Module with high voltage outputs (HC-OUTPUT, PNP or NPN) only to the left of an auxiliary power supply, there combined as required (2). The AS-i master must always be fitted at the far left (1)

43 VISB System limits and planning aspects Modules: 1 2* * max. 1 AS-i master-module Modules any* Modules any* Modules any Possible combinations * High-voltage power supply (grey connection) ends after the last HC output module 1 = AS-i master 4 = Analogue module 2 = HC output (PNP/NPN) 5 = I/O module 4I, 8I (PNP/NPN) or 4O PNP 3 = Auxiliary power supply 6 = Nodes Fig. 1/11: Possible combinations of the electrical I/O modules (example)

44 VISB System limits and planning aspects

45 VISB Installation 1.4 INSTALLATION PN

46 VISB Installation Contents 1.4 INSTALLATION General remarks Connecting up cable to plug/socket Connecting up operating voltage Operating voltage connection Cable length and wire cross section Connecting up electrical inputs Valve terminal type Valve terminal type Examples of input circuitry Connecting up electrical outputs Valve terminal type Valve terminal types Examples of output circuitry Duo cable Designation of inputs and outputs Valve terminal type Valve terminal type Field bus connector assembly FBS-SUB-9-GS Connection instructions for valve terminals Connector assembly S-SUB-15-GS Connector accessories

47 VISB Installation 1.4 INSTALLATION General remarks WARNING Before installation and maintenance work switch off the following: the compressed air supply. the operating voltage supply for the electronics (pin 1 of the operating voltage connection) th operating voltage supply for the outputs/valves (pin 2 of the operating voltage connection) By doing this you will avoid: Uncontrolled movements of loose tubing. Undesired movements of connected actuators. Undefined switching states of the electronics

48 VISB Installation Connecting the cable to the plug/socket CAUTION The position of pins on plugs/sockets differs! The connections of the input and output modules are fitted as sockets. The operating voltage connections are fitted as plugs. The Pin allocation can be found in the following chapter. Once you have selected suitable cables, connect them to the plugs/sockets as indicated in steps below. 1. Open the plug/socket as follows (refer to diagram): Mains socket: Insert the mains socket in the operating voltage connection of the valve terminal. Remove the housing from the socket. Remove the connection part from the socket, located in the operating voltage connection. Sensor connector/diagnosis socket: Remove the middle knurled nut

49 VISB Installation 2. Open the strain relief on the rear part of the housing. Finally, feed the cable through as shown in the diagram. Permitted cable external diameter Threaded Cable diameter connector Mains socket: PG9 PG mm mm Sensor connector: PG mm Cable Strain relief Housing Connection part Sensor Mains socket Fig. 12: Individual components of the connector 3. Remove 5 mm of insulation from the end of the cable. 4. Fit cable strands with cable end sleeve. 5. Connect up the ends of the cables. 6. Replace the connection part back on the housing of the plug/socket and screw both components together. Pull the cable back so that it is not looped inside the housing. 7. Tighten the strain relief

50 VISB Installation

51 VISB Installation Connecting the operating voltage WARNING For reliable electrical isolation of the operating voltage complying with VDE 0113, you will require an isolating transformer complying with DIN/VDE 0551 with a minimum 4 kv isolation resistance. CAUTION The operating voltage supply of the outputs or valves (pin 2) must be externally protected with a fuse maximum 10 A. By using an external fuse you will avoid functional damage to the valve terminal in the event of a short circuit. Before connecting the operating voltage, please note the following: Calculate the total consumption of the valve terminal under the worst operating conditions. In the descriptions of the individual valve terminals (Parts 2a and 2b) you will find formulae to help with the calculations. Then select a suitable power pack and cables with suitable cross sections. Avoid long distances between power supply and valve terminal. If necessay, calculate the distance using the data given below in this chapter. The general formula is: Consumption Cablecross-section Distance Pin 1 = 2.2 A Pin 2 = 10 A max. V B = 24 V 1.5 mm 2 8 m 2.5 mm 2 14 m

52 PG S I EM EN S RUN STOP L2- DP BF SIEMENS PG 24VDC RUN STOP L2-DP FUSE BF VISB Installation Operating voltage connection The connection for the 24 V operating voltages can be found on the left side of the baseplate in the valve terminals type 02 and on the bottom left edge of the control block in valve terminals type 03. Operating voltage connection Fig. 1/13: Operating voltage connection for valve terminals type 02 Operating voltage connection Fig. 1/14: Operating voltage connection for valve terminals type 03 The following components of the valve terminal are supplied separately with + 24 V direct voltage (DC) via this connection: Operating voltage for internal electronics, PLC and the inputs of the input modules (pin 1: DC + 24 V, Tolerance ± 25 %). Operating voltage for outputs of the valves and the outputs of the output modules (pin 2: DC + 24 V, Tolerance ± 10 %, external fuse with max. 10 A required)

53 VISB Installation Recommendation Connect the operating voltage of the outputs and valves via the EMERGENCY STOP circuit. The following diagram shows the pin allocation of the operating voltage connection. 24 V supply for electronics and inputs 24 V supply for valves / outputs PE Protective earth connection (leading contact) 3 0 V Fig. 1/15: Pin allocation operating voltage connection PLEASE NOTE Please note that when a common power supply is used for pin 1 (electronics and inputs) and pin 2 (outputs/valves) the lower tolerance of 10 % must be observed for both electric circuits. Check the 24 V operating voltage for the outputs while your system is operating. Ensure that the operating voltage of the outputs remains within the permitted tolerances, even during full-power operation. Recommendation Use a closed-loop power supply unit

54 VISB Installation Protective earthing The valve terminals are fitted with the following PE terminals: on the operating voltage connection (pin 4 incoming contact). Terminal type 03: on the left end plate (M4 thread). PLEASE NOTE Always connect the protective earth to pin 4 of the operating voltage connection. The protective earthing terminal on the left end plate of valve terminal type 03 can also be used. In this case, make sure that both protective conductors have the same potential and that no compensating currents are flowing. Connection example Diagram 1/16 shows the connection of a common 24 V power supply for pin 1 und pin 2. Please note that: the power supply of the outputs / valves must be protected against short circuit / overload with an external fuse, maximum 10 A, the power supply of the electronics / inputs must be protected against short circuit / overload with an external fuse, maximum 3.15 A, the overall tolerance 24 V DC ± 10 % must be observed, compensating currents must be prevented when both protective conductors are connected, e.g. by using cables with suitable cross-sections as potential compensation

55 VISB Installation Interconnecting cable for potential compensation of the earth connections AC 230 V 3.15 A DC 24 V ± 10 % External fuse 10 A EMERGENCY STOP Protective grounding terminal at pin 4 rated for 12 A Fig. 1/16: Connection example of a common 24 V power supply and both protective conductors Electrical outputs 2 A Valves (must be externally protected) Electrical inputs/sensors 24 V power supply for electronics without internal fuses Operating voltage connection for valve terminals Power supply Fig. 1/17: Internal distribution of the operating voltages

56 VISB Installation Cable length and cross section PLEASE NOTE The following information assumes a working knowledge of the information set out in the "Installation" chapters of this manual and is exclusively for the use of specialists trained in electronics technology. A load-dependent voltage drop occurs on all three cables in the operating voltage supply to a valve terminal. This can lead to the voltage on pin 1 or pin 2 of the operating voltage connection falling outside the permitted tolerance range. Recommendation: Avoid long distances between power supply and valve terminal. Determine the suitable cable length and crosssection using the following graphs or formulae. When doing this, note that - the graphs produce approximate values for the 1.5 und 2.5 mm 2 cross-sections - The formulae produce exact values for all cross-sections. PLEASE NOTE The following graphs and formulae assume that the cable cross sections of the operating voltage supply (pins 1, 2 and 3) are equal

57 VISB Installation Determined with the use a graph Proceed as follows: 1. Calculate the maximum current consumption for outputs/valves (I2). 2. Determine the lowest expected operating voltage (VBmin) of the power supply unit. Take account here of: - the load-dependency of the power supply unit. - the fluctuations of the primary supply voltage. 3. Read off the permitted cable length from the relevant table for your cross section. Example for 1.5 mm 2 : VBmin = 22.8 V, I2 = 2 A; Lmax = 25 m

58 VISB Installation +10% V 26,4 26 Current I2 in amps 10A 8A 6A 4A 25 3A VBmin in Volt A -10% 22 21,6 Cross section 1.5 mm m Cable length in metres Fig. 1/18: Permitted cable length of the mains cable with a cross section of 1.5 mm 2 V Current I2 in amps +10% 26,4 10A 8A 26 6A 25 4A VBmin in Volt A 2A -10% 22 21,6 Cross section 2.5 mm m Cable length in metres Fig. 1/19: Permitted cable length of the mains cable with a cross section of 2.5 mm

59 VISB Installation Determined with the use of formulae Proceed as follows: 1. Calculate the maximum current consumption of the inputs and electronics (I1) as well as of the outputs/valves (I2). 2. Determine the lowest expected operating voltage (VBmin) of the power supply unit. Take account here of: - the load-dependency of the power supply unit, - the fluctuation in primary mains voltage. 3. Enter the values in the corresponding formulae. This substitute circuit diagram and this example explain the relationship. Operating voltage supply Substitute circuit diagram VB Cable resistance (outgoing) AC DC VB 0 V 3.15 AT EMERGENCY STOP 10 AT I1 I2 I0 Pin 1 Pin 2 Pin 3 Valve RL1 VL1 RL2 VL2 UTERMINAL RI1 RI2 Distance (cable length) L RL0 VL2 + VL1 Cable resistance 0 V (return) Fig. 1/20: Cable length (L) and cable resistance (R L)

60 VISB Installation Formula for cable length: L (V Bmin V VALVTERM min ) A κ Cu 2 I 2 + I 1 Where: VTERMINAL = 24 V ± 10 %, minimum: VVALVTERMmin 21.6 V VBmin = minimum operating voltage supply (in power supply unit) Current I1 = Current for electronics and inputs Current I2 = Current for outputs and valves A = Cable cross section (uniform e.g. 1.5 mm 2 ) k = Conductivity of the cables (uniform e.g. κ Cu = 56 m mm 2 Ω ) Example: = 1 A = 5 A = 24 V = 21.6 V m I1 I2 VB VTERMINAL min kcu = 56 mm 2 Ω Results: L 18 m for A = 1.5 mm 2 L 30 m for A = 2.5 mm

61 VISB Installation Empty page for file transfer

62 VISB Installation Connection of electrical inputs WARNING Before installation and maintenance work switch off the following: the compressed air supply the operating voltage supply for the electronics (pin 1) the operating voltage supply for the outputs/valves (pin 2). By doing this you will avoid: uncontrolled movements of loose tubing. undesired movements of connected actuators. undefined switching states of the electronics. The input modules of the valve terminal have various numbers of inputs available for use. All inputs have a positive logic (PNP inputs). Valve terminal type 02: 2 inputs per valve location together with 2 inputs per valve terminal Valve terminal type 03: Input module with 4 or 8 inputs max. 56 inputs per valve terminal

63 VISB Installation Valve terminal type 02 Input socket Upper row Pin allocation of the sockets 24 V (fused) 1 2 Ix 4 3 Ix 0 V Internal pin connections Explanation Bridge between pin 2 and pin 4 Lower row 24 V (fused) Ix Ix 0 V Connection between pin 2/4 of the upper row and pin 2 of the lower row Advantage: Two inputs can be connected to the lower row. This results in: - cable reduction - connection of changeover contact or changeover switch is possible Fig. 1/21: Pin allocation of inputs in valve terminals type 02 WARNING If the lower socket is used for two input cables, then the upper socket must remain unused and protected against dirt with a cover. PLEASE NOTE If the lower sockets are used for two inputs, we recommend that the DUO cable and the accompanying extension cable are used. A description is given further in this chapter

64 VISB Installation Valve terminal type 03 The input modules of the valve terminal type 03 have four or eight inputs available for use. 4-input module 8-input module Sockets, each with one digital input Green LED Sockets, each with two digital inputs One green LED on each digital input Connection preferably with DUO cable Fig. 1/22: Digital input modules (4/8 outputs) for valve terminal type 03 4-pin allocation 0 Free 2 0 V V 1 4 similar assignment Free 0 V V Input Ix Input Ix+3 7 Input Ix V Input Ix V 8-pin allocation similar assignment V Input Ix 0 V Input Ix+6 Fig. 1/23: Pin allocation of the input modules for valve terminal type

65 VISB Installation Examples of input circuitry Internal structure 24 V ± 25 % Pin 2 and pin 4 are internally connected in type 02 PLC Ix Logicrecognition Ix Green LED Ix 0 V 3 Examples of circuitry Pin allocation of type 03 Positive switching Positive switching Three wire sensor Two wire sensor Contact Fig. 1/24: Input module terminal type 02, upper row 4-input module, terminals type

66 VISB Installation Internal structure PLC Ix+1 24 V ± 25 % PLC Ix Logicrecognition Ix+1 Logicrecognition Ix Green LED Ix+1 Green LED Ix 0 V 3 Examples of circuitry Pin allocation of type 03 Duo cable Sensor 2 (Ix+1) Sensor 1 (Ix) Fig. 1/25: Input module terminal type 02, lower row 8-input module, terminals type

67 VISB Installation Connection of electrical outputs WARNING Before installation and maintenance work switch off the following: the compressed air supply. the operating voltage supply for the electronics (pin 1) the operating voltage supply for the outputs/valves (pin 2) By doing this you will avoid: uncontrolled movements of loose tubing. undesired movements of connected actuators. undefined switching states of the electronics. The valve terminal has various numbers of outputs available for use. All outputs have a positive logic (PNP outputs). Valve terminal type 02 2 additional electrical outputs per valve terminal. Relay plates with one or two relay contacts can be fitted on the valve locations. They provide floating contacts. Valve terminal type 03 Output modules with 4 outputs max. 64 outputs per valve terminal, inc. coils, max. 10 A total current

68 VISB Installation Valve terminal type 02 Free O Free 0 V Free O Free 0 V Fig. 1/26: Pin allocation of additional outputs in valve terminals type 02 The additional outputs of the valve terminal type 02 can be used for the actuation of seperately mounted valves, protection devices for motors or signal bulbs. Technical data: 24 V DC, 0.5 A Short circuit resistant WARNING The outputs for the valves are set for the valve solenoid coils. They may only be used as specified

69 VISB Installation Valve terminal type 03 The additional electrical outputs for valve terminal type 03 are contained in modules that are mounted on the left of the control block. 0 1 Yellow LED per output (Status) Red LED per output (short circuit) 2 3 Fig. 1/27: Digital 4-output module 4-pin allocation 0 Free Free V Output Ox 1 2 similar assignment 3 Free Free 1 4 Fig. 1/28: Pin allocation of 4-output module for valve terminals type V Output Ox

70 VISB Installation Examples of output circuitry Internal structure 24 V ± 10 % Free Free 1 2 PLC Ox Output driver 4 Diagnosis - Output status - Overload 0 V Red LED Yellow LED 3 External structure Pin allocation of type 03 NOT ALLOWED + 24 V Fig. 1/29: Electrical outputs, valve terminal type 02, 4-output module, valve terminals type

71 VISB Installation DUO cable The DUO cable offers a simple connection for sensors with assignments for two inputs. The plugs on the sensor side are intended for M8. There are three different pairs of plug design. 0.6 m B A 0.5 m Duo cable C Fastening by means of screw Fastening by means of clamping strap Identification plate Y-distributor Socket Extension cable 2.5 m 5.0 m Plug M12 x 1 Can be screwed into valve terminal with sockets Fig. 1/30: DUO cable and extension cable for simple connection of sensors

72 VISB Installation + (24 V) 1 - (0 V) 3 Signal x 4 Signal x (24 V) 1 - (0 V) 2 Signal x 3 + (24 V) 1 - (0 V) 2 Signal x+1 Fig. 1/31: Pin allocation DUO cable The DUO cable is available in three variants, see table below. The cables are always 500 mm and 600 mm long, sufficient for cylinder switches mounted up to one metre apart. The connections for the sensors are M8 type. The cables are joined in a Y piece and led through a screw-on extension cable to the valve terminal. The Y-distributor can be fastened at any point with a screw or a clamping strap. Name Type Explanation Duo cable KM12-DUO-M8-GDGD Y-piece with M8-sockets, 2 x straight Duo cable KM12-DUO-M8-GDWD Y-piece with M8-sockets, 1 x straight 1 x angled Duo cable KM12-DUO-M8-WDWD Y-piece with M8-sockets, 2 x angled Connecting cable KM12-M12-GSGD-2.5 extension lead with M12 plug/socket, 2.5 m Connecting cable KM12-M12-GSGD-5.0 extension lead with M12 plug/socket, 5.0 m Fig. 1/32: Order codes for DUO cable and extension cable

73 VISB Installation Designation of inputs and outputs For better monitoring during commissioning and for maintenance work the inputs and outputs should be given designations which will ensure clear identification in the circuit diagram or in the program. Valve terminal type (20 pieces per frame) (10 pieces) Fig. 1/33: Holder for identification plate of I/O connections Valve terminal type (64 pieces per frame) (20 pieces per frame) (5 units in bag) Fig. 1/34: Holder for identification plate of electrical inputs and outputs

74 VISB Installation Field bus connector assembly FBS-SUB-9-GS-9, PNo Seal (7): insert in lower cover (9) and upper cover (6). 2. PCB (8): insert into the guide of the lower cover (9). Fix the PCB with countersunk screw (10) to the lower cover. 3. Screw the lower part of the PG compression glands (5) in the upper cover (6) to the limit stop. Thread cable through the union nut (1), clamping ring (2) and cone seal (3). 4. Feed the cable through the upper cover. 5. Remove the insulation from the bus cable as shown in figure 1/32 and connect to the terminal block. 6. Push upper cover (6) over the PCB and connect with the lower cover. Screw the cone seal, clamping ring and union nut to the lower part of the PG threaded connector. Fig. 1/35: Individual components of the plug 7. Insert screws (4) in the connector housing to the limit stop and then screw in under pressure with a screwdriver until they protrude from the lower cover by mm. Sealing plug PLEASE NOTE Only use the cable that is permitted for the PROFIBUS-DP. Fig. 1/36: Close plug

75 VISB Installation WARNING - The terminating resistors must be switched on at the segment start and segment end, (Fig.1/39). - The terminating resistors must not be switched on with looped-through bus cable, (Fig. 1/38). - The cable ends at the segment start and the segment end must be sealed with the sealing plug supplied, (Fig. 1/36). 10 The braided screen must be fastened on directly under the cable clamps 6 5 Fig. 1/37: Preparing the cable Bus cable connector with "looped through" bus cable, switch position OFF (terminating resistor is not switched on). Bus cable connector at segment start and segment end, switch position ON (terminating resistor is switched on). A B AB AB AB Fig. 1/38: Terminating resistor OFF Fig. 1/39: Terminating resistor ON

76 VISB Installation Connection instructions for valve terminals FESTO valve terminals with field bus nodes for the PROFIBUS-DP (FB9) can be advantageously used as a Slave in a system where a valve terminal with control block SF 50 is the Master station. The field bus nodes FB9 have a 4-pin rounded connector for the connection to the field bus. Connect the Slave station to the Master station as shown below. Master station Meaning Slave station AB Connection A Data line A Pin 3 (S-) Connection B Data line B Pin 1 (S+) Braided screen Screening Pin 4 Fig. 1/40: SF 50 connection with FB

77 VISB Installation Connector assembly S-SUB-15-GS-9, PNo , Seal (7): insert in lower cover (9) and upper cover (6) 2. Screw the lower part of the PG compression glands (5) in the upper cover (6) to the limit stop. Close unassigned cable ends with sealing plug (8). 3. Thread cable through the union nut (1), clamping ring (2) and cone seal (3). 4. Feed the cable through the upper cover. 5. Fasten the sub-d connector (11) to the lower cover (9) with countersunk screws (10). 2 models: - Solder connection - Crimp connection Fig. 1/41: Components of the plug 6. Remove a part of the insulation from the cable. Fit individual strands with crimp contacts and contact pins according to the contact allocations into the sub-d connector or remove a part of the insulation from the cable. Solder individual strands according the contact allocations into the sub-d-connector 7. Connect upper cover (6) with the lower cover. Screw the cone seal, clamping ring and union nut to the lower part of the PG threaded connector. 8. Insert screws (4) in the connector housing to the limit stop and then screw in under pressure with a screwdriver until they protrude from the lower cover by mm

78 VISB Installation Contact allocations on the 15-pin sub-d connector are valid for all SB / SF 50 variants: Contact number Contact description 1 Screening 2 TTY IN- (grey-blue) 6 TTY OUT+ (brown) 7 TTY OUT- (yellow) 8 Screening 9 TTY IN+ (white) View in direction of arrow Fig. 1/42: Contact allocations for SB/SF 50 An additional clamping ring is included in the kit (item 2 in Fig. 1/41). This can be used with cables of different external diameters. - without additional clamping ring mm - with additional clamping ring mm

79 VISB Installation Connector accessories Designation Straight mains socket, PG 9 (for 1.5 mm 2 ) Straight mains socket, PG 13.5 (for 2.5 mm 2 ) Angled mains socket, PG 9 (for 1.5 mm 2 ) Type name NTSD-GD-9 NTSD-GD-9 NTSD-GD-9 Sensor connector SEA-GS-7 Field bus connector for SINEC L2-DP (9-pin), FBS-SUB-9-GS-9 Connection of L1 / B&B (15-pin), with crimp connection with solder connection Cover plate for sub-d-connection (complies with IP 65, when connector is not inserted) S-SUB-15-GS-9 S-SUB-15-GS-9-L AK-SUB-9,

80 VISB Installation

81 Programmable valve terminals with control block SB 50 / SF 50 Part 2a: Valve terminal type 02 SIEMENS RUN BF STOP PG L2-DP PN

82 PN is included in: Manual

83 VISB - 50 Chapter summary This manual consists of various parts which can be put together depending on the equipment fitted on the valve terminal. Part 1 Basic principles of installation contains information which is not dependent on the type of valve terminal or on the node selected. Part 2a Valve terminal type 02 System description of valve terminal type 02, contains all information specifically for this type of terminal. Part 2b Valve terminal type 03 System description of valve terminal type 03, contains all information specifically for this type of terminal. Part 3 System description of the SB 50 contains all PLC information irrespective of the type of valve terminal. Part 4 Part 5 Part 6 System description for SF 50 as Master contains additional information that is required when using the PROFIBUS-DP. System description for SF 50 as DP-Slave contains additional information that is required when using the SF 50/DP-Slave (SL 50). Appendix contains additional information concerning command sets, abbreviations, accessories, literature, etc. PN a-I

84 VISB - 50 Notes 2a-II 9706

85 VISB Table of contents TABLE OF CONTENTS 2.1 COMPONENTS - Structure of the valve terminal...2a-3 - Function summary...2a-6 - Valves...2a-7 - Connecting the auxiliary pilot air...2a-8 - Manual override...2a-9 - Designs of manual override...2a-10 - Impairment of function...2a-12 - Locking the manual override...2a-12 - Converting the manual override...2a FITTING - Fitting the valve terminal...2a-17 - Installing the pneumatic components...2a-18 - Connecting the valves...2a-21 - Installing the electronic components...2a ELECTRICAL CONNECTIONS - Power supply voltage...2a-27 - Calculating the current consumption...2a-28 - Operating voltage connection...2a-29 - Protective earthing...2a-31 - Valves...2a-32 - Outputs of the valve locations...2a-33 - Additional outputs...2a-34 - Overload at the additional output...2a-35 - Relay boards...2a-36 - Electrical inputs...2a-37 PN a-III

86 VISB Table of contents 2.4 ADDRESSING - Designating the inputs/outputs...2a-41 - Identification...2a TECHNICAL SPECIFICATIONS 2a-IV 9706

87 VISB Components 2.1 COMPONENTS PN a-1

88 VISB Components Contents 2.1 COMPONENTS - Structure of the valve terminal...2a-3 - Function summary...2a-6 - Valves...2a-7 - Connecting the auxiliary pilot air...2a-8 - Manual override...2a-9 - Designs of manual override...2a-10 - Impairment of function...2a-12 - Locking the manual override...2a-12 - Converting the manual override...2a-13 2a

89 VISB Components 2.1 COMPONENTS OF VALVE TERMINAL TYPE 02 Structure of the valve terminal The programmable valve sensor terminal type 02 consists of the following components: 2 SI EME NS RUN BF STOP PG 1 L2 -DP 3 Figure Components 1 Control block SB 50 or SF 50 2 Basic unit for valve sensor terminal, consisting of: valve sensor coupling unit (upper part) sub-base (lower part) 3 Valve locations for: double solenoid valves solenoid mid-position valves single solenoid valves relay boards blanking plates Fig. 2/1: Components on the programmable valve sensor terminal type a-3

90 VISB Components The following operating and display elements are to be found on the components of the programmable valve sensor terminal: SI EMENS RUN STOP PG BF 15 7 L2-DP Connections for additional outputs 12 Valve location inscription field 2 Common fuse for inputs (per solenoid valve coil) 3 Inscription field for station number 13 Yellow LED (per valve solenoid coil) 4 Red LED BUS FAULT Work connections (per valve) 5 Green LED RUN 14 Common tubing connections 6 Operating voltage connection (left and right-hand sides) 7 Red LED STOP 15 Inscription field for inputs and 8 PG interface additional outputs (per valve location) 9 Field bus interface (only with SF 50) 16 Yellow or green LED 10 Type plate for control block (per additional output or per input) 11 Type plate for basic unit 17 Connections for inputs (e.g. for sensors) Fig. 2/2: Operating and display elements 2a

91 VISB Components The diagrams below show the composition of the identification plates. Valve sensor terminal basic unit, (example: underneath the control block) Control block SF 50, (example: at the side of the control block) Type designation of basic unit Typ IIFB-02-1/8-6 TN18504 max.bar 10 max.psi 145 Serie BB V DC Part number of basic unit Max. operating pressure in bar and PSI Series number and permitted operating voltage Fig. 2/3: Example of a type plate: valve sensor terminal basic unit Typ: SF TN Serie: Cxx 0794 HW: xx.xx.xx SW: xx.xx.xx Produktions-Nr.: xxxxxxxxxxx Exclusive Siemens product for FESTO Made in Germany Type designation of control block Part number SF Series number Hardware status Software status Production number Fig. 2/4: Example of a type plate: control block SF a-5

92 PG SI EME NS RUN STOP L2 -DP BF VISB Components Function summary The heart of the programmable valve sensor terminal is the control block SB 50. This contains a PLC with the function scope of the SIMATIC mini controllers and the electronic components which are required in order to control a valve sensor terminal independently. In this way you can solve your automation tasks on the spot independently, and thereby relieve the higher-order PLC, if necessary. The user programs for the programmable valve sensor terminal are created on a programmer or a PC with the aid of the programming software SIMATIC STEP 5. The programming languages LDR, CSF and STL can be used. The programs are loaded via the diagnostic interface into the programmable valve sensor terminal. Voltage supply If necessary field bus PROFIBUS-DP (only with SF 50) Fig. 2/5: Function summary SB/SF 50 2a

93 VISB Components Valves To make valve terminal type 02 suitable for the functions required, it can be fitted with a large number of different solenoid valves. The following solenoid valves can be used: Switching symbol Type designation Explanation MVH-5-1/8-B-VI MVH-5-1/4-B-VI MVH-5-1/8-S-B-VI MVH-5-1/4-S-B-VI Poppet valve, unilaterally-operated, 5/2-way, spring reset MVH-5-1/8-B-VI MVH-5-1/4-B-VI MVH-5-1/8-L-S-B-VI MVH-5-1/4-L-S-B-VI JMVH-5-1/8-B-VI JMVH-5-1/4-B-VI JMVH-5-1/8-S-B-VI JMVH-5-1/4-S-B-VI MVH-5/3B-1/8-B-VI MVH-5/3B-1/4-B-VI MVH-5/3B-1/8-S-B-VI MVH-5/3B-1/4-S-B-VI MVH-5/3E-1/8-B-VI MVH-5/3E-1/4-B-VI MVH-5/3E-1/8-S-B-VI MVH-5/3E-1/4-S-B-VI MVH-5/3G-1/8-B-VI MVH-5/3G-1/4-B-VI MVH-5/3G-1/8-S-B-VI MVH-5/3G-1/4-S-B-VI IRP1-02-1/8 IRP2-02-1/8 IRP1-02-1/4 IRP2-02-1/4 Fig. 2/6: Types of solenoid valves and relay boards Spool valve, unilaterally-operated, 5/2-way, pneumatic spring reset Spool valve, bilaterally-operated, 5/2-way, without reset Spool valve, bilaterally-operated, 5/3-way, mid-position pressurized, spring reset Spool valve, bilaterally-operated, 5/3-way, mid-position exhausted, spring reset Spool valve, bilaterally-operated, 5/3-way, mid-position blocked, spring reset Relay board with one or two floating contacts for controlling low-current consuming devices All valves and relay boards are available in sizes 1/8" and 1/4". The S-types of valves have a separate connection for the auxiliary pilot air a-7

94 VISB Components Connecting the auxiliary pilot air The solenoid valves used are pneumatic pilot actuated valves. The energy required is normally taken from the main air supply, port 1. This connection is already made internally in the valve and does not have to be made by the user. The correct function of all valves is guaranteed providing the supply pressure is in the range bar. If the pressure is lower, not all the valves will respond. For operation at lower pressures down to vacuum, the auxiliary pilot air must be supplied separately. Valves with "S" in the type designation are fitted with a separate connection for the auxiliary pilot air (port 12 or 14). The connection is on each valve above the connections for the work lines to the cylinder. The valves must be connected to each other externally with tubing. 2 connections with double and mid-position valves 1 connection with single valves Fig. 2/7: Connection for auxiliary pilot air 2a

95 VISB Components Manual override WARNING The manual override influences the effect of the electrical signal. If a signal is present, the valve cannot be switched over by the manual override. If the manual override is operated, the electrical signal has no effect. The manual override is used mainly during commissioning of the pneumatic system, for checking the functioning and effectiveness of the valve or the valve-cylinder combination. When the manual override is operated, the valve can be switched without an electrical signal. Only the compressed air supply need be switched on. Pilot valve Manual override Basic valve Double solenoid valve Mid-position valve Manual override Pilot valve Single solenoid valve Fig. 2/8: Position of manual overrides a-9

96 VISB Components Designs of manual override The manual override has been designed to be used as follows: Manual override designs Manual override with automatic reset. Basic setting as at factory Manual override with stop Conversion of manual override necessary (see Appendix) Method of operation Manual override is reset after operation by spring presssure. Two variants: See above Manual override can be locked during operation Fig. 2/9: Designs of manual override Checking Switch on the compressed air supply. Check the functioning and effectiveness of each individual valve as follows. If the function is impaired see fig. 2/12. Operating the manual override Reaction of valve or of processor Press the plunger of the manual overrride as far as it will go. switches Hold plunger of manual override pressed down. Remove the screw driver. The spring resets the manual override in the basic position. remains in switched position returns to basic position Fig. 2/10: Manual override with automatic reset 2a

97 VISB Components Operating the manual override Insert the screwdriver into the groove of the plunger. Press the plunger of the manual override as far as it will go and turn it to the right. Hold plunger pressed down. Insert the screwdriver into the groove of the plunger. Turn the plunger of the manual override under pressure to the left and remove the screwdriver. Reaction of valve or of processor returns to switch position remains in switch position returns to basic setting Fig. 2/11: Manual override with stop PLEASE NOTE When the valves have been tested, switch the compressed air supply off again. Set the manual override at the basic position again. You thereby prevent uncontrolled movements a-11

98 VISB Components Impairment of function When the compressed air supply is switched on or when the individual valves have been tested, the following is known about the operating status of the pneumatic system: Operating status of pneumatic system Air comes out: of common tubing connection of working connections Valve or pneumatic system does not react: as expected Valve position Basic position Switch position Switch position Error treatment when compressed air is switched off Check the seal or tubing fitting Check the routing of the cables Check the tubing to the auxiliary pilot air does not react Switch position Fig. 2/12: Operating status of pneumatic system Check operating pressure Check auxiliary pilot air If necessary, call service Locking the manual override In systems where security is of great importance, the manual override may be locked against unauthorized use. Conversion is required before the manual override can be locked. 2a

99 VISB Components Converting the manual override The valves for the programmable valve terminal type 02 are fitted as standard with manual override with automatic reset. If the manual override is to be fitted with a stop or if it is to be made inaccessible, conversion is necessary. WARNING Before converting the manual override: Switch off the power supply Switch off the compressed air supply Carry out the following steps in the sequence stated. Remove the valve from the sub-base. Pilot valve Basic valve Loosen screws Fig. 2/13: Dismantling the valve Carefully unscrew the two Philips screws in the cover of the pilot valve, but do not pull them out. Remove the pilot valve together with the fastening screws from the base valve a-13

100 VISB Components Hold the pilot valve firmly at the cover and bottom. Pull down the black cover plate over the manual override. At the same time pay attention to the aluminium plate underneath. Remove the aluminium plate. The plunger of the manual override becomes visible. Conversion (see below) Manual override Conversion with stop Push the black cover of the manual override over the plunger so that the latter is still visible. Press the plunger of the manual override gently down with a screwdriver. with lock Push the black cover of the manual override over the plunger of the manual override so that the latter is covered. Press the plunger of the manual override gently down with a screwdriver. Fig. 2/14: Converting the manual override Place the pilot valve with screws onto the base valve so that the manual override faces the front. Tighten the screws. Place the valve on the sub-base and fasten with the Philips screws. 2a

101 VISB Fitting 2.2 FITTING PN a-15

102 VISB Fitting Contents 2.2 FITTING - Fitting the valve terminal...2a-17 - Installing the pneumatic components...2a-18 - Connecting the valves...2a-21 - Installing the electronic components...2a-24 2a

103 L2 -DP BF VISB Fitting 2.2 FITTING Fitting the valve terminal Before fitting the programmable valve terminal, ensure that there is sufficient space to the left/right of the sub-base for connecting the tubing and, if necessary, the silencers. There are two through holes on both the left-hand and right-hand edges for fastening the programmable valve terminal. SI EME NS RUN STOP PG L1 6.8 mm for screws M6 60 L 1 for 1/4" 32 mm L 1 for 1/8" 27.5 mm L2 Programmable valve terminal Distance between holes [mm] L 2 for 1/4" L 2 for 1/8" IISF-02-1/4(1/8) IISF-02-1/4(1/8) IISF-02-1/4(1/8) IISF-02-1/4(1/8) IISF-02-1/4(1/8) IISF-02-1/4(1/8) Fig. 2/15: Fastening holes a-17

104 VISB Fitting Installing the pneumatic components Before undertaking installation or maintenance work: Switch off the operating voltage for the electronic components and inputs. Switch off the operating voltage for the outputs. Switch off the compressed air supply. Laying the tubing PLEASE NOTE If angled connectors or multiple distributors are used, the air flow will usually be reduced. Fit a suitable seal under each screw connector or silencer. Basic principles Connecting - Push the tubing as far as it will go into or over the screw connector. - Pull the locking ring over the tubing connection or tighten the locking screw. - For reasons of clarity, group the tubing together with: - tube straps or - multiple hose holders. Disconnecting - Loosen the locking screw or the locking ring on the screw connector. - Remove the tubing. - If required, replace the screw connector with a blanking plug. 2a

105 L2 -DP BF VISB Fitting Preparing the sub-base There are connections for common tubing on both sides of the sub-base. This enables common tubing to be fitted on the left or the right depending on requirements. To increase the air flow, we recommend that the compressed air and/or exhaust air be connected on both sides in the following cases: on programmable valve terminals with more than 10 valves (rated supply pressure 6 bar) with large volume actuators Prepare the connections as shown in the table below. SIEMENS RUN STOP PG 5 connections for common tubing (lupolen plugs) 5 connections for common tubing (blanking plugs) Connecting the common tubing Left Right Both sides Fig. 2/16: Assigning the sub-base Procedure Remove all lupolen plugs Remove all lupolen plugs Remove all blanking plugs and fit on left Remove all lupolen and blanking plugs a-19

106 VISB Fitting Connecting the sub-base Fit the screw connectors or silencers with appropriate seals as shown in the table below. Then connect the tubing. Pilot exhaust Pilot exhaust Exhaust 5/3 3/5 Exhaust 1 Compressed air Common tubing Connection code (ISO 5599) Connection size (ISO 228) Connection Compressed air 1 G1/2 (G3/8) Screw connector Exhaust 5/3 3/5 Pilot exhaust Specifications in brackets apply to valve terminal size 1/8" Fig. 2/17: Assigning the sub-base G1/2 (G3/8) Screw connector (with ducted G1/8 (G1/8) exhaust) or silencers 2a

107 VISB Fitting Connecting the valves Cover vacant or unused valve locations with blanking plates. If one of the fitted valves is not used, connections 2 and 4 as well as 14 and, if necessary, 12 must be fitted with blanking plugs. PLEASE NOTE Use seals of aluminium for the working connections 2 and 4. Remove the lupolen plugs and fit the screw connectors with appropriate seals in accordance with the following tables: Fig. 4/5: Assignment of single solenoid valve Fig. 4/6: Assignment of double solenoid valve and mid-position valve Then connect the tubing a-21

108 VISB Fitting Single solenoid valve (5/2-way) Auxiliary pilot air - only S-valves Working air Pneumatic spring - only L-S-valves Tubing Connection code (ISO 5599) Working air 2 Auxiliary pilot air Pneumatic spring Connection Connection size (ISO 228) G1/4 (G1/8) Screw connector or multi-distributor 4 14 G1/8 (G1/8) Only S-valve 12 G1/8 (G1/8) Only L-S-valve Fig. 2/18: Connections on the solenoid valve 2a

109 VISB Fitting Double solenoid valve (5/2-way) and solenoid mid-position valve (5/3-way) Auxiliary pilot air - only S-valve Working air Auxiliary pilot air - only S-valve Tubing Connection code (ISO 5599) Working air 2 Auxiliary pilot air Connection Connection size (ISO 228) G1/4 (G1/8) Screw connector or multi-distributor G1/8 (G1/8) Only S-valve Fig. 2/19: Connections on double solenoid and mid-position valves a-23

110 VISB Fitting Installing the electronic components No settings must be made on the control blocks SB 50 and SF 50. WARNING Before installation or maintenance work is carried out: Switch off the operating voltage to the electronic components and inputs Switch off the operating voltage to the outputs Switch off the compressed air supply Part 1, chapter 1.3 of this manual describes the power supply, and the connection of the cables and contains further suggestions for fault-free commissioning of the programmable valve sensor terminal. 2a

111 VISB Electrical connections 2.3 ELECTRICAL CONNECTIONS PN a-25

112 VISB Electrical connections Contents 2.3 ELECTRICAL CONNECTIONS - Supply voltage...2a-27 - Calculating the current consumption...2a-28 - Operating voltage connection...2a-29 - Protective earthing...2a-31 - Valves...2a-32 - Outputs of the valve locations...2a-33 - Additional outputs...2a-34 - Overload at the additional output...2a-35 - Relay boards...2a-36 - Electrical inputs...2a-37 2a

113 VISB Electrical connections 2.3 ELECTRICAL CONNECTIONS Supply voltage WARNING An isolating transformer as per DIN/VDE 0551 with at least 4 kv isolation resistance is required in order that the operating voltages can be separated as per VDE CAUTION The power supply to the outputs/valves (Pin 2) must be fused externally with max. 10 A. The external fuse prevents damage to the terminal functions in the case of a short circuit. Please observe the following before connecting the operating voltage: Calculate the complete current consumption according to the following table and select both a suitable power unit and cable cross section. Avoid long distances between the power unit and the terminal. Calculate also the permitted distance according to part 1 of this manual, INSTALLA- TION. The following rule applies: Consumption Pin 1 = 2.2 A Pin 2 = 10 A max. V Op = 24 V Cablecross Distance section 1.5 mm 2 8 m 2.5 mm 2 14 m a-27

114 VISB Electrical connections Calculating the current consumption The following table permits calculation of the total current consumption of the valve terminal. Current consumption of electronic comp. node and inputs (Pin 1, 24 V ± 25 %) Node A Number of simultaneously assigned sensor inputs x A + Σ A Supply to sensors (see Manufacturer specifications) x A + Σ A Current consumption of electronic components node and inputs max. 2.2 A = Σ A Σ A Current consumption of valves and outputs (Pin 2, 24 V ± 10 %) Number of valve coils (sim. under power) x A Number of relay boards (sim. under power) x A + + Σ Σ A A Additional output 0 (max. 0.5 A) Additional output 1 (max. 0.5 A) + + A A Current consumption of outputs (Pin 2) max. 10 A = Σ A + Σ A Total current consumption valve terminal type 02 = Σ A Fig. 2/20: Calculating the current consumption of the valve terminal Select a suitable power unit and observe the remarks in part 1, chapter 3.1, of this manual. 2a

115 STOP VISB Electrical connections Operating voltage connection The connection for the operating voltage is on the lefthand side of the base plate. Fuse for sensor supply Power socket SIEMENS RUN BF PG L2-DP Operating voltage connection Fig. 2/21: Position of operating voltage connection The following components on the valve terminal are supplied separately with + 24 V DC via this connection: the internal electronic components, PLC and the inputs (Pin 1: + 24 V DC, tolerance ± 25 %). the valves and special outputs (Pin 2: + 24 V DC, tolerance ± 10 %, external fuse with max. 10 A required). Recommendation Connect the operating voltage for the outputs and valves via the EMERGENCY STOP circuit a-29

116 VISB Electrical connections The diagram below shows the pin assignment of the operating voltage connection. 24 V supply electronic components and inputs 24 V supply for valves/outputs 1 PE Connector (incoming contact) V Fig. 2/22: Pin assignment of operating voltage connection PLEASE NOTE With a common supply voltage for pin 1 (electronic components and inputs) and pin 2 (outputs/valves) the lower tolerance of ± 10 % for both circuits must be observed. Check the 24 V operating voltage of the outputs whilst the system is in operation. Ensure that the operating voltage of the outputs lies within the permitted tolerances even during full operation. Recommendation Use a closed-loop power unit. 2a

117 VISB Electrical connections Protective earthing The valve terminal has a protective earth connection: on the operating voltage connection (pin 4 incoming contact). PLEASE NOTE Always connect the protective conductor to pin 4 of the operating voltage connection a-31

118 VISB Electrical connections Valves The switching status of the valves is indicated by a yellow LED per valve coil. The LEDs for valve side 14 are situated on the lower edge of the sensor coupling unit. The LEDs for valve side 12 are in the adapter plate which is fitted between the basic unit and the valve. SIEMENS LED for valve side 14 RUN BF STOP PG L2-DP LED for valve side 12 (double solenoid and mid-pos. valves) LED Switch position valve solenoid coil Meaning Yellow out Basic position Logic 0 (no signal) Yellow alight Switch position or Basic position Logic 1 (signal) Logic 1 but operating voltage of valves outside tolerance range ( V) or compressed air supply not correct or pilot exhaust blocked Fig. 2/23: LEDs for the valve coils 2a

119 VISB Electrical connections Outputs of the valve locations The outputs for the valves are matched to the current consumption and the mechanical connection of the valve coils. They can only be used in the form intended. Another current consuming device must not be connected. The following applies: The outputs are not short-circuit resistant. Two outputs per valve location. With unilaterally-operated valves, the output with the even bit number is used. The other output cannot be used for other purposes. Relay with one or two floating contacts are available to allow electrical load devices to be connected to one of the valve positions. See also below in this chapter a-33

120 VISB Electrical connections Additional outputs Two additional outputs (O0.00 and O0.01) are available for user applications on the valve sensor coupling unit of the programmable valve terminal. These are transistor outputs with positive logic (PNP outputs). PNP outputs (0.5 A/24 V) S IEMENS RUN BF STOP PG L2-DP Fig. 2/24: Position of additional outputs LED (yellow) for status display free O free 0 V Yellow LED for additional outputs free O free 0 V Fig. 2/25: Pin assignment of additional outputs Each of these outputs has a yellow LED for the status display. 2a

121 VISB Electrical connections Short circuit / overload at the additional output If there is a short circuit or overload: the relevant output will be switched off I7.2 or I7.3 of the diagnostic byte will be set. In order to reactivate the output, you must first set it at logic 0 by means of the program or with the programmer (FORCE VAR). In this way the relevant error bit in IW7 becomes zero again. If the short circuit still exists, the output is switched off again immediately and the error bit will be set again a-35

122 VISB Electrical connections Relay boards The relay boards IRP1-02-1/x and IRP2-02-1/x provide one or two floating contacts. The boards are mounted at a valve position and can be used to good advantage: to connect up load devices with an operating voltage other than 24 V, with high current consumption, to connect up floating signals being transmitted to a master controller or lower-level piece of equipment. Max. contact rating of relay boards: - 2 A at 230 V AC - 2 A at 24 V DC LED side 12 (output n+1) Relay 1 Single relay board 1 2 Relay 2 Double relay board Pin plug 4 Fig. 2/26: Relay with one or two relays The LED for relay 1 is included in the basic unit. This is the same LED as shows the switching position for valve side 14 when a valve is fitted (output n). 2a

123 VISB Electrical connections Electrical inputs Two inputs are available for user applications on the valve sensor coupling unit of the programmable valve terminal. There are two further inputs above the control block. The inputs have positive logic (PNP inputs). PNP inputs Common fuse (4 A slow blowing) for supply to sensors SI EM ENS RUN BF STOP Fig. 2/27: Sensor inputs of the programmable valve terminal Each of these inputs has a yellow LED for the status display a-37

124 VISB Electrical connections Input sockets Upper row Pin assignment of sockets 24 V (fused) 1 2 Ix Internal connection of pins Explanation Bridge between pin 2 and pin 4 Ix V LED for status of input Lower row 24 V (fused) Ix+1 LED for status of input Ix 0 V Connection between pins 2/4 of upper row and pin 2 of lower row Advantages: Two inputs can be connected on the lower row. Therefore: - Less tubing - Converter or chageover switch can be connected Fig. 2/28: Pin assignment of inputs WARNING If you use the lower socket for two input cables, the upper socket must remain unused and must be protected by a dust cap. PLEASE NOTE If the lower socket is used for two inputs, the DUO cable and the appropriate extension cable should be used. Description see part 1, chapter 1.3, in this manual. 2a

125 VISB Addressing 2.4 ADDRESSING TP a-39

126 VISB Addressing Contents 2.4 ADDRESSING Designating the inputs/outputs...2a-41 Identification...2a-43 2a

127 VISB Addressing 2.4 ADDRESSING Designating the inputs/outputs The valve coils, the electrical inputs of sensors and the additional electrical outputs are addressed as onboard periphery by the PLC program. The address range of the inputs is principally from I0.0 to I6.7. However, the largest mechanical extension to a valve terminal type 02 permits only the address range I0.0 to I4.1. Access to the addresses I4.2 to I6.7 has no effect and does not produce an error message. The diagnostic information is stored at addresses I7.0 to I7.7. For details see part 3. Address Diagnostic information I7.0 Unused I7.1 Unused I7.2 Short circuit SA0 I7.3 Short circuit SA1 I7.4 Voltage supply sensors V SEN < 10 V I7.5 Voltage supply valves V Val < 21.6 V I7.6 Voltage supply valves V Vout < 10 V I7.7 Unused Fig. 2/29: Diagnostic information in IB7 The address range of the outputs is principally from O0.0 to O7.7. However, the largest mechanical extension to a valve terminal type 02 permits only the address range O0.0 to O4.1. Setting or resetting the addresses O4.2 to O6.7 has no effect and does not produce an error message. The diagram below shows the relationship between the address and the position of the input or output a-41

128 VISB Addressing SB 50/SF 50 O0.1 O0.0 O0.3 O0.2 O0.5 O0.4 O0.7 O0.6 I0.1 I0.3 I0.5 I0.7 I0.0 I0.2 I0.4 I0.6 Size of the programmable valve terminal O1.1 O1.3 O1.0 I1.1 O1.2 I1.3 I1.0 I1.2 4 valves O1.5 O1.7 O1.4 O1.6 I1.5 I1.7 I1.4 I1.6 6 valves O2.1 O2.3 O2.0 O2.2 I2.1 I2.3 I2.0 I2.2 8 valves O2.5 O2.7 O2.4 O2.6 I2.5 I2.7 I2.4 I valves O3.1 O3.0 I3.1 I valves O3.3 O3.2 I3.3 I3.2 O3.5 O3.7 O3.4 O3.6 I3.5 I3.7 I3.4 I valves O4.1 O4.0 I4.1 These outputs are only available for controlling double solenoid and mid-position valves I4.0 Fig. 2/30: Addressing the inputs and outputs on the valve terminal 16 valves 2a

129 VISB Addressing Identifying the inputs and outputs Supports are available for labeling the valves and inputs with system-related designations (20 items in frame) (10 items) Fig. 2/31: Support for designation labels The supports (order no ) are placed over the sockets for the sensor connections. They adhere and cannot fall off when the sensor plugs are inserted. There are three locations for designation signs. Two locations are intended for the inputs, the third location serves for designating the valve coil on side a-43

130 VISB Addressing 2a

131 VISB Technical specifications 2.5 TECHNICAL SPECIFICATIONS PN a-45

132 VISB Technical specifications Contents 2.5 TECHNICAL SPECIFICATIONS - General...2a-47 - Electronic components...2a-48 - Pneumatic components...2a-50 - Sub-base...2a-50 2a

133 VISB Technical specifications TECHNICAL SPECIFICATIONS General Protection class (as per DIN 40050) IP 65 Temperature during operation storage/transport Mounting position Chemical resistance Oscillation (conforming to IEC 68, parts 2...6) Shock (conforming to IEC 68, parts ) Dimensions (LxWxH) when basic unit is fully fitted 0 o C o C - 20 o C o C Any See Festo Pneumatics Catalogue (resistance table) Frequency range Hz Hz at 3.5 mm Hz at 1 g Hz at 0.35 mm Hz at 5 g max. 30 g Valve sensor terminal IISB ( 1 8) x x 141 mm (235.5 x x mm) IISB ( 1 8) x x 141 mm (289.5 x x mm) IISB ( 1 8 ) x x 141 mm (343.5 x x mm) IISB ( 1 8 ) x x 141 mm (397.5 x x mm) IISB ( 1 8) x x 141 mm (429 x x mm IISB ( 1 8) x x 141 mm (483 x x mm) IISB ( 1 8) x x 141 mm (537 x x mm) a-47

134 VISB Technical specifications Electronic components Operating voltage of electronic components and inputs (Pin 1 - operating voltage connection) Rated value (protected against incorrect polarity) 24 V DC Tolerance Residual ripple Current consumption (at 24 V) Valve sensor terminal ± 25 % (18 V...30 V DC) ± 4 Vpp 200 ma + sum of current consumption of inputs Power consumption (P) Calculation P[W] = (0.2 A + I inputs) 24 V Power failure bridging time min. 10 ms Operating voltage of outputs (Pin 2 - operating voltage connection) rated value (protected against incorrect polarity ) tolerance residual ripple External fuse required 24 V DC ± 10 % (21.6 V V DC) ± 4 Vpp current consumption (at 24 V) 10 ma + sum of current consumption of additional outputs + sum of current consumption of switched valve solenoid coils (per solenoid coil 120 ma) Power consumption (P) Calculation P[W] = (0.01 A + I additional outputs + I solenod coil) 24 V 2a

135 VISB Technical specifications Electromagnetic compatibility (EMC) Resistance to interference Discharge of static electricity (as per IEC 801, part 2) Interference bursts (as per IEC 801, part 4) on operating voltage cable on serial interface Interference suppression (as per VDE 0871) Additional outputs Loading Per additional output 10 kv 2 kv 1 kv Limit class B 24 V DC max. 0.5 A (bulbs max. 10 W because of PTC characteristics) Electronic fuse (short circuit, overload) Triggering current Response time (short circuit) max. 1 A max. 1 s Inputs Logic level ON OFF Voltage range Current consumption (at 24 V) (current from sensor to input) Input delay time (at 24 V) 12 V 7.5 V 0 V...30 V max. 9 ma typ. 5 ms a-49

136 VISB Technical specifications Pneumatic components Pneumatic components Air composition Filter fineness (standard) Poppet valve Spool valve Pressure Operating pressure range Rated pressure Highest pressure at 1 Filtered or filtered and dried compressed air Lubricated or nonlubricated compressed air 40 µm 5 µm 2 bar...10 bar; 29 psi psi 6 bar 10 bar Sub-base Fastening Type Fitting Connection size of 1 (compressed air) 3 and 5 (exhaust) 82 and 84 (pilot exhaust) 4 through holes From the front with 4 screws (M6x60) G 1 2 (G 3 8) G 1 8 (G 1 8 ) 2a

137 VISB Technical specifications Notes a-51

138 VISB Technical specifications 2a

139 Programmable valve terminal with control block SB 50 / SF 50 Part 3: System description SB 50 PN

140 PN is included in: Manual Manual Manual

141 VISB - 50 Chapter summary This manual consists of various parts which can be put together depending on the equipment fitted on the valve terminal. Part 1 Basic principles of installation contains information which is not dependent on the type of valve terminal or on the node selected. Part 2a Valve terminal type 02 system description of valve terminal type 02, contains all information specifically for this type of terminal. Part 2b Valve terminal type 03 system description of valve terminal type 03, contains all information specifically for this type of terminal. Part 3 System description for SB 50 contains all PLC-specific information that is independent of the valve terminal type. Part 4 Part 5 Part 6 System description for SF 50 as Master contains additional information that is required when using the PROFIBUS-DP. System description for SF 50 as DP Slave contains additional information that is required when using the SF 50/DP-Slave (SL 50). Appendix contains additional information concerning command sets, abbreviations, accessories, literature, etc.. PN I

142 VISB - 50 Notes 3-II 9706

143 VISB - 50 Table of contents TABLE OF CONTENTS 3.1 STRUCTURE OF NODE SB 50 SB 50 - SIMATIC integrated INTERNAL OPERATING METHOD Function units COMMISSIONING Commissioning and program test Operating modes SB 50 overall reset Commissioning a system Commissioning procedures Loading the program into the SB Saving programs Operation without a battery Signal status display STATUS Signal status display STATUS VAR Controlling variables FORCE VAR Special features Search DIAGNOSTICS AND ERROR TREATMENT Valve terminal diagnosis Reading the diagnostic byte Error message by means of LEDs Faults in the SB Interruption analysis Error in copying a program Abbreviations in ISTACK Program errors PN III

144 VISB - 50 Table of contents 3.5 ADDRESSING Structure of process image table Alarm process diagrams and timecontrolled program processing in OB Address allocation in RAM memory INTRODUCTION TO STEP 5 Creating a program Representation types Operand ranges Program structure Block types Programming Organization block (OB) Program blocks (PB) Step blocks (SB) Function blocks (FB) Block header Creating a function block Calling a function block Programming data blocks Program processing with data blocks Function of data block Program processing Programming possibilities START programming Cyclic program processing Time-controlled program processing Prerequisites for time-controlled program processing Processing blocks Program modifications Block modifications Compressing the program memory Representing numbers IV 9706

145 VISB - 50 Table of contents 3.7 STEP 5 OPERATIONS Basic operations Linking operations Memory operations Load operations Transfer operations Time operations Counting operations Arithmetical operations Comparison operations Block access operations Jump-back functions Zero operations Stop operations Picture structure operations Supplementary operations Linking operations Bit and memory operations Time and counting operations Load and transfer operations Jump operations Other operations System operations Evaluating CC 0 and CC V

146 VISB - 50 Table of contents 3.8 INTEGRATED BLOCKS DB1: parametrizing internal functions Rules for parametrizing DB Transferring the DB1 parameters Parameter block ERT Localizing parametrizing errors Parameter block SDP Parameter block TFB Parameter block SL DB1 parametrizing for reference Integrated function blocks Code converter: B4 -FB Code converter: 16 -FB Multiplier: 16 -FB Divider: 16 -FB Analogue value adaption blocks Reading the analogue value -FB Outputting the analogue value -FB Diagnostics SINEC L2-DP -FB Diagnostics of local periphery -FB Integrated organization blocks Cycle trigger -OB PID-control algorithm -OB SB 50 to SINEC L Parametrizing for data exchange Coordinating the data exchange Sending data Structure of coordinating byte KBS Receiving data Structure of coordinating byte KBE Special features VI 9706

147 VISB SIMATIC Integrated 3.1 SIMATIC Integrated PN

148 VISB SIMATIC Integrated Contents 3.1 STRUCTURE OF NODE SB 50 SB 50 - SIMATIC integrated

149 VISB SIMATIC Integrated SB 50 - SIMATIC integrated SIMATIC Integrated By equipping a valve terminal with SIMATIC, FESTO offers an economic solution for simple automation tasks which require pneumatic control. The SB 50 is a PLC with the command and operating scope of the SIMATIC mini controllers. S5-155U S5-135U S5-115U S5-95U S5-90U S5-100U SB 50 is a PLC with the scope of commands and operations of the mini controllers in the SIMATIC family Fig. 3/1: Position of the SB 50 in the SIMATIC family The following connection possibilities are available: Valves Digital inputs and outputs Operating and observing L1 bus

150 VISB SIMATIC Integrated Simple programming The proven STEP 5 software is available for programming in the three languages ladder diagram, function chart and statement list. Programming is made with the programmers of the SIMATIC family. In this way you can: - Make use of existing programs - Transfer programs - Use your experience with STEP 5 and - Carry out commissioning as is customary. Operating and display elements SIEMENS RUN STOP LED for control PG Diagnostic interface Mains supply 24VDC FUSE Fuse for sensor connections Fig. 3/2: SB 50: Display/operating elements and interfaces

151 VISB Internal operating method 3.2 INTERNAL OPERATING METHOD PN

152 VISB Internal operating method Contents 3.2 INTERNAL OPERATING METHOD Function units v:\sb50-gb\sys-sb50\sb5-k32.chp

153 VISB Internal operating method 3.2 INTERNAL OPERATING METHOD The following chapter describes how the SB 50 processes your program. Function units SB 50 CPU PII Calculator Operating system (ROM memory) Internal program memory (RAM) Memory module (EEPROM) Timers Counters Flags Controller PIQ Serial interface FESTO- Periphery bus Input modules Valves Output modules FESTO modules Fig. 3/3: Function units SB

154 VISB Internal operating method SIMATIC Integrated Program memory (EEPROM) In order to protect the control program of the SB 50 against loss in the event of a power failure, you must save it on an integrated EEPROM module. Programs thus saved on the EEPROM module are automatically copied into the internal program memory when the voltage supply is switched on (see fig. 3/7). This internal program memory is a reserved area of the internal RAM of the CPU. The internal RAM memory has the following characteristics: - The memory contents can quickly be amended. - The memory contents are deleted if there is a power failure. Operating system (ROM memory) The operating system contains system programs in which the design of user program, input and output management, distribution of memory space, data management etc. are determined. The operating system is specified and cannot be modified. Process image table (PII, PIO) The signal states of the inputs and outputs are stored in the CPU in "Process image tables." These process image tables are reserved areas in the RAM memory of the CPU. There are separate process image tables for input and output modules: - The process image inputs table (PII) and - The process image outputs table (PIO)

155 VISB Internal operating method Serial interface Connection for programmers, operating and observation units. The SB 50 can also be connected as slave on the SINEC L1 bus. SIMATIC Integrated PLEASE NOTE The programmer interface has been designed as a passive interface. (e.g. PG605 cannot be used, an active interface converter V 24 TTY is required for PCs). Timers, counters and flags The CPU makes internally available timers, counters and flags which can be used by the control program. The timers and counters can be set, reset, started and stopped by the program. The values for the timers and counters are stored in reserved areas of the RAM. Information, e.g. intermediate results can be stored as flags in a further range of the RAM. The flags can be addressed bit-by-bit, byte-by-byte or word-by-word. If there is a power failure, some of the flags and counters in the internal RAM are saved in an integrated EEPROM. When the mains voltage is switched on again, they are written back into the internal RAM. We then speak of remanent flags and remanent counters. The following table shows the number and remanence reaction (contents of internal memory are saved/not saved) of the timers, counters and flags. Operand Remanent Non-remanent Flags F0.0...F63.7 F F255.7 Counters C0...C7 C8...C127 Timers --- T0...T127 Table 3/1: Remanent and non-remanent operands

156 VISB Internal operating method Arithmetic-logic unit The arithmetic-logic unit consists of two accumulators, ACCU1 and 2. These can process byte and word operations. Load information from the PII Process information in ACCU1 and ACCU2 Transfer information to the PIO Fig. 3/4: Example for the operation of the calculator ACCU1 ACCU High byte Low byte High byte Low byte Fig. 3/5: Structure of the accumulators Control unit Depending on the control program, the control unit accesses the instructions in the program memory one after the other and processes them. In doing this it processes the information from the PII, and takes into consideration the values of the internal timers and counters as well as the signal states of the internal flags. SIMATIC Integrated Festo peripheral bus (PBUS) The Festo peripheral bus is the electrical connection for all signals exchanged between the CPU und the valves or the input and output modules

157 VISB Commissioning 3.3 COMMISSIONING PN

158 VISB Commissioning Contents 3.3 COMMISSIONING Commissioning and program test Operating modes SB 50 overall reset Commissioning a system Commissioning procedures Loading the program into the SB Saving programs Operation without a battery Signal status display STATUS Signal status display STATUS VAR Controlling variables FORCE VAR Special features Search

159 VISB Commissioning 3.3 COMMISSIONING AND PROGRAM TEST This chapter contains instructions on commissioning, the program test and operation of the SB 50. SIEMENS PG RUN STOP Operating mode display (green LED RUN) Operating mode display (red LED STOP) Fig. 3/6: Operating field of the SB 50 SIMATIC Integrated Operating modes Changing the operating mode A change can be made from one operating mode to another as follows: - by a programmer - by faults which bring the SB 50 into the operating mode "STOP". After POWER ON, the terminal initially goes into the RUN mode. If an error is present, the SB 50 then goes directly into the STOP mode. Operating mode "STOP" The program will not be processed. - The values of timers, counters, flags and process diagrams, which are current at the moment the "STOP" status is reached, will be maintained. - Valves and output modules will be blocked (signal status "0")

160 VISB Commissioning - In the transition from "STOP" to "RUN", the process diagrams, timers and the non-remanent flags and counters will be set at "zero". Operating mode "RUN" - The program is processed cyclically. - Times started in the program run out. - The signal states of the input modules are loaded. - The valves and output modules are addressed. - Operating mode "RUN" can also be set after "GENERAL RESET", i.e. with an empty program memory. Operating mode "START" - The DB1 is processed by the operating system and the parameters are transferred. - The start organisation blocks OB21 or OB22 are processed. - The start duration is not limited in time as the cycle time monitoring is not activated. - Time-controlled program processing is not possible. - The valves, input and output blocks are blocked during the start. SB 50 Overall reset SIMATIC Integrated Before entering a new program, we recommend that you perform the function "Overall reset". The following will then be deleted: - the program memory of the SB 50 (RAM and EEPROM), - all data (flags, times and counters) as well as - all error identifiers

161 VISB Commissioning The OVERALL RESET function is triggered by the reset of all modules of the SB 50 (see programmer manual) and is possible only in the STOP mode. PLEASE NOTE Without "Overall reset", information will be maintained even if the program is overwritten. Commissioning a system The following section contains instructions on project planning and on how to commission a system with programmable logic controllers. Instructions on project planning and installation Since the product when used is usually an integral part of a system, these instructions should serve as a guide for safe integration of the product. WARNING The relevant safety and accident prevention regulations must always be observed. If used with a fixed connection (non-moveable devices and systems) without an all-pole power-off switch and/or fuses, a power-off switch must be fitted into the installation; the device must be connected to a PE conductor. If using devices operated by a mains switch, check before commissioning whether the rated voltage range set corresponds to the local mains power supply. With a 24 V supply, the low voltage must be correctly separated from the mains supply

162 VISB Commissioning WARNING (continued) Fluctuations in the mains voltage from the rated value must not exceed the tolerance limits quoted in the technical specifications, otherwise there may be operating failures and dangerous situations on the electronic modules/device. Measures must be taken, so that a program can be continued properly after voltage failures and interruptions. Dangerous operating conditions must not occur, not even briefly. If necessary "emergency stop" must be used. Emergency stop devices as per EN 60204, IEC 204 (VDE 0113) must be effective in all operating modes of the automation device. Unlocking the emergency stop device must not trigger any uncontrolled or undefined new start. Connection and signal cables must be installed so that inductive and capacitive influences do not impair the automation functions. Automation devices and their operating elements must be fitted so that they are sufficiently protected against unauthorized handling In order that a cable or core fracture on the signal side does not lead to undefined states in the automation device, appropriate safety measures must be taken in both the hardware and the software in the I/O coupling

163 VISB Commissioning Commissioning procedures for the SB 50 Prerequisites, work steps System and SB 50 must be switched off Check mechanical configuration and wiring Remarks Observe installation guidelines as per VDE 0100/VDE 0113 and VDE Displays Test periphery Switch on power supply and load power unit for SB 50 Connect programmer to SB 50 Overall reset SB 50 SB 50 at "RUN" Operate signal generators one after the other Switch on power supply for valves and outputs Control outputs with programmer function "FORCE VAR" Programmer function Programmer function With progr. function "STATUS VAR" the Input signals can be observed in PII. The switching states of the valves and actuators are modified Red LED of SB 50 lights up Green LED of SB 50 l lights up Test program SB 50 at "STOP" Transfer user program from programmer to SB 50 SB 50 at "RUN" Test program and correct if necessary SB 50 at "STOP" Save program with "COMPRESS" on EEPROM SB 50 in "RUN" Programmer function Programmer function Programmer function Programmer function Programmer function Programmer function System is in operation Red LED of SB 50 lights up Green LED of SB 50 lights up Red LED of SB 50 lights up Red LED flickers and then lights up Table 3/2: Commissioning the SB

164 VISB Commissioning Loading a program into the SB 50 During loading, a program is transferred to the program memory of the SB 50. As first possibility, you can load a program from a connected programmer (on-line operation). The exact instructions are to be found in the manual for your programmer. The second possibility, the automatic loading from a memory block, is described overleaf. SIMATIC Integrated During automatic loading, the program is copied from the integrated EEPROM memory block into the program memory of the automation unit. Only valid blocks are loaded

165 VISB Commissioning SB 50 switched off Power on System initialization Copy blocks EEPROM RAM Error? Yes Red LED blinks No Red LED flickers SB 50 in STOP (carry out error diagnosis ) Blocks in RAM of SB 50 RUN-info in EEPROM? Yes No Red LED lights up Green LED lights up SB 50 in STOP SB 50 in RUN Fig. 3/7: Procedure for "Load program from integrated EEPROM into SB 50"

166 VISB Commissioning Saving the program SIMATIC Integrated During saving, a program is copied from the program memory of the SB 50 into an integrated EEPROM memory block. Only valid blocks are saved. The integrated default-db1, also belongs here, as soon as it has been modified. Power on SB 50 in operating mode STOP COMPRESS programmer function Copy block RAM EEPROM Error? Yes Red LED blinks No Red LED flickers: Program is saved Carry out error diagnosis Red LED lights up Program saved on EEPROM Fig. 3/8: Procedure for "Save program from RAM to EEPROM memory block"

167 VISB Commissioning Operation without a backup battery Program blocks Flags FY255 Counters C127 Y64 Timers T127 C8 Y63 C7 FY0 C0 T0 RAM Data blocks FB SB PB OB Power off DB Power on Compress. PB programmer function OB Power on FY63 C7 FY0 C0 EEPROM FB SB DB Fig. 3/9: RAM-EEPROM SIMATIC Integrated In addition to the RAM, an EEPROM has also been firmly installed for data saving. This EEPROM enables the SB 50 to be operated without a battery and fully maintenance-free. If there is an interruption of the operating voltage, the remanent operands (see table 3/1) are transferred from the RAM to the EEPROM and are written back into the RAM when the operating voltage is switched on again. The remaining non-remanent operands are set at zero. When the voltage supply is switched on again, the blocks, i.e. the program, are also written from the EEPROM into the RAM. The blocks can be written in operating mode STOP from the RAM into the EEPROM by means of the programmer function COMPRESS. Data blocks are not saved in the EEPROM after interruption of the operating voltage

168 VISB Commissioning Like the other blocks, the data blocks are also written in operating mode STOP from the RAM into the EEPROM by means of the programmer function COMPRESS. When the operating voltage is switched on again, the values stored in the EEPROM are copied into the RAM and any values formed in the process are overwritten. PLEASE NOTE Data blocks are not remanent. The resulting start reaction must be taken into account at all costs when the program is created. Program-dependent signal status display "STATUS" This test function shows the current signal states and the RLO of the individual operands during program processing. Corrections to the program can also be carried out. Direct signal status display "STATUS VAR" This test function shows the status of any operand (inputs, outputs, flags, data words, counters or timers) at the end of program processing. Information from inputs and outputs is taken from the process image table of the selected operands. Controlling variables "FORCE VAR" The process image table of the operands is modified in operating mode RUN of the SB 50. The following variables can be modified: I, Q, F, T, C and D. Program processing with the modified process variables is carried out in operating mode RUN. In the further course of the program, they can be modified again, without any return message. The process variables are controlled asynchronously to the program

169 VISB Commissioning Special features The variables I, Q and F can be modified bit-by-bit, byte-by-byte or word-by-word in the process diagram. In the case of the variables T and C in the format KM and KH - Enter also "YES" in the mask PRESETTINGS in the field SYSTEM COMMANDS (with screen programmers). - Note the control of the edge flags. The signal status display is interrupted if there is an incorrect format entry or operand entry. The programmer then shows the message "CONTROL NOT POSSSIBLE." Information on accessing the test functions on the programmer are to be found in the appropriate programmer manuals

170 VISB Commissioning Search The search is used to look for certain terms in the program. These terms are then listed on the programmer display. Amendments to the program can be made at this stage. Searches can be made in the following programmer functions: - INPUT - OUTPUT - STATUS Possible search terms: - Statements (e.g. A I32.0) - Operands (e.g. Q32.5) - Labels (e.g. X 01) Only possible in function blocks - Addresses (e.g. 0006H) PLEASE NOTE The search is made differently in the individual programmers and is described in detail in the appropriate operating instructions

171 VISB Diagnostics and error treatment 3.4 DIAGNOSTICS AND ERROR TREATMENT PN

172 VISB Diagnostics and error treatment Contents 3.4 DIAGNOSTICS AND ERROR TREATMENT Valve terminal diagnosis Reading the diagnostic byte Error message by means of LEDs Faults in the SB Interruption analysis Error in copying a program Abbreviations in ISTACK Program errors

173 VISB Diagnostics and error treatment 3.4 Diagnostics and error treatment Valve terminal diagnostics SIMATIC Integrated The diagnostic byte offers the user the possibility of carrying out a diagnosis of the valve terminal via the PLC program. The diagnostic byte is in the input byte IB7 in the SB 50. Bit no.: IB7 F F F F F Not used V val: Supply voltage of valves < 10 V V val: Supply voltage of valves < 21.6 V V sen: Supply voltage of sensors < 10 V SA1: Short circuit output (only type 02) SA0: Short circuit output (at type 03 group message) Not used Not used F = 1 Error message without meaning in SB 50 Fig. 3/10: Assignment of diagnostic byte in the SB 50 The messages SA0 and SA1 are individual messages for the two special outputs in the case of a type 02 valve terminal. In the case of valve terminal type 03, only bit I7.2 is present; this is a group message and indicates a short-circuit at one of the electrical outputs

174 VISB Diagnostics and error treatment Notes on diagnostics information: Vsen: Operating voltage for the sensors is below 10 V. This error occurs when the fuse for the sensors has blown. Vval: The valves are designed for an operating voltage of 24 V ± 10 % ( V). If the voltage at Pin 2 of the mains socket falls below 21.6 V, the bit Vval is set. The cause may be overload of the power supply unit or a supply cable which is too long. Vout: The operating voltage of the valves and electrical outputs is below 10 V. Pin 2 of the power supply connection is monitored. The cause may be an open-circuit line, a blown fuse or an interruption caused by an EMERGENCY STOP; see also Vval. Reading the diagnostic byte The data stored in the diagnostic byte can be read and evaluated in the control program by means of binary operations (e.g. A I7.2) or with load operations (e.g. L IB7). Error message by means of LEDs If there is an error in the operating method of your controller, this will be shown in the operating field of the programmer (see table 3/3). If both LEDs light up, the SB 50 has started

175 VISB Diagnostics and error treatment Error display SB 50 in STOP, red LED lights up AG in STOP, red LED blinks Programmer in RUN, green LED lights up, incorrect operation Error analysis Fault in SB 50 Carry out interrupt analysis with programmer. Error in loading or saving the program on EEPROM. Carry out interrupt analysis with programmer. Program error or fault in periphery Carry out fault analysis Table 3/3: Error display and error analysis Faults in the SB 50 Analysis function "ISTACK" The interruption stack is an internal memory of the SB 50. The causes of faults are stored here. If there is a fault, a bit will be stored in the appropriate byte of the memory. The memory can be read byte-by-byte via the programmer. This can be accessed in the menu on the programmer in operating mode "STOP". The sequence of keys can be found in the programmer manual. PLEASE NOTE Only the ISTACK bytes (first diagram) can be output in operating mode RUN. There is no interruption which could cause the SB 50 to enter the "STOP" status. The control bits are output in bytes (first diagram)

176 VISB Diagnostics and error treatment Interruption analysis ISTACKdisplay Cause of error Elimination SUF Substitution error Correct FB call TRAF Transfer error Eliminate program error - Programmed DB with DW no. greater than data block length - Programmed data block command without previous DB opening NNN - Command cannot be decoded Eliminate program error - Bracket level exceeded () - Parameter exceeded - Direct periphery access in cyclic program processing NINEU No restart possible Overall reset, load program STS Stop by programmer or software stop by S5 command (STP) STUEB Block stack overrun The max. nesting depth (16) is Eliminate program error exceeded NAU Power failure Stabilize supply voltage QVZ Acknowledgement delay Error in decentral periphery or in L2-DP interface ZYK Cycle time exceeded The program processing time exceeds the cycle monitoring time Cause: - program too long PEU Periphery not clear Error in local periphery ASPFA EEPROM error - Maximum number of write cycles reached - Error in write cycle Table 3/4: Interrupt analysis Check decentral periphery blocks and if necessary replace (SD15/16) Check program for endless loops or shorten Check valve terminal periphery (SD14) Replace SB 50 Try again

177 VISB Diagnostics and error treatment With table 3/4 you can ascertain the cause if there is an interruption in the program processing. The SB 50 then enters the "STOP" status. Error in copying a program Error message: After "Switch automation device to RUN", the red LED blinks again. ISTACK display BSTSCH SCHTAE ADRBAU STOANZ STOZUS NEUSTA AF KOPFNI URLAD SYNFEH CC 1/CC 0 OVFL ODER CARRY STATUS RLO ERAB FKT Abbreviations in ISTACK Explanation Shift block Actuate shift Address list structure SB 50 in "STOP" Internal control bit for STOP/RUN transfer SB 50 has not yet been in cycle after POWER ON Cause see interrupt analysis Alarm release/release time-controlled OB13 Faulty program Block head cannot be interpreted General reset, program defective Synchronizing error (block not correct, e.g. block head missing) Display bits for arithmetical, logical and shift operations Arithmetical overflow Identifier bit OR memory Carry between the two bytes of the arithmetic unit Status recognition of operands of last processed binary command Result of logic operation Identifier bit first interrogation 0: O( OR bracket open 1: U( AND bracket open Table 3/5: Meaning of remaining relevant ISTACK bits

178 VISB Diagnostics and error treatment Program errors Determining the error address. The STEP address counter (SAC) in ISTACK (bytes 25, 26) gives the absolute memory address of the STEP 5 instruction in the programmer which caused the programmer to enter the "STOP" status, or it indicates the block start address of the incorrect block. The relevant block start address can be found with the programmer function "DIR AG". If the instruction is not permitted, the programmer will interrupt the program processing and enter the "STOP" status with the error message "NNN". The STEP address counter stands on the absolute address of the next, still unprocessed instruction or on the block start address of the incorrect block in the program memory. Program tracing with the "BSTACK" function. During program processing, the following information about jump functions is entered in the block stack (BSTACK): - the data block which was valid before the module was exited; - the absolute block start address - this gives the memory address of the block start in the program memory. This information can be accessed with the programmer function "BSTACK " in operating mode STOP, if the SB 50 enters the STOP status due to a fault. There is no BSTACK regeneration after POWER OFF. SIMATIC Integrated System parameters The system parameters (e.g. software status) of the SB 50 can be read with the programmer function "SYSPAR" (see programmer manual)

179 VISB Addressing 3.5 ADDRESSING PN

180 VISB Addressing Contents 3.5 ADDRESSING Structure of process image table Alarm process diagrams and timecontrolled program processing in OB Address allocation in RAM memory

181 VISB Addressing 3.5 ADDRESSING The inputs and outputs on the valve terminal are described herein as local periphery. In order that the valves and the inputs and outputs of the local periphery can be addressed, they must be assigned with certain addresses. The addresses of the local periphery are orientated around the physical arrangement of the valve terminal. The various valve terminals have a different distribution and arrangement of the addresses. Please refer to Part 2 for the valid addressing. Structure of process image table SIMATIC Integrated Information about the inputs is stored in the process image input table (PII), and information about the outputs is stored in the process image output table (PIQ). The PII and the PIQ of the local periphery cover a range of 8 bytes each in the RAM memory. Byte address in Inputs PII and PIQ IB0...6 Local inputs 7 IB7 Local valve terminal diagnostics Outputs QB0...7 Local outputs Table 3/6: Structure of process input image table (PII) and process output image table (PIQ)

182 VISB Addressing Alarm process image tables and time-controlled program processing in OB13 The SB 50 offers the possibility of time-controlled program processing for which the OB13 must be programmed. This is accessed periodically. The frequency of access can be set (see chapter 3.8). Within the time-controlled program processing, you can use the operand identifiers "PB", "PY", "PW" on the local periphery. PLEASE NOTE The load and transfer operations with the operand identifiers "PB", "PY", "PW" on the local addresses do not effect a direct access to the periphery, but represent an image table of the PIQ/PII. The alarm process image tables are only used in time-controlled program processing. The alarm process image tables and the "normal" process image tables are structured identically

183 VISB Addressing Address allocation of the RAM memory SIMATIC Integrated The tables below show how the RAM memory of the two automation devices is assigned. Address RAM memory Address RAM memory Address RAM memory 0000 H FF H 0100 H FF H 4100 H CFF H 5D00 H EFF H 5F00 H FFF H 6000 H F H 6010 H FF H 6100 H F H 6140 H FF H Internal data Program memory Internal data System date Timer T0...T127 Counter C0...C7 (remanent) Counter C8...C127 (non remanent) Flags F (remanent) FY0...FY63 Flags F (non remanent) FY64...FY H H 6208 H F H 6280 H H 6288 H FF H 6300 H FF H 6400 H H 6408 H F H 6480 H H 6488H FF H Alarm PII local periphery Alarm PII decentral periphery Alarm PIQ local periphery Alarm PIQ decentral periphery Internal data PII of local periphery 6407 loc. diag. PII of decentral periphery PIQ of local periphery PIQ of decentral periphery 6500H FF H 7600H FF H 7800H FF H 7A00H BFF H 7C00 H DFF H 7E00H FFF H Internal data Module address list OB Module address list FB Module address list PB Module address list SB Module address list DB Table 3/7: RAM memory in the SB5 0 SIMATIC Integrated The table overleaf shows the sequence of system data which are important for the user

184 VISB Addressing System data word Address (hex.) Meaning 13 5D1A Number of processed timers 14 5D1C Error code PBUS (local periphery) permits error analysis with set ISTACK bit PEU 15 5D1E Error code of decentral periphery or from interface PLC field bus permits error analysis with set ISTACK bit QVZ ( not for SB 50) 16 5D20 Extended error code of decentral periphery or from interface PLC field bus permits extended error analysis if bit QVZ is set ( not for SB 50) 17 5D22 00 = standard parameter SF = user parameter SF D24 Number of EEPROM segment (0...31), which accepts the system data to be stored remanent 19 5D26 Number of write cycles EEPROM ( ) 20 5D28 EEPROM write error 21 5D2A Number of local input bytes 22 5D2C Number of local output bytes 33 5D42 Full indicator of internal program memory 5D D44 5D46 Full indicator of assembler range start address of internal RAMs 37 5D4A End address of internal RAMs 5D4B D50 CPU version / software status 5D5F D SINEC L1 parameter field 5D7F 97 5ECC Time interval for OB13 (multiples of 10 ms) 5DC ECC 5ECD Explanatory error messages, e.g. memory errors Module stack Interrupt stack Table 3/8: System data range of the SB

185 VISB Introduction to STEP5 3.6 INTRODUCTION TO STEP 5 PN

186 VISB Introduction to STEP5 Contents 3.6 INTRODUCTION TO STEP 5 Creating a program Representation types Operand ranges Program structure Block types Programming Organization block (OB) Program blocks (PB) Step blocks (SB) Function blocks (FB) Block header Creating a function block Calling a function block Programming data blocks Program processing with data blocks Function of data block Program processing Programming possibilities START programming Cyclic program processing Time-controlled program processing Prerequisites for time-controlled program processing Processing blocks Program modifications Block modifications Compressing the program memory Representing numbers

187 VISB Introduction to STEP5 3.6 INTRODUCTION TO STEP 5 This chapter describes how to program automation tasks with the SB 50. An explanation is given of how programs are created and of the blocks which can be used to form the links in a program. You will also find a summary of the various number representations recognised by the programming language STEP 5. Creating a program With programmable logic controllers (PLC) automation tasks are formulated as control programs. Here the user determines in a series of instructions, how the SB 50 is to control the system. In order that the automation device can "understand" the program, the latter must be written in a particular language, i.e. the programming language, in accordance with fixed rules. The programming language STEP 5 has been developed for the SIMATIC S5 family

188 VISB Introduction to STEP5 Representation types The following representation types are possible with the uniform programming language STEP 5 for the SI- MATIC S5 series: Statement list (STL): The STL presents the program as a sequence of command abbreviations. An instruction is composed as follows: 002: A I 2.0 Relative address of instruction in relevant block Operation Operand Parameter Operand identifier Fig. 3/11: Structure of an instruction The operation tells the SB 50, what it must do with the operand. The parameter specifies the address of an operand. Control system flow chart (CSF): In the CSF the logical links are represented graphically as symbols. Ladder diagram (LDR): In the LDR the control functions are represented graphically with symbols of the circuit diagram. GRAPH5: This representation type serves for describing the structure of sequence controllers. The "fast version" can be used in the SB 50. Each representation type has special characteristics. A program block which has been programmed in STL cannot be output without further treatment in CSF or LDR. Also, the graphical representation types are not compatible with each other

189 VISB Introduction to STEP5 However, programs in CSF or LDR can always be translated into STL. These statements are represented below in the form of a sets diagram. CSF LDR STL Fig. 3/12: Compatibility between programming languages The programming language STEP 5 distinguishes between three types of operations: Basic operations Supplementary operations System operations Table 3/10 contains further information on the individual operation types. Programming language STEP 5 Basic operations Supplementary operations System operations Area of application In all blocks Only in function blocks Only in function blocks Representation STL, CSF, LDR STL STL Special features Only for users with good knowledge of the system. Table 3/9: Comparison of operation types

190 VISB Introduction to STEP5 Operand ranges The programming language STEP 5 recognises the following operand ranges: I (Inputs) Interfaces from the process to the automation device Q (Outputs) Interfaces from the automation device to the process F (Flag) Memory for binary intermediate results D (Data) Memory for digital intermediate results T (Timers) Memory for implementing timers C (Counter) Memory for implementing counters P (Periphery) Interface from the process to the automation device K (Constants) Fixed numerical values OB (blocks) Aids for structuring the program PB SB FB DB

191 VISB Introduction to STEP5 Program structure For solving complex tasks, the user should divide the complete program into sensible individual self-contained program parts (blocks). This procedure offers the user the following advantages: Simple and easy-to-understand programming even of larger programs. Possibility of standardizing program parts Simple possibilities of amendment Simple program test Simple commissioning Subprogram techniques (accessing a block from different points) There are five blocks types in the programming language STEP 5: Organization blocks (OB) Organization blocks manage the control program. Program blocks (PB) The control program is divided up according to functional or technological viewpoints in program blocks. Step blocks (SB) Step blocks are special program blocks for programming sequence controllers. They are treated like program blocks. Function blocks (FB) Function blocks are special program blocks. Frequently reoccurring or particularly complex program parts (e.g. message or calculating functions) are programmed in function blocks. They can be parametrized and possess an extended scope of operations (e.g. jump operations within a block)

192 VISB Introduction to STEP5 Data blocks (DB) The data blocks are used for storing datas which are required for processing the control program. These are e.g. actual values, limit values or texts. A block can be exited with block accesses and a jump made to another block. Program, function and step blocks can therefore be nested in up to 16 levels. PLEASE NOTE When calculating the nesting depth, you must take into account that, under certain circumstances, the system program in the SB 50 can itself access an organisation block (e.g. OB13). The complete nesting depth is the sum of the nesting depths of the cyclic (OB1) and time-controlled (OB13) program processing. If there are more than 16 levels of nesting, the SB 50 will enter the STOP status with the error message "Block stack overflow STUEB". OB1 PB1 FB110 FB7 PB2 FB111 FB60 DB2 PB10 FB81 Level 1 Level 2 Level 3 Level 4 Level 16 Fig. 3/13: Nesting depth

193 VISB Introduction to STEP5 Number Block types The most important features of the individual block types are to be found in the table below. OB PB SB FB DB OB1...OB PB0...PB SB0...SB FB0...FB DB2...DB255 Length (max) 8 kbyte 8 kbyte 8 kbyte 8 kbyte 256 Data words Operation scope Programming languages Length of mod. head Basic operations STL, CSF, LDR Basic operations STL, CSF, LDR Basic operations STL, CSF, LDR Basic operations, suppl. operations, system operations STL CSF 4, LDR 4 Bit pattern Numbers texts 5 words 5 words 5 words 5 words 5 words 1 Special OBs are accessed automatically from the operating system 2 Function blocks have already been integrated in the operating system 3 Data blocks DB0 and DB1 are reserved 4 As from V6.x STEP 5 Table 3/10: Comparison of block types Programming The blocks are programmed as follows (except for data blocks): - Specify block type (e.g. PB), - Specify block number (e.g. 27), - Enter the instructions of the control program, - Terminate the block with instruction "BE"

194 VISB Introduction to STEP5 Organization blocks (OB) Organization blocks form the interface between the operating system and the control program. There are three types of organization blocks. An organization block is accessed cyclically from the operating system (OB1) Some of the organization blocks are event-controlled or time-controlled, i.e. they are accessed by - STOP - RUN or POWER OFF - POWER ON transition (OB21, OB22) - Time intervals (OB13) Some other organization blocks represent operating functions (similar to the integrated function blocks), which can be accessed by the control program (see chapter 3.8.1). OB no. Function OB must be programmed by the user and is accessed by the program OB1 Cyclic program processing Alarm-controlled program processing OB13 Time-controlled program processing Treatment of start reaction OB21 When switched on manually (STOP RUN) OB22 When voltage is switched on again OB has already been programmed, OB must be accessed by user OB31 Cycle time triggering OB251 PID control algorithm Table 3/11: Summary of organisation blocks In the SB 50, you can program all organisation blocks with parameters from the permitted range (OB ). However, they must be accessed in the control program

195 VISB Introduction to STEP5 The following diagram shows how to build up a structured control program. It also makes clear the importance of the organization blocks. OB21/22 Cycle Start OB1 PB1 FB110 FB111 System program Organization blocks Control program Fig. 3/14: Example for the use of organization blocks

196 VISB Introduction to STEP5 Program blocks (PB) Self-contained program parts are programmed in these blocks. Special feature: The control functions can be represented graphically in program blocks. Access Program blocks are activated with the block accesses JU and JC. These operations can be programmed in all block types, except for data blocks. block accesses and terminations limit the RLO. However, it can be transferred and evaluated in the "newly accessed" block. Step blocks (SB) Step blocks are special forms of program blocks for processing sequence controllers. They are treated like program blocks. Function blocks (FB) Frequently reoccurring or complex control functions are programmed in function blocks. Special features Function blocks can be parametrized, Actual parameters can be transferred when the block is accessed, There is an extended scope of operations compared to other blocks, The program with an extended scope of commands can only be created and documented as STL

197 VISB Introduction to STEP5 With the SB 50 there are various designs of function blocks. These are: programmed by the user, integrated in the operating system or obtainable as a software package (standard function blocks). Block header In addition to the block header, function blocks possess organisation information different from the other blocks. The memory requirement of FBs is calculated from: The block header (5 words) The block name (5 words) The block parameter in parametrizing (3 words per parameter) The FB-access occupies two words in the internal program memory; each parameter a further memory word. Creating a function block In contrast to other blocks, FBs can be parametrized. The following specifications on the block parameters must be programmed for the parametrization. Names of the block parameter (formal operand) - Each block parameter receives a designation (DES) under which, as a formal operand, it is replaced by an actual operand when the function block is accessed. - The name may contain max. four characters and must begin with a letter. You can program up to 40 parameters per function block

198 VISB Introduction to STEP5 Type of block parameter The following parameter types can be entered: - I Input parameter - Q (O) Output parameter - D Date - B Block - T Timer - C Counter Output parameters are shown to the right of the function symbol in the graphic representation. The other parameters are on the left. Type of block parameter You can specify the following types: - BI for operands with bit address - BY for operands with byte address - W for operands with word address - K for constant values Block header (5 words) Block name (5 words) Block parameter (3 words per parameter) Control program Name: EXAMPLE DES: DES: DES: IN1 IN2 OUT1 Parameter :A = IN 1 :A = IN 2 := = OUT1 I I Q Sort of Program example BI BI BI Type Fig. 3/15: Programming of the FB with block parameter All specifications on the block parameters must be entered for parametrizing

199 VISB Introduction to STEP5 Form of Type of parameter parameter I, Q BI for an operand with bit address Permitted actual operands I x.y Inputs Q x.y Outputs F x.y Flags BY for an operand with byte address IB x Input byte QB x Output byte FY x Flag byte DL x Data byte left DR x Data byte right PY x Periphery byte* W for an operand with word address IW x Input word OW x Output word FW x Flag word DW x Data word PW x Periphery word* D KM for a binary pattern (16 positions) Constants KY for two byte-by-byte numbers in the range 0 to 255 KH for a hexadecimal pattern (max. 4 positions) KS for a character (max. 2 alphanumerical characters) KT for a time value (BCD time value) with pattern 1.0 to KC for a counter value (BCD) 0 to 999 KF for a fixed-point number in the range to B No type display permitted DBx Data block, command ADBx is processed OBx Organisation blocks are accessed absolute FBx Function blocks (only without parameter) are accessed absolute PBx Program blocks are accessed absolute SBx Step blocks are accessed absolute T No type display permitted T Timer; time value must be parametrized as date or as constant in FB C No type display permitted C Counter; counter value must be parametrized as date or as constant in FB * Not for integrated FBs and only permitted within the time-controlled program processing (OB13) Table 3/12: Form and type of block parameter with permitted actual operands

200 VISB Introduction to STEP5 Calling a function block Function blocks are stored, like the other blocks, under a certain number (e.g. FB47) in the internal program memory. The numbers are reserved for integrated FBs. Accesses of FBs can be programmed in all blocks except data blocks. The access of a function block consists of the following: Access instruction - JU FBx absolute access of FBx (Jump Unconditional...) - JC FBx access of FBx, only when RLO=1 (Jump Conditional...) Parameter list (only necessary if block parameters are defined in the FB) Function blocks can only be accessed if they have already been programmed. When an FB-access is programmed, the programmer automatically requests the parameter list for the FB, providing block parameters have been defined in the FB. Parametrizing a function block The program in the function block specifies how the formal operands (parameters defined as "DES") are to be processed. As soon as you have programmed an access instruction (e.g. JU FB2), the programmer superimposes the parameter list. The parameter list consists of the names of the parameters, each followed by a colon (:). So-called actual operands must now be assigned to the parameters. Actual operands replace the formal operands defined when the FBs are accessed, so that the FB "actually" works with the actual operands. The parameter list must not contain more than 40 parameters

201 VISB Introduction to STEP5 PLEASE NOTE When a formal operand is later inserted in the parameter list, all the formal operands will be moved one position. Programmed formal operands within the function block therefore modify their names and also their function. The diagram below shows a detailed example for parametrizing a function block. Control program with function block Function block PB3 NAME IN1 IN2 OUT1 NAME IN1 IN 2 OUT1 :SPA FB5 :EXAMPLE :I0.0 :I0.1 :Q0.0 :JU FB5 :EXAMPLE :I1.0 :I1.1 :Q0.1 FB5 NAME :EXAMPLE DES :IN1 I BI DES :IN2 I BI DES OUT1 Q BI : :A =ON1 :A =ON2 := =OFF1 :*** Processed program : :A I0.0 :A I0.1 := Q0.0 : :A I1.0 :A I1.1 := Q0.1 Fig. 3/16: Parametrizing a function block

202 VISB Introduction to STEP5 Data blocks (DB) The data blocks are for storing data which are to be processed in the program. The following types of data are permitted: Bit pattern (representation of system states), Numbers in hexadecimal, binary or decimal form (time values, calculation results), Alphanumeric characters (message texts). Programming data blocks Programming of a DB begins with the specification of a block number between 2 and 255. The DB0 is reserved for the operating system; the DB1 for parametrizing internal functions. The data are stored word-by-word in this block. If the information contains less than 16 bits, the higher-value bits are filled up with zeros. Data entry begins with data word 0 and is continued in ascending order. A data block can accept up to 256 data words. The contents of the data words can be accessed or modified with load or transfer operations. Entry Stored values 0000 : KH = A13C DW0 A13C 0001 : KT = DW : KF = DW Fig. 3/17: Example of the contents of a data block In the SB 50, data blocks can also be created or deleted in the control program

203 VISB Introduction to STEP5 Program processing with data blocks A data block must be accessed in the program with the command C DBx (x=no.) before it can actually be used. A data block remains valid within a block, until another data block is accessed. If a jump is made back to the higher-order block, the data block valid before the block access is then valid again. When OB1, 13, 21, 22 are accessed by the operating system, no DB counts as being accessed. PB7 PB20 DB3 DB3 : C DB3 : :JU PB20 : : :L DW1 :T DW2 :C DB11 :L DW1 :T DW2 DB3 DB11 Fig. 3/18: Validity range of data blocks SIMATIC Integrated PLEASE NOTE Data blocks are not remanent and are overwritten after POWER ON by the initialization values stored in the EEPROM (see chapter 3.3)

204 VISB Introduction to STEP5 Function of the DB1 The DB1 is intended for the use of special functions in the SB 50 and is already integrated. It contains preset values (default values), which can either be transferred or modified by the user. The DB1 is evaluated once at the start, i.e. after POWER ON or after a STOP - RUN transition (see chapter 3.8)

205 VISB Introduction to STEP5 Program processing Some of the organization blocks (OBs) take over the task of structuring and managing the control program. These OBs can be grouped according to the following tasks: OBs for START program processing OB for cyclic program processing OBs for time-controlled program processing In addition, there are also OBs in the SB 50 which offer functions similar to the integrated function blocks (e.g. PID control algorithms). These OBs are described in the chapter "Integrated blocks." A summary of all OBs is to be found in table 3/13. Processing Blocks Cyclic OB1 Time-controlled OB13 Integrated FBs FB230, , 250, 251 GRAPH5 (fast version) SB Parametrizable FBs FB Table 3/13: Programming possibilities Summary of the programming possibilities In the following chapters you will see which special organization blocks the SB 50 makes available for the above-listed tasks and what must be taken into account in their programming

206 VISB Introduction to STEP5 START program processing In START processing, the operating system of the SB 50 automatically accesses a START-OB, providing it has been programmed. OB21 (with manual new start) or OB22 (with automatic new start after POWER ON, providing the SB 50 was previously in operating mode RUN). If you have programmed the START-OBs, this program will be processed before the cyclic program processing. It is therefore suitable e.g. for the (once only) presetting of certain system data. If the relevant START-OB is not programmed, the SB 50 will branch directly into the operating mode RUN. Features of the start blocks (OB21, OB22) The red and green LEDs light up The timers are processed The cycle monitoring is not activated

207 VISB Introduction to STEP5 Programmer function RUN Return of power supply Delete process image table of non-remanent timers, counters and flags, interpret the DB1 Delete process image table of non-remanent timers, counters and flags, interpret the DB1 Sart up routine Process the OB21 Process the OB22 Release outputs START Process image input table Process the OB1 Process image output table Cyclic program processing Fig. 3/19: Settings of the start reaction The two following examples show how a START-OB can be programmed

208 VISB Introduction to STEP5 Example STL Explanation After the restoration of the power supply, it must be checked that the supply voltages for the decentral periphery have reached their nominal values before the cyclic program is executed. A timer loop is programmed in OB22 for this purpose. OB22 :AN T 1 ACCU1 is charged with a :L KT 50.1 time constant of 5 s. Timer 1 is started. :SE T 1 Name :JU FB 1 :SCHLEIFE BE FB1 Name :SCHLEIFE LOOP :A T 1 :JC=LOOP :BE At the end of the 5 seconds, cyclic program execution is started (in OB1). Example 1: Programming OB22 Example STL Explanation After new start with operating mode switch, the flag bytes are to be assigned with value 0. The other flag bytes are to be kept, as they contain important machine functions. :L KF 0 Value 0 is loaded into :T MW 0 ACCU1 and transferred to flag words 0, 2, 4, 6, :T MW 2 and 8. :T MW 4 :T MW 6 :T MW 8 :BE Example 2: Programming OB

209 VISB Introduction to STEP5 Cyclic program processing The OB1 is accessed cyclically by the operating system. If you wish to program in a structured manner, you should only program jump functions (block accesses) in the OB1. The blocks accessed (PBs, FBs and SBs) should contain completed function units, so that understanding is simplified. Each cyclic program processing starts a monitoring period at the beginning (cycle trigger). If the cycle trigger is not touched again during the monitoring period, the SB 50 will enter the "STOP" status and will block the outputs and valves. The monitoring time is approx. 300 ms. If the control program is so complex, that it cannot be processed in the 300 ms prescribed, you can extend the monitoring time in the control program in the SB 50 with the aid of the OB31 (trigger at a later stage). The monitoring time is exceeded, e.g. if you program an endless loop or if there is a fault in the SB 50. Cycle trigger Control program Transfer data Fig. 3/20: Cyclic program processing

210 VISB Introduction to STEP5 Time-controlled program processing Time-controlled program processing exists when a (periodical) time signal causes the SB 50 to interrupt the cyclic program processing and to process a specific program. When this program has been processed, the SB 50 returns to the point of interruption in the cyclic program and continues processing at that point. Prerequisites for time-controlled program processing Time-controlled program processing is only possible when the following conditions are fulfilled: Organization block 13 must be programmed. The SB 50 must be in the POWER-ON status and operating mode "RUN" must be set. The alarm processing must not be blocked (by STEP 5 operation "IA"). The OB13 access interval is set at 10 (DB1). The OB13 is available for time-controlled program processing. The OB13 is processed by the operating system at intervals determined by the user. It is not possible to modify the access intervals during the cyclic program processing. If the OB13 has not been programmed, the cyclic program processing will continue. Setting the access interval The access interval can be set in the DB1 under the block identifier TFB (parametrized). Times from 10 ms to ms (in 10 ms steps) can be set. An interval of 100 ms is preset for the OB

211 VISB Introduction to STEP5 Interrupt possibilities The OB13 can interrupt the cyclic program after each STEP 5 instruction. The OB13 cannot interrupt: - The operating system - The current time-controlled program processing (OB13) Block/release access With the command "IA", the OB13 access can be blocked, with "RA" released again. A request for access can be stored during an access block. "RA" is preset (see chapter 3.7). Saving data If a time-controlled OB uses "scratch flags" which are also used in the cyclic control program, these flags must be saved in a data block during the OB processing. PLEASE NOTE Also with the time-ob13 processing, the block nesting depth must not exceed 16 levels

212 VISB Introduction to STEP5 Direct access to the local as well as to the decentral periphery by means of the STEP 5 commands LPB, LPW, TPB and TPW is possible during the time-obs (OB13). Direct periphery access is effected (or rather produced) by the use of an alternative process image table, the so-called alarm process image table. Use of the commands for direct access to the periphery during the cyclic program process will lead to a RUN/STOP transition, whereby the ISTACK-bit NNN will be set. No periphery access is permitted in the start OBs. The alarm process image table is treated as follows: - If the OB13 is programmed, then the process image output table will be duplicated in the alarm process image output table. - At the beginning and end of the OB13 there is a complete transfer of the alarm process image table

213 VISB Introduction to STEP 5 Processing blocks The previous sections of this manual have described how blocks can be used. Chapter 3.7 lists all operations which are required for working with blocks. Blocks already programmed can of course be modified again. The individual possibilities for modification are only described briefly. The necessary work steps are described in detail in the operating instructions of the programmer. Program modifications Program modifications can be carried out in the following programmer functions, irrespective of the block type. INPUT OUTPUT STATUS In these functions you can undertake the following modifications: Delete, insert or overwrite instructions Insert or delete networks Block modifications Program modifications refer to the contents of a block. However, you can delete or overwrite complete blocks. The blocks are not, however, deleted in the program memory, but simply made invalid. These memory locations cannot be re-written. This fact can mean that new blocks are no longer accepted. The error message "No memory space" is then shown on the programmer. You can eliminate this error by compressing the SB 50 memory

214 VISB Introduction to STEP 5 Compressing the program memory You can "clear up" the internal program memory with the programmer function COMPRESS. The diagram below shows what happens in the program memory with the operation COMPRESS. Internally one block per cycle is shifted. The prerequisite for the function COMPRESS is that the SB 50 is in operating mode RUN. Program memory RAM Program memory RAM Blocks Valid Invalid Compress Entry possible Entry not possible Free memory locations Fig. 3/21: Meaning of compressing If a power failure occurs whilst a block is being shifted because of compressing, and if the shifting of the block cannot be completed, the SB 50 remains in the STOP status with the error message NINEU. In addition to NINEU, the bits BSTSCH and SCHTAE are set in the ISTACK. Remedy: Overall reset SIMATIC Integrated PLEASE NOTE If the programmer function "COMPRESS" is triggered in operating mode "STOP" of the SB 50, the blocks are transferred from the RAM to the EEPROM of the SB

215 VISB Introduction to STEP 5 Representing numbers STEP 5 gives you the possibility of working with numbers in five different representations: Decimal numbers from to (KF) Hexadecimal numbers from 0000 to FFFF (KH) BCD-numbers (4 tetrads) from 0000 to 9999 Bit pattern (KM) Constant byte as two-byte representation (KY) per byte

216 VISB Introduction to STEP

217 VISB STEP 5 operations 3.7 STEP 5 OPERATIONS PN

218 VISB STEP 5 operations Contents 3.7 STEP 5 OPERATIONS Basic operations Linking operations Memory operations Load operations Transfer operations Time operations Counting operations Arithmetical operations Comparison operations Block access operations Jump-back functions Zero operations Stop operations Picture structure operations Supplementary operations Linking operations Bit and memory operations Timing and counting operations Load and transfer operations Jump operations Other operations System operations Evaluating CC 0 and CC

219 VISB STEP 5 operations 3.7 STEP 5 OPERATIONS The programming language STEP 5 distinguishes between three types of operations: Basic operations Basic operations include functions which can be performed in organization, program, step and function blocks. Except for addition (+F), subtraction (-F) and the organizational operations, they can be input and output in all three programming languages (STL, CSF and LDR). Supplementary operations Supplementary operations contain complex functions such as substitution instructions, test functions, shift and conversion operations. They can only be input and output in the programming language STL. System operations System operations have direct access to the operating system. Only an experienced programmer should use them. The system operations can only be input and output in the STL programming language

220 VISB STEP 5 operations Basic operations The scope of basic operations consists of the following categories of instructions: - Linking operations - Memory operations - Loading and transferring - Timing operations - Counting operations - Arithmetical functions - Comparison operations - Block access operations - Other operations The scope of basic operations can be used in all blocks (OB/PB/FB/SB). The basic operations are listed and described in the following table:

221 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Link operations A I,Q N J N AND link: interrogate for F N J N signal status "1" T N J N C N J N AN I,Q N J N AND link: interrogate for F N J N signal status "0" T N J N C N J N O I,Q N J N OR link: interrogate for F N J N signal status "1" T N J N C N J N ON I,Q N J N OR link: interrogate for F N J N signal status "0" T N J N C N J N O N J N OR link of AND functions A( N J N AND link of bracket expressions (6 bracket levels) O( N J N OR link of bracket expressions (6 bracket levels) ) N J N Brackets closed (conclusion of a bracket expression) Memory operations S I,Q J N J Set the operand at value "1" F J N J R I,Q J N J Set the operand at value "0" F J N J = I,Q J N J Value of the RLO is assigned to F J N J the operand * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/14: Link operations / memory operations

222 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Load operations L IB N N N 11 Load input byte of PII into ACCU1 L QB N N N 11 Load output byte of PIQ into ACCU1 L IW N N N 15 Load an input word of PII into ACCU1: Byte n ACCU1 (bits ) Byte n+1 ACCU1 (bits 0...7) L QW N N N 15 Load an output word of PIQ into ACCU 1: Byte n ACCU1 (bits ) Byte n+1 ACCU1 (bits 0...7) L PY N N N 39 Only permitted in OB13. Load an input byte of the digital/ analogue entries from alarm PII into ACCU1 L PW N N N 42 Only permitted in OB13. Load an input word of the digital/ analogue entries from alarm PII into ACCU1 L FY N N N 11 Load a flag byte into ACCU1 L FW N N N 15 Load a flag word into ACCU1: Byte n ACCU1 (bits ) Byte n+1 ACCU1 (bits 0...7) L DL N N N 33 Load left byte of a data word of current data block into ACCU1 L DR N N N 35 Load right byte of a data word of current data block into ACCU1 L DW N N N 35 Load a data word of the current data block into ACCU1 * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/15: Load operations

223 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Load operations (continued) L KB N N N 5 Load a constant (1-byte number) into ACCU1 L KS N N N 5 Load a constant (2-characters in ASCII format) into ACCU1 L KF N N N 5 Load a constant (fixed point number) into ACCU1 L KH N N N 5 Load a constant (hexa-code) into ACCU1 L KM N N N 5 Load a constant (bit pattern) into ACCU1 L KY N N N 5 Load a constant (2-byte number) into ACCU1 L KT N N N 5 Load a constant (time value) into ACCU1 (BCD) L KC N N N 5 Load a constant (counter value) into ACCU1 (BCD) L T,C N N N 14 Load a timer or counter value (binary coded) into ACCU1 LC T N N N 58 Load timer or counter value (BCD) C N N N 59 into ACCU1 * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/16: Load operations

224 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Transfer operation T IB N N N 5 Transfer contents of ACCU1 to an input byte (into PII) T QB N N N 5 Transfer contents of ACCU1 to an output byte (into PIQ) T IW N N N 12 Transfer contents of ACCU1 to an input word (into PII): ACCU1 (bits ) byte n; ACCU2 (bits 0...7) byte n+1 T QW N N N 12 Transfer contents of ACCU1 to an output word (into PIQ): ACCU1 (bits ) byte n; ACCU2 (bits 0...7) byte n+1 T PY N N N 41 Only permitted in OB13. Transfer contents of ACCU1 into alarm PIQ with regard to PIQ T PW N N N 45 Only permitted in OB13. Transfer contents of ACCU1 into alarm PIQ with regard to PIQ T FY N N N 5 Transfer contents of ACCU1 to a flag byte T FW N N N 12 Transfer contents of ACCU1 to a flag word T DL N N N 25 Transfer contents of ACCU1 to a data word (right byte) T DR N N N 26 Transfer contents of ACCU1 to a data word (left byte) T DW N N N 34 Transfer ACCU1 to a data word * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/17: Transfer operations

225 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Time operations SP T J N J 64 Start a time (stored in ACCU1) as impulse SE T J N J 64 Start a time (stored in ACCU1) as extended impulse SD T J N J 65 Start a time (stored in ACCU1) with switch-on delay SS T J N J 65 Start a time (stored in ACCU1) storing with switch-on delay SF T J N J 64 Start a time (stored in ACCU1) storing with switch-off delay R T J N J 21 Counter operations CU C J N J 35 Counter counts 1 forwards CD C J N J 40 Counter counts 1 backwards S C J N J 62 Set a counter R C J N J 17 Reset a counter Arithmetical functions +F N N N 19 Add two fixed point numbers: ACCU1 + ACCU2. Result can be evaluated with CC 1/CC 0/O V -F N N N 22 Subtract two fixed point numbers: ACCU2 - ACCU1. Result can be evaluated with CC 1/CC 0/O V * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/18: Time/counter operations and arithmetical functions

226 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Function description Comparison operations!=f N J N 21 Compare two fixed point numbers for equality: If ACCU1 = ACCU2, then RLO = "1". CC 1/CC O is influenced ><F N J N 22 Compare two fixed point numbers for inequality: If ACCU1 >< ACCU2, then RLO = "1". CC 1/CC O is influenced >F N J N 22 Compare two fixed point numbers, which is larger?: If ACCU2 > ACCU1, then RLO = "1". CC 1/CC O is influenced >=F N J N 22 Compare two fixed point numbers, larger or equal?: If ACCU2 >= ACCU1, then RLO = "1". CC 1/CC O is influenced <F N J N 22 Compare two fixed point numbers, which is smaller?: If ACCU2 < ACCU1, then RLO = "1". CC 1/CC O is influenced <=F N J N 22 Compare two fixed point numbers, smaller or equal?: If ACCU2 <= ACCU1, then RLO = "1". CC 1/CC 0 is influenced Table 3/19: Comparison operations

227 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description block access operations JU PB N N J 66 Absolute (unconditional) jump to a program block JU FB N N J 63 Absolute (unconditional) jump to a function block JU SB N N J 66 Absolute (unconditional) jump to a step block JC PB J J J 68 Conditional jump to a p program block JC FB J J J 70 Conditional jump to a function block JC SB J J J 68 Conditional jump to a step block C DB N N N 30 Access a data block G DB N N J 109 Create or delete a data block Jump-back operations BE N N J 42 Block end (conclude a block) BEU N N J 42 Block end absolute (uncon ditional), (cannot be used in organization blocks) BEC Y Y 1) 43 Block end conditional Zero operations NOP0 N N N 0 Zero operation (all bits deleted) NOP1 N N N 0 Zero operation (all bits set) Stop operations STP N N N 1 Stop: cycle will be completed. Error identifier STS in ISTACK will be set * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? 1) RLO is set to "1" Table 3/20: Block access operations

228 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Picture structure operations BLD 130 BLD 131 BLD 132 BLD 133 BLD 255 Process time in µs Function description N N N 0 Picture structure command for the programmer: Create an empty line with Carriage Return N N N 0 Picture structure command for the programmer: Switch to statement list (STL) N N N 0 Picture structure command for the programmer: Switch to function chart (CSF) N N N 0 Picture structure command for the programmer: Switch to ladder diagram (LDR) N N N 0 Picture structure command for the programmer: End segment (network) * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/21: Picture structure operations

229 VISB STEP 5 operations Supplementary operations Basic operations can be programmed in all blocks. By means of the "supplementary operations", the scope of operations can be extended. However, the following limitations apply to these operations: They can only be programmed in function blocks. They can only be represented in STL. The supplementary operations consist of the following categories of instructions: - Substitution operations - Conversion operations - Shift operations - jump operations - Block/release alarm - Decrement/increment - Processing operation - system operations Supplementary operations are described in the following tables

230 VISB STEP 5 operations Operation (STL) Permitted operands Link operations A = Formal operand I,Q,F,T,C AN = O = ON = Formal operand I,Q,F,T,C Formal operand I,Q,F,T,C Formal operand I,Q,F,T,C RLO* Process time in µs Function description N J N AND link: Interrogate formal operand for signal status "1" (parameter type: BI) N J N AND link: Interrogate formal operand for signal status "0" (parameter type: BI) N J N OR link: Interrogate formal operand for signal status "1" (parameter type: BI) N J N OR link: Interrogate formal operand for signal status "1" (parameter type: BI) AW N N N 16 AND link (bit-by-bit): ACCU2 with ACCU1. Result in ACCU1. CC 1/CC 0 are affected. OW N N N 16 OR link (bit-by-bit): ACCU2 with ACCU1. Result in ACCU1. CC 1/CC 0 are affected XOW N N N 16 Exclusive-OR link (bit-by-bit): ACCU2 with ACCU1. Result in ACCU1. CC 1/CC 0 are affected * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/22: Link operations

231 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Bit operations TB T,C N J N 5 Check bit of timer or counter word for signal status "1" TB D N J N 32 Check bit of data word for signal status "1" TB RS N J N 5 Check bit of data word in range of system data for signal status "1" TBN T,C N J N 5 Check bit of timer or counter word for signal status "0" TBN D N J N 33 Check bit of data word for signal status "0" TBN RS N J N 5 Check bit of data word in range of system data for signal status "0" SU T,C N N J 6 Set bit of a timer or counter word unconditionally SU D N N J 34 Set bit of a data word unconditionally RU T,C N N J 6 Reset bit of a timer or counter word unconditionally RU D N N J 34 Reset bit of a data word unconditionally Memory operations S = Formal operand I,Q,F RB = Formal operand I,Q,F RD = Formal operand T,C = = Formal operand I,Q,F J N J Set a formal operand (with RLO = "1") (parameter type: BI) J N J Reset a formal operand (with RLO = "1") (parameter type: BI) J N J Reset a formal operand (digital) (with RLO = "1") J N J The value of the RLO is assigned to the status of the formal operand (parameter type: BI) * 1 RLO abhängig? 2 RLO beeinflussend? 3 RLO begrenzend? Table 3/23: Bit and memory operations

232 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Timer and counter operations FR T J N J 20 Release timer/counter for new start. If RLO = 1, with - "FR T" the timer will be started C J N J 16 - "FR C" the counter will be set, counted forwards or backwards. FR = SP= SD= SEC= SSU= SFD= Formal operand T Formal operand C Formal operand T Formal operand T Formal operand T Formal operand C Formal operand T Formal operand C Formal operand T Formal operand C J J N N J J Release formal operand (timer/counter) for new start. If RLO = 1, with - "FR T" the timer will be started - "FR C" the counter will be set, counted forwards or backwards. J N J 114 Start a timer (formal operand) as impulse. Value is stored in ACCU1. J N J 116 Start a timer (formal operand) with switch-on delay. Value is stored in ACCU1. J J N N J J Start a timer (formal operand) as extended impulse with the value stored in ACCU1, or set a counter (formal operand) with the following specified counter value. J J N N J J Start a timer (formal operand) as stored switch-on delay with the value stored in ACCU1, or increment a counter (formal operand). J J N N J J Start a timer (formal operand) as switch-off delay with the value stored in ACCU1, or decrement a counter (formal operand). * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/24: Timer and counter operations

233 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Load and transfer operations L = Formal operand I,Q,F,T,C Process time in µs Function description N N N Load the value of the formal operand into the ACCU1. Parameter type: BY, W; Further actual operands: DL, DR, DW L RS N N N 15 Load a word from the range LD = LW = Formal operand T,C Formal operand T= Formal operand I,Q,F system data into the ACCU1. N N N 86 Load the value of the formal operand in BCD code into the ACCU1. N N N 34 Load the bit pattern of a formal operand into the ACCU1. (parameter form D; parameter type KF, KH, KM, KY, KC, KT, KZ) N N N Transfer the contents of ACCU1 to the formal operand (parameter type: BY, W); additional actual operands: DR, DL, DW Conversion operations CFW N N N 4 Form the complement of 1 of ACCU1 CSW N N N 19 Form the complement of 2 of ACCU1. CC 1/CC 0 and OV are affected. Shift operations SLW SRW Parameter n= Parameter n= N N N 12 + n 8 Shift contents of ACCU1 to the left by the value specified in the parameter. Free positions will be filled with "0". CC 1/CC 0 are affected. N N N 12 + n 8 Shift contents of ACCU1 to the right by the value specified in the parameter. Free positions will be filled with "0". CC 1/CC 0 are affected. * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/25: Load and transfer, conversion and shift operations

234 VISB STEP 5 operations Operation (STL) Permitted operands Jump operations JU= Symbol addr. max. 4 char. JC= Symbol addr. max. 4 char. JZ= Symbol addr. max. 4 char. JN= Symbol addr. max. 4 char. JP= Symbol addr.max. 4 char. JM= Symbol addr. max. 4 char. JO= Symbol addr. max. 4 char. RLO* Process time in µs Function description N N N 5 Jump absolute (unconditional) to jump address Y Y Y 1) 7 Conditional jump to symbol address (If RLO = "0", RLO "1" will be set) N N N 9 Jump if zero: only made if CC1=0 and CC0=0. The RLO is not modified. N N N 12 Jump if not zero: only made if CC >< 0. The RLO is not modified. N N N 9 Jump if plus sign: only made if CC 1=1 and CC 0=0. The RLO is not modified. N N N 9 Jump if minus sign: only made if CC 1=0 and CC 0=1. The RLO is not modified. N N N 7 Jump if "overflow": only made if display OVERFLOW is set. The RLO is not modified. * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? 1) RLO will be set to "1" Table 3/26: Jump operations

235 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Other operations IA N N N 1 Block alarm: time OB13 processing is blocked RA N N N 19 Release alarm: cancels effect of operation AS D N N N 4 Decrement the low byte of ACCU1 (bit 0...7) by value n (n= ) I N N N 3 Increment the low byte of ACCU1 (bit 0...7) by value n (n= ) DO= Formal operand N N J 95 Process block: (Only C DB, JU OB, JU PB, JU FB, JU SB can be substituted) Actual operands: C DB, JU OB, JU PB, JU FB, JU SB DO DO DW FW N N N N N N Process word: the following operation is combined with the parameter specified in the word (OR link) and evaluated Permitted operations: L FY/FW/IB/QB/IW/QW L DL/DR/DW T FY/FW/IB/QB/IW/QW T DL/DR/DW JU OB/SB/FB/PB, C DB A F, S F, R F, =F, SS T, SE T, R T, A T, AN T, SLW, SRW * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/27: Other operations

236 VISB STEP 5 operations Operation (STL) Permitted operands RLO* Process time in µs Function description Set operations SU RS N N J 6 Set bit in range of system data unconditionally RU RS N N J 6 Reset bit in range of system data unconditionally Load and transfer operations LIR N N N 50 Load register (0: ACCU1, 2: ACCU2) with contents of a memory word indirectly (addressed by ACCU1) TIR N N N 50 Transfer register (0: ACCU1, 2: ACCU2) into memory word indirectly (addressed by ACCU1) TNB Parameter n= N N N 52 + n 16 Byte-by-byte block transfer (number of bytes ) T RS N N N 12 Transfer a word to the range of the system data. Block access and jump back operations JU OB N N J 61 Access organization block absolute. JC OB J J J Access organization block conditionally. Arithmetical operations ADD BK N N N 10 Add byte constant to ACCU1 ADD KF N N N 10 Add fixed point constant (word) to ACCU1 Other operations STS N N N 2 Stop command: program processing is discontinued immediately after the command TAK N N N 10 Swap the contents of ACCU1 and ACCU2 * 1 RLO dependent? 2 RLO affected? 3 RLO reloaded? Table 3/28: System operations

237 VISB STEP 5 operations CC 1 CC 0 Arithmetical operations Digital link operations Comparison operations Shift operations Conversion operations 0 0 Result = 0 Result = 0 ACCU2 = ACCU1 0 1 Result --- ACCU2 < 0 < ACCU1 1 0 Result Result ACCU2 > 0 >< 0 > ACCU1 Table 3/29: Evaluation of CC 1 and CC 0 Shifted bit --- = Result < 0 Shifted bit Result = 1 >

238 VISB STEP 5 operations

239 VISB Integrated blocks 3.8 INTEGRATED BLOCKS PN

240 VISB Integrated blocks Contents 3.8 INTEGRATED BLOCKS DB1: parametrizing internal functions Rules for parametrizing DB Transferring the DB1 parameters Parameter block ERT Localizing parametrizing errors Parameter block SDP Parameter block TFB Parameter block SL DB1 parametrizing for reference Integrated function blocks Code converter: B4 -FB Code converter: 16 -FB Multiplier: 16 -FB Divider: 16 -FB Analogue value adaption blocks Reading the analogue value -FB Outputting the analogue value -FB Diagnosis SINEC L2-DP -FB Diagnosis of local periphery -FB Integrated organization blocks Cycle trigger -OB PID-control algorithm -OB SB 50 to SINEC L Parametrizing for data exchange Coordinating the data exchange Sending data Structure of coordinating byte KBS Receiving data Structure of coordinating byte KBE Special features

241 VISB Integrated blocks 3.8 INTEGRATED BLOCKS DB1: parametrizing internal functions The SB 50 has functions which you can set (parametrize) according to your needs. These functions are as follows: Enable data exchange via SINEC L1 Modify access interval for time-controlled program processing (OB13) Set system characteristics Determine address for parametrizing error code You can parametrize these functions in data block DB1. Structure and presettings of DB1 SIMATIC Integrated To simplify parametrizing, a DB1 with preset values (default parameters) has already been fitted into the SB 50. If you load the default DB1 from the SB 50 into the programmer after "Overall reset" and display this on the screen, it will be composed as follows: "DB1" must stand in front of the parameter blocks, followed by at least one filling character (empty space or comma). 0: KC =,DB1 #SL1: SLN 1 SF DB2 ; 12: KC =, DW0 EF DB3 DW0 KB ; 24: KC =,E MB100 KBS MB101 ; 36: KC =, PGN 1 ;# SDP: NT 12 ; 48: KC =,8 ; TFB: OB ; E ; 60: KC =,ND Fig. 3/22: DB1 with default parameters

242 VISB Integrated blocks Block identifier Meaning/presetting This preset DB1 contains a parameter block for every function. Each parameter block begins with a block identifier (with black background in fig. 3/22), followed by a colon. There must be at least one filling character after the colon. The individual parameters for the relevant functions are grouped together within the parameter blocks. The semi-colon (;) indicates the end of a parameter block. The following parameter blocks exist for the SB 50 (see table 3/30). DB1 Start identifer SL1 SINEC L1: Parameter block for SINEC L1 connection Default setting: included in comment line SDP System Dependent Parameter: Parameter block for system characteristics Default setting: 128 internal timers are processed TFB Timer Function Blocks: Parameter block for time-controlled program processing: Default setting: OB13 is accessed every 100 ms ERT Error Return: Address for parametrizable error code No default setting END End identifier of the DB1 Table 3/30: Parameter blocks and their identifiers The sequence of parameter blocks in DB1 is not specified, individual blocks are separated from each other with a semi-colon (;). There must be at least one filling character between the semi-colon and the next block identifier

243 VISB Integrated blocks Rules for parametrizing the DB1 We have listed here all the rules which you must observe if you wish to modify parameters or complete whole parameter blocks in DB1. It is essential that these rules be observed, as otherwise the SB 50 cannot "understand" what you have entered. Start identifier "DB1" The DB1 must begin with the entry "DB1". The three characters must not be separated from each other by filling characters. After the start identifier there must be at least one filling character. Empty spaces and commas are generally permitted as filling characters. After the start identifer together with filling character, there comes the block identifer of a parameter block. The sequence of the parameter blocks in DB1 is optional. The block identifier marks a block of parameters which belong together. The block identifer "SL1" stands e.g. for SINEC L1 parameter. There must be a colon (:) immediately after the block identifier. If the colon is missing, the SB 50 will jump over this block and issue an error message. There must be at least one filling character after the block identifier concluded with a colon. A parameter name follows Parameter names are names for individual parameters within a parameter block. Within a block the first four characters of a parameter name must be different from each other. There must be at least one filling character after the parameter name. At least one argument belongs to each parameter name. An argument is either a number or a STEP 5 operand which you must enter. If several arguments belong to a parameter name, they must be separated from each other by at least one filling character. At least one filling character must also follow the last argument

244 VISB Integrated blocks The end of the block must be marked by a semicolon (;). There must be at least one filling character after the semi-colon. If you forget the semicolon, there will be an error interpretation in the SB 50. Further parameter blocks can then follow. The end identifier "END" must be entered at the end of the last parameter block. This marks the end of the DB1. If you forget to enter this end identifier, there will be an error in the SB 50. Comments can be entered in the DB1. Comments can be inserted at any point where a filling character may also reside. The comment character is the lattice symbol (#). This must reside at the beginning and at the end of a comment. The text between two comment characters must not contain any further lattice symbol. At least one filling character must follow

245 VISB Integrated blocks Transferring the DB1 parameters to the SB 50 In contrast to the other data blocks, the DB1 is only processed once, during a new start of the SB 50. This has been done in order to equip the DB1 for certain very special functions. Such a special function is the parametrizing of the SB 50 with the aid of the DB1. Parametrizing means that you enter in data block DB1 the parameters for the internal functions with which your SB 50 is to work. These entries in the DB1 are only transferred to the operating system during a new start of the SB 50. Every modification in the DB1 must therefore be followed by a corresponding new start. This can be accomplished by switching from - POWER OFF POWER ON or from - STOP RUN The SB 50 takes over the parameters of the DB1 and stores them in the system data range. In order to store the parameters remanent in the EEPROM memory, the programmer function "Compress automation device" must be carried out in operating mode "STOP" (see chapter 3.6). PLEASE NOTE The SB 50 remains in STOP if it detects a parametrizing error during the start. The red LED will then light up on the operating panel and an error address of the DB1 will be shown in the ISTACK

246 VISB Integrated blocks Parameter block ERT: Recognizing and eliminating parametrizing errors. If there has been an error in parametrizing and if the SB 50 does not enter the RUN status, there are two possibilities of recognizing parametrizing errors: - With the aid of a parametrizing error code or - By means of the analysis function "ISTACK" Both possibilities are described below. Interrogate parametrizing error code If you have specified a start address for the parametrizing error code in parameter block "ERT:" of the DB1, then you can interrogate the cause of the error and its location under this address. The complete error code occupies 10 data words or 20 flag bytes. In the following examples and tables we assume that the error code is stored in a data block as from data word 0. The error code then occupies DW0...DW9. In the operand range "Flags", this corresponds to FY0...FY

247 VISB Integrated blocks Example: ERT: ERR DB3 DW0 ; You have specified the start address DB3 DW0 in the parameter block "ERT:" and the DB1 thus parametrized has already been accepted by the automation device. You then continue parametrizing the DB1. After transferring the modified DB1 parameters to the SB 50, you ascertain that the latter remains in STOP. You assume the cause of the STOP to be a parametrizing error. In order to find the error, you must output the DB3 on the programmer. The complete contents of the DB3 will appear on the screen; the data words DW0 to DW9 contain the parametrizing error code. The diagram below shows what your screen might look like. Directly after the screen display you will find a complete list of parametrizing error codes and their meaning. 0: KH= : KH= : KH= : KH= : KH= : KH= : KH= : KH= : KH= : KH= : KH= 0000 Fig. 3/23: Screen display with parametrizing errors

248 VISB Integrated blocks Error cause (Which error has occurred?) DL DR Error location (In which parameter block has the error occurred?) No error Not defined Start or end identifier missing Not defined Non concluded comment Not defined before END; semi-colon before END missing. Block identifier syntax error SL1: SINEC L1 Argument syntax error TFB: Timer function block Range exceeded or not SDP: System data parameter reached in an argument Parameter combination not 07 permitted Not defined 08 Not defined 09 DB does not exist 10 Insufficient space in DB ERT: Error Return Table 3/31: Parametrizing error code and its meaning Localizing parametrizing errors in the "ISTACK" If, during the start, the SB 50 detects a parametrizing error in the DB1, the SB 50 will remain in the STOP status and enter the error in the ISTACK. The ISTACK contains both the absolute (error) address and the relative (error) address. The STEP address counter (SAC) in the ISTACK then shows either: - The address containing the incorrect entry or - The position directly in front of the address containing the incorrect entry. These are byte addresses

249 VISB Integrated blocks Parameter block SDP: Determining the system characteristics in the DB1 In this parameter block you can set the number of the 128 internal timers which are to be continually processed by the processor. (Parameter NT 128) The parameter for the internal timers "NT" has been set so that all 128 timers are processed continually. You can reduce the processing time required for this by parametrizing only the number of internal timers that you actually need. Parameter block TFB: Set access interval "time-controlled program processing" In this parameter block you can set the access interval of the time-controlled program processing. The values ms are possible here, whereby steps of 10 ms are specified (e.g. 110, 120, 130, etc.). Entering the value 100 means an access and processing of the OB13 at intervals of 100 ms. Parameter block SL1: Data exchange via SINEC L1 In this parameter block you can specify the addresses of the data fields (transmitter and receiver) and the assigned coordination bytes. A detailed description can be found in the chapter " SINEC L1"

250 VISB Integrated blocks Parameter Argument Meaning DB1 parametrizing for reference Block identifier: SL1: SINEC L1 SLN SF EF KBE KBS PGN p DBx DWy DBx DWy FYy FYy p Slave number Position of transmitter Position of receiver Position of coordination byte "Receive" Position of coordination byte "Transmit" PG bus number p = x = y = Default setting: comment Block identifier: TFB: Timer Function block OB13 p Interval (ms) during which the OB13 is accessed and processed p = (in 10 ms steps) Default setting: 100 ms Block identifier: ERT: Store for error information of the DB1 evaluation (10 errors needs 2 bytes) ERR FYy or DBx DWy Address for the parametrizing error code x = y = No default setting Block identifier: SDP: System Dependent Parameter NT p Number of timers which are processed p = Default setting: 128 Table 3/32: Parameterizing of the DB1 for reference

251 VISB Integrated blocks Integrated function blocks Some standard function blocks are integrated in the SB 50. These blocks can be accessed in the control program with the commands "JU FB x" or "JC FB x" - x stands for the block number. Block no. FB240 FB241 FB242 FB243 FB250 FB251 Block name COD:B4 COD:16 MUL:16 DIV:16 RLG:AE RLG:AA Access length (in words) Processsing < 0.8 < 1.0 < time (in ms) Diagnostic blocks Block no. FB230 FB231 Block name S_DIAG P_DIAG Access length 4 4 (in words) Processing time (in ms) < 6.5 < 2 Table 3/33: Summary of the integrated function blocks Code converter : B4 -FB240- With this function block, a BCD number (4 tetrads) with sign can be converted into a fixed point binary number (16 bits). 2-tetrad numbers must be transferred to 4-tetrad numbers before conversion. If a tetrad is not in a BCD-defined range, the FB240 will output the value "0". There is no error bit display. Parameter Meaning Type Assignment STL BCD BCD number I W :JU FB240 SBCD Sign of BCD I BI "1" for "-" NAME :COD:B4 number "0" for "+" BCD : DUAL Fixed point Q W 16 bits "0" SBCD : number (KF) or "1" DUAL : Table 3/34: Access and parametrizing of the FB

252 VISB Integrated blocks Code converter : 16 With this function block, a fixed point binary number (16 bits) can be converted into a BCD number with the sign taken into account. 8-bit binary numbers must be transferred to 16-bit words before conversion. Parameter Meaning Type Assignment STL DUAL Binary number I W :JU FB241 SBCD Sign of BCD Q BI "1" for "-" NAME :COD:16 number "0" for "+" DUAL : BCD2 BCD number Q BY 2 tetrads SBCD : 4th & 5th tetrads BCD2 : BCD1 BCD number Q W 4 tetrads BCD1 : tetrads Table 3/35: Access and parametrizing the FB241 Multiplier : 16 -FB241- -FB242- With this function block, two fixed point binary numbers (16 bits) can be multiplied. The result is represented by a fixed point number (32 bits). In addition, the result is interrogated for zero. 8-bit numbers must be transferred to 16-bit words before multiplication. Parameter Meaning Type Assignment STL Z1 Multiplier I W :JU FB242 Z2 Multiplicand I W NAME :MUL:16 Z3=0 Interrogate I BI "1" if the result Z1 : for zero is zero Z2 : Z32 Result high word Q W 16 bits Z3=0 : Z32 : Z31 Result low word Q W 16 bits Z31 : Table 3/36: Access and parametrizing the FB

253 VISB Integrated blocks Divider : 16 -FB243- With this function block, two fixed point binary numbers (16 bits) can be divided. The result (quotient and rest) is represented by two fixed point binary numbers (16 bits each). In addition, the result and the divisor are interrogated for zero. 8-bit numbers must be transferred to 16-bit words before division. Parameter Meaning Type Assignment STL Z1 Dividend I W :JU FB243 Z2 Divisor I W NAME :DIV:16 OV Overrun display Q BI "1" if overrun Z1 : FEH Error Q BI "1" if division by Z2 : zero OV : FEH : Z3=0 Interrogate for Q BI "1":quotient is Z3=0 : zero zero Z4=0 : Z4=0 Interrog. for zero Q BI "1":rest is zero Z3 : Z3 Quotient Q W 16 bits Z4 : Z4 Rest Q W 16 bits Table 3/37: Access and parametrizing the FB

254 VISB Integrated blocks Analogue value adapter blocks -FB250 and FB251- The FB250 reads an analogue value of an analogue input module. It then supplies a value XA at the output in a (standard) range specified by the user. With the FB251, analogue values can be output on analogue output blocks. Values are thereby transferred from the range between the parameters lower limit "UGR" and upper limit "OGR" to the nominal range of the appropriate block. PLEASE NOTE The analogue value adapter blocks FB250 and FB251 can be used with the SF 50 as standardizing blocks for analogue blocks of the decentral periphery. Read and standardize analogue value -FB250- This function block reads an analogue value of an analogue input block and supplies a value XA at the output in a (standardized) range specified by the user. The type of analogue value representation of the block (channel type) must be specified in parameter KNKT (see table 3/38). With the parameters upper limit OGR and lower limit UGR, the user can determine the desired range

255 VISB Integrated blocks Parameter Meaning Type Assignment STL BG Slot number D KF 126 :JU FB250 KNKT Channel number D KY KY = x,y NAME :RLG:AE channel type x = BG : y = *) KNKT : OGR Upper limit of D KF OGR : output value UGR : EINZ : UGR Lower limit of D KF XA : output value FB : XA Output value Q W Standard BU : analogue value FB Error bit Q BI Is "1" if unfavourable channel or slot number or invalid channel type BU Range exceeded Q BI Is "1" if rated range is exceeded *) 3 = Absolute value repres. (4 to 20 ma) 4 = Unipolar representation 5 = Bipolar absolute value 6 = Bipolar fixed-point number Table 3/38: Access and parametrizing the FB250 Rated range Representation of analogue input block UGR OGR Range standardized by user Fig. 3/24: Standardizing scheme FB

256 VISB Integrated blocks Output analogue value -FB251- *) 0: Unipolar representation 1: Fixed-point number With this function block, analogue values can be output on analogue output blocks. Values are thereby transferred from the range between the parameters lower limit "UGR" and upper limit "OGR" to the nominal range of the appropriate block. Parameter Meaning Type Assignment STL XE Analogue value to be output I W Input word (complement of two) in range UGR...OGR NAME BG Slot number D KF KNKT Channel number D KY KY = x,y channel type x = y = *) OGR Upper limit of output value D KF UGR Lower limit of output value D KF FEH BU Error in limit specification Input value exceeded UGR or OGR Q BI Is "1" if UGR=OGR, with invalid channel/slot number or invalid channel type Q BI With "1", XE is outside (UGR; OGR) XE accepts the limit value XE : BG : KNKT : OGR : UGR : FEH : BU : :JU FB251 :RLG:AA Table 3/39: Access and parametrizing the FB

257 VISB Integrated blocks Diagnostic evaluation of local and decentral periphery Diagnostic evaluation SINEC L2-DP: S_DIAG -FB230- SIMATIC Integrated The function block S_DIAG reads the diagnostic data of the parametrized SINEC L2-DP Slave station and stores it in the parametrized data block S_DIAG. Up to 34 bytes of diagnostic data (as per PROFIBUS-DP - DIN part 3) are stored in the data block designated by the transfer parameter, beginning with the data word also specified by transfer parameter. PLEASE NOTE This function block can only be used with the SB 50 with field bus extension, i.e. the SF 50. The data block intended for receiving the diagnostic data must be created in sufficient length before the function block S_DIAG is accessed. The minimum length of the data block should be determined by the maximum length of the diagnostic information of 17 data words (34 bytes). It is therefore sensible to check the existence of a diagnostic message by interrogating the station diagnostic bits before accessing the function block

258 VISB Integrated blocks Parameter Meaning Type Assignment S_NR Station number D KY KY=x,y Slave number x=0 Direct parametrizing y= Station or Slave no. y> First station with diagnosis X<>0 y Indirect parametrizing With indirect parametrizing irrelevant DBNR Definition of destination range D KY KY=x,y Direct parametrizing x= data block number y= data word number The diagnostic data are stored as from the thus specified data word of the parametrized DB number Indirect parametrizing x= data block number y= data word number The parameters station number and destination range are stored as from the thus specified data word of the data block. The high byte of the parameter station number must have the value zero. Table 3/40: Access and parametrizing the FB230 The diagnostic data can be evaluated in the control program by interrogation of data block S_DIAG. Table 3/41 shows the structure of diagnostic data

259 VISB Integrated blocks DWn Diagnosis address (DLn) Diagnosis address + 1 (DRn) 0 Number of Slave station which supplies the diagnosis Number of subsequent diagnostic bytes 1 Station status 1 Station status 2 2 Station status 3 Master address 3 Depending on manufacturer information 4 Header Code-specific diagnostics 5 Code-specific diagnostics Code-specific diagnostics Code-specific diagnostics Code-specific diagnostics Table 3/41: Structure of diagnostic data (DIN E19245, part 3) Example :A I126.3 Fourth Slave station on SF 50 is faulty :JU FB230 Access diagnostic block S_DIAG Name :S_DIAG S_NR : KY 0.3 Direct parametrizing Interrogation of fourth Slave DBNR : KY 2.0 Store diagnostic data in DB2, as from DW0 SIMATIC Integrated Diagnostic block of local periphery: P_DIAG -FB231- With this function block, a short circuit diagnosis can be made of the outputs (local periphery) of the valve terminals with output blocks. An FW ( ) or DW ( ) serves as transfer parameter in which the byte number of the first short-circuited output in the low byte, and the bit number of the first short-circuited output in the high byte of the input parameter is stored

260 VISB Integrated blocks PLEASE NOTE Function block FB231 can only be used with a valve terminal with output blocks. This should be called at the end of cyclic program execution (OB1). Evaluation can only be made if the short-circuit is displayed with I7.2 = "1" in the diagnostic byte of the local periphery (IB7). A short-circuited output must be reset by the user when the short circuit has been eliminated. Parameter Meaning Type Assignment QUIT Reset the short-circuited output I BI The detected short-circuited output is reset if the input parameter QUIT has signal status "1". A_NR Short-circuited output Q W Table 3/42: Access and parametrizing the FB231 In this word the first short-circuited output of the local periphery of an output block is transferred to the control program. Data are stored in format KY KY = x,y x = bit number of output y = byte number of output Example :A I7.2 Short circuit of an output :JU FB231 Access block P_DIAG Name :P_DIAG QUIT : F202.0 Reset output A_NR : FW200 Transfer output :L KY3.2 Mask for output Q2.3 :L FW200 :!=F :A I7.2 := F21.3 Error message, short circuit Q

261 VISB Integrated modules Integrated organization blocks Cycle trigger OB31 By means of a "cycle monitor", the time course of cyclic program processing can be controlled. If program processing lasts longer than the cycle monitoring time set of 300 ms, then the SB 50 will enter the STOP status. This can occur when: - The control program is too long - An endless loop is programmed By accessing the OB31, the cycle monitor can be triggered again at any point in the control program, i.e. the cycle monitoring time is activated again. Access - Condition: on the programmer SYSTEM COMMANDS "YES" - Enter at any point in the control program JU OB31 Programming An instruction within the OB31 is sufficent, e.g. "BE", to activate the re-triggering. Further instructions are possible

262 VISB Integrated blocks PID control algorithm OB251 A PID control algorithm is integrated in the operating system of the SB 50. With the aid of the organization block OB251, you can use this for your own purposes. Before accessing the OB251, you must open a data block (regulator DB) which contains the control parameters and other control-specific data. The PID algorithm is accessed in a particular time pattern and forms the positioning variable. The more accurately the scanning time, the more accurately the regulator can fulfil its tasks. The control parameters specified in the regulator DB must be adapted to the scanning time. You should always access the OB251 in the time OB (OB13). Time OBs can be set at access intervals of 10 ms to ms. The maximum processing time of the PID control algorithm is 1.7 ms. OB13 Time-controlled processing C DBn JU OB BE OB251 PID control algorithm DBn Controller data block DW DW49 Fig. 3/25: Accessing the OB251 PID control algorithm The quasi-continuous regulator has been designed for control paths such as occur, e.g. in process technology as pressure, temperature or flow control devices. (see Bibliography - Manual of AG S5-95U)

263 VISB Integrated modules SB 50 to SINEC L1 SINEC L1 is a bus system for coupling SIMATIC S5 automation devices. It operates on the Master-Slave principle. Detailed information on the method of operation of the SINEC L1 bus system is to be found in the manual "SINEC L1". Previous knowledge of the operation of the SINEC L1 is essential here. The SB 50 can be coupled as a slave directly to the SINEC L1. Connecting the SB 50 to the L1 bus cable In order to connect the SB 50 to the L1 bus cable you will require a bus terminal BT 777 as a level converter. Proceed as follows: - Connect the L1 bus cable to the bus terminal BT Supply bus terminal BT 777 with 5 V terminal C=+5 V ( V; 0.3 A); terminal D=earth/ground PLEASE NOTE You should also refer to the section "Bus terminal for external Slaves" in the SINEC L1 manual, as from edition 5, chapter If there is a power failure on the SB 50, the 5 V supply to the bus terminal must also be switched off (otherwise bus functions are not possible). - Connect the plug of the bus terminal cable to the socket for PG/OP/SINEC L

264 VISB Integrated blocks Parametrizing the SB 50 for data exchange The SB 50 requires the following information for performing the data exchange via the L1 bus: - Where are the data to be transmitted? (data block or in flag range) Brief designation: transmitter, abb. SF - Where are the data to be received? (data block or in flag range) Brief designation: receiver, abb. EF - Where is coordinating information for sending data to be stored? (e.g. the message "Release transmitter for transmitting") Brief designation: coordinating byte transmit, abb. KBS - Where is coordinating information for receiving data to be stored? (e.g. the message: "Received data can be read") Brief designation: coordinating byte receive, abb. KBE and (if programmer functions are to "RUN" via the L1 bus) - programmer bus number. These parameters can be set in the DB1 parameter block. It is sensible to proceed as follows: - A default DB1 has been integrated in the operating system of the SB 50. Certain parameters there are pre-assigned for data exchange via the SINEC L1. Load the default-db1 into your programmer function transfer, source: automation device, destination: FD (programmer)

265 VISB Integrated modules - Search for the SINEC L1 parameter block, the block designation is "SL1:" for the connecting socket PG/OP/SINEC L1. Special feature of the SB 50 The SINEC L1 parameter block is enclosed in comment symbols (#) and cannot be interpreted in this form by the SB 50. Therefore overwrite the comment symbols in front of the block designation (SL1:) and after the last SINEC L1 parameter (PGN 1) with an empty space. - Edit the default parameters according to your specifications. In doing so you must not modify the syntax. Example (default): The SB 50 is to participate on the SINEC L1 bus as slave number 1 - Transmitter in DB2 as from data word 0 - Receiver in DB3 as from data word 0 - Coordinating byte transmit is flag byte Coordinating byte receive is flag byte Programmer bus number should be 1 Table 3/43 shows the default parameters and the parameter specifications which are also permitted

266 VISB Integrated blocks Block identifier: SL1: Parameter Argument (default) SLN 1 SLN x x= SF DB2DW0 SF DBxDWy x= y=0.255 EF DB3DW0 EF DBxDWy x= y=0.255 KBE MB100 KBE MBz z= or KBE DBxDWy x= y= KBS MB101 KBS MBz z= or KBE DBxDWy x= y= PGN 1 PGN x x= SINEC L1 Meaning Slave No. of the SB 50 Position of transmitter Position of receiver Table 3/43: Parametrizing the interface for SINEC L1 Position of "Receive coordination byte" Position of "Transmit coordination byte" ProGrammer bus Number (necessary for programmer functions via L1 bus) Transfer the modified DB1 to the SB 50; you thereby overwrite the default DB1. If you now trigger a STOP-RUN transition or a POWER ON - POWER OFF transition, the SB 50 will accept the modified parameters and place them in the system data range. PLEASE NOTE In order to store the parameters remanent in the EEPROM memory of the SB 50, the programmer function "COMPRESS" must be performed in operating mode "STOP"

267 VISB Integrated modules Coordinating the data exchange in the control program When parametrizing has been completed, the control program must be created for data exchange. The control program must here access coordinating information which the operating system makes available in the coordinating bytes. Transmitter (source) KBS Receiver (destination) KBS Control program for data exchange Transmitter Receiver L1 BUS Transmitter Receiver Control program for data exchange KBE KBE Fig. 3/26: Data exchange between transmitter and receiver (principle)

268 VISB Integrated blocks Sending data Prerequisites for sending data - The position of the transmitter has been parametrized in the DB1. - Transmitted data and additional information (length of transmitted data ("net data") and destination slave number) are transferred to the transmitter. Fig. 3/27 shows which information must be stored where in the transmitter. Example 1: Transmitter in flag range (as from FY1) Example 2: Transmitter in data block (as from DW1) FY1 FY2 FY3 Example 1 Length of "net data" (in bytes (1...64) Number of receiver 0 = Master = Slaves 31 = Broadcast Data ("net data") max. 64 bytes Example 2 DL DR DW1 Length of "net data" Number of receiver DW2 1st. data 2nd. data DW3 3rd. data... FY66 DW33 63rd. data 64th. data Fig. 3/27: Structure of transmitter

269 VISB Integrated modules Bit KBS S 5 5 S F Structure of coordinating byte "Transmit" (KBS) Fig. 3/28 shows the structure of the coordinating byte "Transmit" (KBS). 0: No error 1: Error in last data transfer 0: No telegram 1: Request bus interrupt for this message (telegram) 5 Without meaning S Control bit F Error message 0: Program can process transmitter 1: Release transmitter to send Fig. 3/28: Structure of coordinating byte "Transmit" (KBS) The control program for the transmitting process should be structured as follows: - Check bit 7 in the KBS, to see if transmitting is now taking place (providing the SB 50 is transmitting, bit 7 of the KBS is set. The transmitter must not be modified in this phase and no new transmission may be started). - If bit 7 in the KBS is reset: start the transmitting process by setting bit 7 in the KBS. - If bit 7 has been reset by the operating system after the transmitting process, evaluate the error

270 VISB Integrated blocks By setting bit 4 in the KBS (telegram), you can achieve the following: - the transmitting programmer gives this telegram priority (a telegram not yet sent can be overwritten) and - the transmission is treated as a telegram by the receiver. If there is an error, the operating system will set bit 0 of the KBS. The error message is not valid until bit 7 in the KBS is reset. Receiving data Prerequirements for receiving data The positions of the receiver and of the coordinating byte "Receive" (KBE) have been parametrized in DB1. Fig. 3/29 shows which information must be stored where with the receiver. FY1 FY2 FY3 Length of "net data" (in bytes) Number of receiver 0 = Master = Slaves Data ("net data") (max. 64 bytes) DL DR DW1 Length of "net data" Number of receiver DW2 1st. data 2nd. data DW3 3rd. data... Fig. 3/29: Structure of receiver

271 VISB Integrated modules Structure of the coordinating byte "Receive" (KBE) Bit KBE S 5 5 S 5 S F F 0: No error 1: Error in last data transfer 0: No slave failed 1: At least one slave failed 0: BUS in STOP 1: Bus in RUN 0: No telegram 1: Data arrive as telegram 5 Without meaning S Control bit F Error message 0: Program can access receiver (operating system has no access) 1: Operating system transfers data to receiver (program has no access) Fig. 3/30: Structure of coordinating byte "Receive" (KBE) Structure of the control program for receiving data: - Check by interrogating bit 7 in the KBE, whether or not it is sensible to read data from the receiver. Bit 7 must be "0", in order that the receiver can be read. In addition, the following errors and operating states can be interrogated by the KBE: - At least one Slave has failed - Bus in RUN (STOP) - Data package received comes as telegram

272 VISB Integrated blocks Special features If you have not reserved sufficient memory space for the receiver, the memory space available will be filled up completely (flag range up to FY255, data block up to DW255) - the remaining data received cannot be stored. The SB 50 does not create an overrun message in this case. Examples of programs for sending and receiving data are to be found in the manual SINEC L1 (chapter "Programming")

273 Programmable valve terminals with control block SB 50 / SF 50 Part 4: System description SF 50/DP-Master PN

274 PN is included in: Manual Manual Manual

275 VISB - 50 Chapter summary The manual consists of various sections which are linked, dependent on the equipment used for the valve terminal: Part 1 Installation guidelines contains information that is not dependent on the type of valve terminal and the selected nodes Part 2a Valve terminal type 02 System description of valve terminal type 02 contains all necessary information specially required for this type of terminal Part 2b Valve terminal type 03 System description of valve terminal type 03 contains all necessary information specially required for this type of terminal Part 3 System description for SB 50 contains all PLC-specific information that is independent of the valve terminal type Part 4 Part 5 Part 6 System description for SF 50 as Master contains additional information that is required when using the PROFIBUS-DP. System description for SF 50 as DP-Slave contains additional information that is required when using the SF 50/DP-Slave (SL 50) Appendix contains additional information concerning command sets, abbreviations, accessories, literature, etc. PN I

276 VISB - 50 Notes 4-II 9706

277 VISF - 50/DP-Master Contents PN Contents 4.1 SYSTEM SUMMARY SF 50 as master module in the PROFIBUS-DP field bus system What are DP Siemens and DP Standard? Differences between DP Siemens and DP Standard What does PROFIBUS-DP comprise? Structure with electronic bus medium (two wire cable) What is a bus segment? Maximum extension of a bus segment Parameters for a bus segment Performance characteristics of the SF 50 and the components of the PROFIBUS-DP system Field bus PROFIBUS-DP Parameterization Software Requirements for operating COM PROFIBUS PROFIBUS-DP bus cable connector (from Festo) PG/PC interface component (optional) Interface component of the SF 50 (Master interface) Display and operating elements Pin allocation of the DP-Master interface Memory module of the master interface of the SF 50 master module PROFIBUS-DP bus cable connector of the SF 50 and two wire cable Line termination III

278 VISF - 50/DP-Master Contents Fitting bus cables to PROFIBUS-DP bus cable connector PROCEDURE - FROM PLANNING TO COMMISSIONING Planning the structure Structure of the field bus system Considerations, before configuring the construction using COM PROFIBUS Configuration of construction using COM PROFIBUS STEP 5 description - User programs Commissioning the field bus system BASIC CONDITIONS AND INTRODUCTION TO THE PLANNING SOFTWARE COM PROFIBUS Requirements for the operation of COM PROFIBUS Requirements for configuring the data Requirements for data transfer to the EEPROM integrated in the SF 50 DP-Master COM PROFIBUS preparations for operation with the SF 50 DP-Master Operater interface of COM PROFIBUS SAMPLE FOR THE PLANNING OF A STRUCTURE USING COM PROFIBUS Procedure Starting the COM PROFIBUS Selecting bus parameters IV 9706

279 VISF - 50/DP-Master Contents Entering host parameters Entering master parameters Entering slave parameters Selecting slave parameters Selecting slave parameters through the menu bar Selecting slave parameters through the window "Slaves Selecting slave parameters through the DP slave symbol Configuring the slave parameters Saving the plannned structure using COM PROFIBUS Saving opportunities Transferring a configured master system using the "SF 50-Download software from Festo Possible applications for the "SF 50-Download software Requirements for operating "SF 50-Download 4-69 DOS version Operation under DOS MS Windows version Operation under MS Windows Transferring a structure configured with an interface component Deleting a structure configured with the EEPROM integrated in the SF 50/DP-Master V

280 VISF - 50/DP-Master Contents 4.5 DIAGNOSIS Fault diagnosis in the PROFIBUS-DP system Fault diagnosis with the display elements Diagnosis options in the STEP 5 control program of the SF Station diagnosis Booting up the SF 50 DP-Master on the bus Requirements for booting up Booting up the SF 50 DP-Master Default parameter block Reporting in operating system data How the PROFIBUS-DP system works Power supply / mains power restoration / RUN<->STOP Reactions in relation to response monitoring Reaction times in the system VI 9706

281 VISF- 50/DP-Master 4.1 System summary 4.1 SYSTEM SUMMARY

282 VISF - 50/DP-Master 4.1 System summary Contents 4.1 SYSTEM SUMMARY SF 50 as master module in the PROFIBUS-DP field bus system What are DP Siemens and DP Standard? Differences between DP Siemens and DP Standard What does PROFIBUS-DP comprise? Structure with electronic bus medium (two wire cable) What is a bus segment? Maximum extension of a bus segment Parameters for a bus segment Performance characteristics of the SF 50 and the components of the PROFIBUS-DP system 4-11 Field bus PROFIBUS-DP Configuration software Requirements for operating COM PROFIBUS PROFIBUS-DP bus cable connector (from Festo) PG/PC interface component (optional) Interface component of the SF 50 (master interface) Display and operating elements Pin allocation of the DP-Master interface Memory module of the master interface of the SF PROFIBUS-DP bus cable connector of the SF 50 and two wire cable Line termination Fitting bus cable to PROFIBUS-DP bus cable connector

283 VISF- 50/DP-Master 4.1 System summary 4.1 SYSTEM SUMMARY SF 50 as master module in the PROFIBUS-DP field bus system The SF 50 is an SB 50 with a master module for the field bus system PROFIBUS-DP. This system consists of the following components: - Active bus slaves - Passive bus slaves - Field bus PROFIBUS-DP - PROFIBUS-DP system components The following can be inserted as active bus stations (Master): - SF 50/DP-Master, the SB 50 with a built-in Master module - The programmers PG or - PCs with an interface for the PROFIBUS-DP. The Master module of the SF 50 is produced in compliance with the DP Standard (DIN 19245, part 3) and therefore the following passive bus stations (Slaves) can be used: - The field bus valve terminals FB9, FB13 and SF 50/DP-Slave from Festo - Units of the remote peripheral system ET200, e.g. ET 200B and ET 200X from Siemens (DP Siemens and DP Standard) - Field units, including those of other manufacturers, complying with the PROFIBUS-DP Standard (DIN 19245, part 3)

284 SIEMENS PG 24VDC RUN STOP L2-DP FUSE BF VISF - 50/DP-Master 4.1 System summary PLEASE NOTE There is a separate manual for the field bus valve terminals FB9 and FB13. There are separate manuals for the remote peripheral devices ET 200U, ET 200B and ET 200X. The order number can be found in the Siemens catalogue. This chapter examines the SF 50 as a Master module and, as an example, the field bus valve terminal FB9 as a Slave module. The remote peripheral devices from Siemens are shown in the system. Programmer with PROFIBUS-DP module STEP5 Further slaves of PROFIBUS-DP ET200U COM PROFIBUS Valve terminal with field bus nodes FB9 Valve terminal with SF 50 Fig. 4/1: Components of the remote peripheral system ET

285 VISF- 50/DP-Master 4.1 System summary The inputs/outputs of the remote peripherals can be operated from the control program like the local inputs/outputs of the SB/SF 50. Communications via the field bus PROFIBUS-DP are completely taken over by the module in SF 50 and by the modules in the remote peripheral devices. The configuration of the remote peripheral systems is supported by the configuration software COM PROFIBUS. This allows the compilation of the address lists and the evaluation of diagnostic data. Faults can therefore easily be located during commissioning. What are DP Siemens and DP Standard? DP Siemens is a bus protocol that has been developed by Siemens. This bus protocol was expanded into an open and manufacturer-independent system in cooperation with the PROFIBUS user organisation. In order to differentiate between the two bus protocols, the newly produced bus protocol is called DP Standard in this manual. Differences between DP Siemens and DP Standard On the surface, there is hardly any difference between DP Siemens and DP Standard. All the operating possibilities available with a field bus valve terminal using the FB9 (DP Siemens), are also available using remote peripheral devices that comply with the DP Standard

286 VISF - 50/DP-Master 4.1 System summary The PROFIBUS-DP also offers the following advantages: - Slave stations that comply with the PROFIBUS-DP draft standard can be connected to the PROFIBUS- DP, - Masters, e. g. SF 50, that comply with the PROFIBUS-DP draft standard can communicate with the slaves developed in compliance with the standard provisions (e.g. ET200 U-DP from Siemens). What does PROFIBUS-DP comprise? The series of field bus standards PROFIBUS DIN covers a wide processing spectrum which therefore means that the bus system has universal applications. Applications range from the control and cell level to the field level. PROFIBUS-DP uses DIN 19245, part 1 and complements the provisions set out for the special applications in the sector of the remote peripherals. DIN 19245, part 1 describes the bus access and transfer protocols, together with the provisions for the necessary transfer technology. For applications in the sector of remote peripherals, where a short system reaction time is required, DIN E 19245, part 3 offers a possible solution. The main task of the PROFIBUS-DP is the rapid cyclical data exchange between the programmable controller (Master station) and the low operation peripheral devices (Slave stations)

287 VISF- 50/DP-Master 4.1 System summary PROFIBUS-DP offers the following features: - the transmission of 1024 bits I/O data with 32 slaves in less than 10 ms, - comprehensive diagnosis concept, - reduced parametising and configuration requirements. SIMATIC Integrated PLEASE NOTE The SF 50 (DP Standard) is configured using the Parameterization Software COM ET200 Windows (from v.2.x) or COM PROFIBUS. Both DP Siemens and DP Standard slaves can be operated. Structure with electronic bus medium (two wire cable) Master and slaves form stations on the PROFIBUS- DP field bus. Possible bus structures with master and slave stations are shown below. What is a bus segment? A PROFIBUS-DP system consists of at least one bus segment. This bus segment consists of at least 2 stations, one of which is an SF 50. A bus segment is the bus section between two terminating resistors. There are no branches within a bus segment

288 VISF - 50/DP-Master 4.1 System summary Maximum extension of a bus segment SIMATIC Integrated Figure 4/2 shows the maximum amount of equipment which can be fitted on a PROFIBUS-DP bus segment (= bus line) with an SF50 master station, 16 slave stations and a PG with a module for PROFIBUS-DP. The terminating resistors must be switched on at the ends of the bus line (two wire cable). Station No. 1 SF 50 Station No. 0 PG FB Station No. 15 FB Station No. 16 FB Station No. 17 SF 50 PG FB FB Valve terminal with SF 50 Programmer with module for PROFIBUS-DP Valve terminal with FB9 or ET200 or other PROFIBUS-DP slave Valve terminal with FB9 or ET200 or other PROFIBUS-DP slave with functioning terminating resistor Fig. 4/2: A PROFIBUS-DP segment with SF

289 VISF- 50/DP-Master 4.1 System summary Parameters for a bus segment One segment can hold a maximum of 18 stations, with max. one SF 50 and max. one PG with a module for PROFIBUS-DP. The maximum cable length of the PROFIBUS-DP bus segment is dependent on the baud rate (table 4/1): Baudrate (in kbit/s) Max. cable length of a segment (in m) Table 4/1: Permitted cable length of a segment

290 VISF - 50/DP-Master 4.1 System summary

291 VISF- 50/DP-Master 4.1 System summary Performance characteristics of the SF 50 and the components of the PROFIBUS-DP system The following section gives details concerning the performance characteristics and properties of the components which are available for the construction of a PROFIBUS-DP network with the SF 50 as the Master interface module. Field bus PROFIBUS DP PN The Master interface module of the SF 50 dictates the properties of the PROFIBUS-DP. The following list gives details concerning the performance characteristics of the field bus PROFIBUS-DP in connection with the Master interface of the SF 50. PROFIBUS-DP (DP Standard) and SINEC L2-DP (DP Siemens) - slaves can be connected, Multiple construction possibilities using two wire cable, 6 transfer rates: 9.6 / 19.2 / / / 500 / 1500 kbaud, Slaves automatically detect the selected transfer rate, max. 18 stations can be connected to the PROFIBUS-DP bus: - per segment, max. 18 stations, - in total, max. 2 master (one SF 50 and one programmer with an interface component for the PROFIBUS DP) - max. 16 slaves very large addressing capacity (see table 4/2), secure data transfer (hamming distance = 4), Bus function is not influenced if stations are taken offline (i.e. connection and removal of stations is possible during operation),

292 VISF - 50/DP-Master 4.1 System summary Comprehensive diagnosis options: - with fault and diagnosis LEDs - in the control program in accordance with EN Byte addresses Inputs Outputs in PII and PIO IB local inputs QB local 7 IB7 8 I local diagnosis of the valve terminal outputs IB byte I for digital, analogue and intelligent peripherals QB byte O for digital, analogue and intelligent peripherals IB126 IB I diagnosis PROFIBUS-DP Table 4/2: Addressing capacity of the SF 50 SIMATIC Integrated PLEASE NOTE The SF 50 with DP-Master interface does not allow the connection of DP-Slaves, which are not limited to a message length of 32 bytes. The SF 50 can only process a maximum of 32 bytes input and output data per DP Slave

293 VISF- 50/DP-Master 4.1 System summary Parameterization Software The operation of the parameterization software is shown below using the COM PROFIBUS as an example. The operating procedure for COM ET200 WINDOWS (v. 2.x or later) is directly transferable. The parameterization software COM PROFIBUS offers the following functions: Configuration of the bus structure Transfer of configuration data to the SF 50/ DP-Master Comprehensive equipment documentation Operating functions for all slave stations Parameterization software COM PROFIBUS Programmer PROFIBUS-DPinterface (optional) PROFIBUS-DP Valve terminal with SF 50 Fig. 4/3: Configuration of bus structure using COM PROFIBUS SIMATIC Integrated PLEASE NOTE SF 50 requires the parameterization software COM PROFIBUS or COM WINDOWS from v. 2.x or later

294 VISF - 50/DP-Master 4.1 System summary Requirements for operating COM PROFIBUS COM PROFIBUS runs on the user interface MS Windows. Prior knowledge of MS-Windows is assumed. To use COM PROFIBUS without any restrictions, you need: Operating system MS DOS (v. 5.0 or later) User interface MS Windows (v. 3.x or later) minimum 4 MB free RAM minimum 5 MB free memory on the hard drive minimum 386 processor

295 VISF- 50/DP-Master 4.1 System summary PROFIBUS-DP bus cable connector (from Festo) SIMATIC Integrated The SF 50 is an IP 65 PLC and therefore requires a bus cable connector with the protection class IP 65. This connector links the SF 50 over a two-wire, screened bus line, to the field bus valve terminal with an FB9, an ET 200 Station or another PROFIBUS-DP Slave. Fig. 4/4: PROFIBUS-DP bus cable connector from Festo

296 VISF - 50/DP-Master 4.1 System summary PG/PC interface component (optional) SIMATIC Integrated The interface component is used to transfer the configuration data from the PG/PC to the SF 50, as an EEPROM is already integrated into the SF 50. The E(E)PROM programmer and erasing device are not required with the SF 50. To transfer the data with the COM PROFIBUS to the SF 50, use one of the following interfaces: Interface Baud rate Note MPI card 9.6 kbaud to 500 kbaud MPI card is already integrated in the 720, 740 and 760 PG s DP12-ISA card 9.6 kbaud to Connecting 730, 740, 750, 770 PGs and PTs (CP 5411) 12 MBaud CP kbaud to 12 MBaud Connecting PC with PCMCIA slot NOTE The configuration data can also be transferred via the PG interface using the Festo SF 50-Download-Tool to the EEPROM integrated in the SF 50 (see chapter 4.4)

297 VISF- 50/DP-Master 4.1 System summary Interface component of the SF 50 (Master interface) The Master interface component of the SF 50 enables the remote extension of the SB 50 with the PROFIBUS-DP. SIEMENS RUN BF BF LED Display (BUS FAULT = red) STOP PG L2-DP DP-Master interface for PROFIBUS-DP Fig. 4/5: Structure of the SF 50 Display and operating elements SIMATIC Integrated Like the SB 50, the SF 50 has no operating elements. The PROFIBUS-DP Master is supplied with power through the power supply of the valve terminal and is switched to RUN or STOP through the programmer and the PLC "START/STOP" function simultaneously with the built-in PLC. PN

298 VISF - 50/DP-Master 4.1 System summary LED BF LED RUN LED STOP Significance Remedy Off Blinks Lights up Lights up Lights up Off Off Off Lights up All configured DP slaves are addressable At least one DP slave is not addressable Bus short circuit or missing terminator resistors or configuration error Off Lights up Lights up Acceleration delay or OB21/OB22 Off Off Flickers DP parameter block is being transferred within the SF 50 between the controller and communications processor or the STEP 5 user program is being saved. - Check the DP slaves and evaluate the slave diagnosis. Check the bus cable and the bus structure. After the fault is fixed, the SF 50 system must be switched off and then on again

299 VISF- 50/DP-Master 4.1 System summary Pin allocation of the DP-Master interface The remote peripheral devices are connected over the DP-Master interface to the SF 50 over the PROFIBUS-DP. The DP-Master interface is based on a 9-pin D-subsocket matching the PROFIBUS-DP. View PIN No. Signal name Designation RxD / TxD-P RTS M5V2 P5V2 - RxD / TxD-N - Functional earth - Data line B Request to send Data earth Supply Plus - Data line A - Table 4/3: Pin assignment of the PROFIBUS-DP interface Memory module of the master interface of the SF 50 SIMATIC Integrated To hold the PROFIBUS system parameters and the configuration data, a 12 KB memory area is reserved in the EEPROM of the SF 50. The EEPROM is programmed by a correct transfer of the data from the programmer to the SF 50 and can be overwritten by a new data transfer. The PT function "delete" deletes all the system parameters and configuration data in the reserved section of the EEPROM and resets them to the default values

300 VISF - 50/DP-Master 4.1 System summary Mains on SF 50 in STOP operating mode DOWNLOAD with COM PROFIBUS DOWNLOAD with Festo Download-Tool Fault? Yes Red LED "BF" lights up no Parameter block in RAM of SF 50 MAINS OFF ON or DELETE Activation of the parameter block Red LED "STOP" flickers: Parameter block is being saved Red LED "STOP" lights up: Parameter block saved in EEPROM Fig. 4/6: Transferring/saving of system parameters and configuration data

301 VISF- 50/DP-Master 4.1 System summary PROFIBUS-DP bus cable connector of the SF 50 and two wire cable Maximum cable lengths are achieved by using a two wire twisted and screened cable with the following properties: Characteristics Values Surge impedance ca Ω (f = MHz) Loop resistance 115 Ω /km Working capacitance 30 nf/km Damping 0.9 db/100 (f = 200 khz) Permissible wire cross-section for bus cable connector 0.3 mm mm 2 Permissible cable diameter 8 mm ± 0.5 mm Table 4/4: Features of the bus cable The maximum cable lengths given in table 4/5 are guaranteed with the bus cable for PROFIBUS-DP (Siemens order No. 6XV AH10). Transfer rate (kbits/s) Max. permissible cable length of the bus cable per segment (m) Without slaves, Remote segment With slaves Max. branch line capacitance (nf) Table 4/5: Length of bus cable in relation to the transfer rate The branch line capacitance must only be taken into account when the bus cable is not directly mounted on the bus cable connector (e.g. when using a bus terminal). The branch line capacitance can then be divided by the number of connected slaves

302 VISF - 50/DP-Master 4.1 System summary Example: The capacitance of the branch line used is 100 pf/m. This means that, with a transfer rate of 500 kbps, 15 slaves per 2 m of branch line can be connected. Line termination A bus segment must be closed with its surge impedance. The terminating resistor must be activated with the last bus station of a segment (for switch position on bus cable connector, see figure 4/7). The terminating resistors must be activated at the segment start (first slave, e.g. SF 50) and the segment end (last slave). PLEASE NOTE If the terminating resistors are not correctly activated this may lead to a STOP status of the bus. The remote peripherals (e.g. inputs and outputs) can then no longer be addressed. Terminating resistor OFF A B A B Terminating resistor ON Fig. 4/7: Terminating resistor switched on / off

303 VISF- 50/DP-Master 4.1 System summary Fitting bus cables to PROFIBUS-DP bus cable connector The following must be noted when connecting the cables: The same wires (green/red for PROFIBUS-DP cable) must be fitted to connection A or B (e.g. connection A is always linked with the green wire and connection B with the red wire) and The cable must be insulated in such a manner that the screening is directly underneath the pressure clamp. The connection method for the PROFIBUS-DP bus cable connector as per protection class IP 65 is described in detail in part 1, chapter 1.3, FBS-SS-9 Field bus connector assembly

304 VISF - 50/DP-Master 4.1 System summary

305 VISF- 50/DP-Master 4.2 Procedure 4.2 PROCEDURE PN

306 VISF - 50/DP-Master 4.2 Procedure Contents 4.2 PROCEDURE - FROM PLANNING TO COMMISSIONING Planning the structure Structure of the field bus system Considerations before configuring the structure using COM PROFIBUS Configuration of structure using COM PROFIBUS Writing the STEP 5 user program Commissioning the field bus system

307 VISF- 50/DP-Master 4.2 Procedure 4.2 PROCEDURE - FROM PLANNING TO COMMISSIONING This chapter offers an overview of the procedures in the field bus system PROFIBUS-DP. It is aimed at readers who have no previous experience with the PROFIBUS-DP. It is a complete guide to the manual, from planning to commissioning, and includes wiring, configuration with the COM PROFIBUS and writing the STEP 5 user program. Reading this chapter will show how to proceed with the field bus system PROFIBUS-DP of the SF 50/DP-Master and how to find further information in this manual

308 VISF - 50/DP-Master 4.2 Procedure Planning the structure This section shows what must be considered first during the planning stage. Fundamental for planning the structure is a layout: Step Task Further information 1 Distribute the inputs and outputs to the sites where they are required. 2 Arrange the inputs and outputs of the corresponding DP slaves 3 Determine the sites for the DP slaves and the programmable controller(s). 4 Calculate the distances between the sites. These calculations show the maximum attainable baud rates. Table 4/6: Structural planning Manuals on the DP slaves Manuals on the DP slaves See table 4/

309 VISF- 50/DP-Master 4.2 Procedure Structure of the field bus system This section shows what must be taken into consideration in the mechanical and electrical construction of the components. Step Task Further information 1 First determine the position of the cable channels and therefore the distance between the cables. 2 Fix the DP slaves and the programmable controllers to their positions. 3 Connect the power supply, sensors and actuators to the DP slaves. 4 Connect all bus stations with the appropriate bus cable connector to the field bus PROFIBUS-DP. 5 Activate the terminating resistor of the first and last field bus slave (of a segment). Table 4/7: Manuals for the DP slaves Manuals for the DP slaves e.g. see figure 4/7 e.g. see figure 4/

310 VISF - 50/DP-Master 4.2 Procedure Considerations before configuring the structure with COM PROFIBUS The following section shows what must be taken into consideration before using the COM PROFIBUS. There are two main possibilities for implementing the configuration with COM PROFIBUS and when writing the user program: Firstly, plan the structure with COM PROFIBUS and let it automatically assign all station numbers and addresses in the STEP 5 user program. Then print out the equipment documentation and use this as a basis for the STEP 5 user program. Configuring with COM PROFIBUS and recording the STEP 5 user program take place simultaneously. The following must be determined before initiating the configuration with COM PROFIBUS: The following must be determined before initiating COM PROFIBUS: Step Task Further information 1 Which DP slave should be assigned which station number. 2 Which addresses the DP slaves should occupy in the STEP 5 user program. 3 The requirements of the equipment determine whether response monitoring should be activated for the DP slaves. Table 4/8: COM PROFIBUS considerations See table 4/

311 VISF- 50/DP-Master 4.2 Procedure Configuring a structure using COM PROFIBUS The following chapter summarises the procedure for configuring a structure with COM PROFIBUS. To configure and save the structure, follow the method below: Step Task Further information 1 After starting COM PROFIBUS, input the parameters of the individual components to See chapter 4.4 The bus The DP-Master (characteristics of the field bus module) The host (characteristics of the PLC) 2 Configure the individual DP slaves. Input the following parameters. See chapter 4.4 Some examples are given below: Slave numbers Address identifiers (number of inputs and outputs) Addresses in the user program (parameters) Always enter the slave parameters after the master parameters, as the slave parameters may switch off the response monitoring for the DP slaves that was previously switched on with the master parameters

312 VISF - 50/DP-Master 4.2 Procedure 3 Once the configuration of the structure is complete, save the whole configuration. There are two data transfer options available: See chapter 4.4 Export the data via a PROFIBUS interface component (e.g. an MPI card) directly into the built-in EEPROM of the SF 50/DP-Master (interface PROFIBUS L2-DP). Export the data as a binary file and transfer the data using the Festo Software Tool "SF 50-Download" to the built-in EEPROM of the SF 50/DP-Master (PG interface). 4 Finally, print out the equipment documentation. Table 4/9: Configuration of construction using COM PROFIBUS

313 VISF- 50/DP-Master 4.2 Procedure Writing the STEP 5 user program Use the following information to record the STEP 5 user program: Step Task Further information 1 Which DP slaves occupy which addresses in the STEP 5 user program. Equipment documentation with COM PROFIBUS 2 How to access the remote peripherals using the STEP 5 user program. See chapter How to evaluate diagnostic messages using the FB 230 diagnostic reports. Table 4/10: Writing the STEP 5 user program See chapter 4.5 Commissioning the field bus system The decentralised peripheral system ET 200 can be activated as follows: Step Task Further information 1 Allocate a DIP-switch to each DP slave (e.g. FB9 or ET 200U) or use software (e.g. ET 200C) to assign a valid station number. 2 Activate the bus stations in a specific sequence. 3 Activate all field bus stations using the PG interface of the SF 50/DP-Master. The functions of the DP slaves can easily be tested using the function "Force Variables" in the STEP 5 programming package. See manual on the DP slaves See chapter 4.5 See chapter 3.3 Table 4/11: Commissioning the field bus system

314 VISF - 50/DP-Master 4.2 Procedure

315 VISF- 50/DP-Master 4.3 Requirements 4.3 REQUIREMENTS PN

316 VISF - 50/DP-Master 4.3 Requirements Contents 4.3 BASIC REQUIREMENTS AND INTRODUCTION TO THE COM PROFIBUS CONFIGURATION SOFTWARE Requirements for operating COM PROFIBUS Requirements for configuring the data Requirements for data transfer to the integrated EEPROM in the SF 50/DP-Master Preparing COM PROFIBUS for operation with the SF 50/DP-Master COM PROFIBUS user interface

317 VISF- 50/DP-Master 4.3 Requirements 4.3 BASIC REQUIREMENTS AND INTRODUCTION TO THE COM PROFIBUS CONFIGURATION SOFTWARE Why do you need COM PROFIBUS? Configuring software COM PROFIBUS is needed for: Configuration of the bus structure, the host, the DP-Master and the DP slaves. For writing the data (Download) to the integrated EEPROM of the SF 50/DP-Master or reading (uploading) this data. Comprehensive equipment documentation Requirements for operating COM PROFIBUS COM PROFIBUS runs on the user interface MS Windows. Prior knowledge of MS Windows is assumed. Operating system MS DOS (v. 5.0 or later) User interface MS Windows (v. 3.1.x or later) minimum 4 MB free RAM minimum 5 MB free memory on the hard drive minimum 386 processor The following section assumes the correct installation of the COM PROFIBUS. Installation instructions can be found in the information material for COM PROFIBUS provided by Siemens

318 VISF - 50/DP-Master 4.3 Requirements Requirements for configuring the data COM PROFIBUS uses type files for configuration and parametrising which contain all information, arranged according to the station model family, concerning the "appearance" of a PROFIBUS-DP station. PROFIBUS-DP stations can be: Slave stations Master stations The type files for the SF 50/DP-Master are included on a disk in this manual and must be stored in a COM PROFIBUS directory. Requirements for data transfer to the EEPROM integrated in the SF 50/DP-Master There are two different possibilities of data transfer available with the SF 50/DP-Master from the COM PROFIBUS to the integrated EEPROM of the SF 50/DP-Master: "FESTO SF 50-Download software tool to transfer a binary file created with COM PROFIBUS via the PG interface Data transfer using an interface component for PC/PT over the PROFIBUS-DP and field bus interface (L2-DP). The appropriate installation instructions are available with the interfaces. To connect the PGs/PCs to the "L2-DP interface, use the PG connecting cable from Siemens

319 VISF- 50/DP-Master 4.3 Requirements Interface Note Manufacturer and sales Integrated MPI The MPI card is already integrated Siemens AG interface in the PG720, PG740 and PG760. MPI card The MPI card is available as an ISA Siemens AG plug-in card for the PG730, PG750, PG770 or the PC. DP12-ISA card ISA plug-in card for the connection Siemens AG (CP 5411) of PG730, PG750, PG770 or PC. CP 5511 PCMCIA plug-in card for the connection of PC with a PCMCIA module slot (e.g. Notebook) Siemens AG Table 4/12: Interfaces for COM PROFIBUS

320 VISF - 50/DP-Master 4.3 Requirements Preparing COM PROFIBUS for operation with the SF 50/DP-Master SIMATIC Integrated Each PROFIBUS-DP-Master is formally described in a type file for the operation of the COM PROFIBUS. These type files contain data that enables easy input and the interrogation of limiting values and parameters within COM PROFIBUS. Some examples are given for the model files of the SF 50/DP-Master : The number of slave stations is limited to 16 slaves Address space limited to IW8 to IW124 and OW8 to OW126. To install the type files of the SF 50/DP-Master for the COM PROFIBUS, follow the instructions below: 1. Copy the file "FEFB50XD.2MH from the directory A:\SF50\COMWIN20\MASTER\ on the accompanying disk to the directory..\masters\ in COM PROFIBUS 2. Copy the files "FE-TYP3N.BMP" and "FE-TYP3S.BMP" from the directory A:\SF50\COMWIN20\BMP on the accompanying disk to the directory...\bitmaps\ in COM PROFIBUS 3. Start up COM PROFIBUS 4. Go to FILE/NEW and 5. Select SF 50/DP-Master from the selection of DP-Masters in the window "Master & host selection -> Master station type" in COM PROFIBUS 6. Station No. =

321 VISF- 50/DP-Master 4.3 Requirements Fig. 4/8: Selecting a DP-Master in COM PROFIBUS PLEASE NOTE The master type files are read by COM PROFIBUS during initialisation. If a master type file is copied into the relevant directory when COM PROFIBUS is open, it is not recognised and is displayed in the "Master & host selection window

322 VISF - 50/DP-Master 4.3 Requirements User interface of COM PROFIBUS Fig. 4/9: COM PROFIBUS user interface The COM PROFIBUS user interface includes the following standard MS Windows elements: 1. Title bar 2. Menu bar 3. Symbol bar 4. User window 5. Status bar

323 VISF- 50/DP-Master 4.3 Requirements 1. Title bar The title bar always contains the name of the application 2. Menu bar The menu bar contains the names of the various selection menus (see table 4/13). 3. Symbol bar The symbol bar contains the symbols that simplify the selection of menu commands (see table 4/13). 4. User window The user window is where the construction of the bus is implemented using the graphics symbols. Each user window contains a DP-Master where the corresponding DP slaves can be graphically arranged. Double-clicking on the symbol or the designation automatically moves the user to the window for entering individual parameters. 5. Status bar The status bar contains a short description of the current command, the current COM PROFIBUS activity or operating instructions. In addition, it shows how much address space has already been used for the inputs and outputs

324 VISF - 50/DP-Master 4.3 Requirements Menu Important commands Symbols Menu commands File Starts the configuration of a bus structure File\New Opening program files Saving and closing program files File\Open File\Save Process Saving master systems on the DP-Master (SF 50/DP-Master). Saving current master system on a binary file. Reading the master system of the DP-Master (SF 50/DP-Master). Printing equipment documentation (In menu field "Documentation open documentation window). Cutting, copying, pasting and deleting selected sections Entering bus, host, master and slave parameters Creating new Master system File\Export\ DP-Master File\Export\ Binary file File\Import\ DP-Master File\Print Configure\ New Master system Configuration Documentation Production of equipment documentation Service Setting the PG/PC interface parameters Window Changing the screen view Help Windows Help files for the theme Help \ Contents Table 4/13: Important menu fields and symbols in COM PROFIBUS

325 VISF- 50/DP-Master 4.4 Configuration 4.4 CONFIGURATION PN

326 VISF - 50/DP-Master 4.4 Configuration Contents 4.4 SAMPLE FOR THE PLANNING OF A STRUCTURE USING COM PROFIBUS Procedure Starting the COM PROFIBUS Selecting bus parameters Entering host parameters Entering master parameters Entering slave parameters Selecting slave parameters Selecting slave parameters from the menu bar 4-61 Selecting slave parameters with the "Slave" window Selecting slave parameters with the DP slave symbol Configuring the slave parameters Saving a structure configured with the COM PROFIBUS Saving methods Transferring a configured master system using the "SF 50 Download software from Festo Possible applications of the "SF 50-Download" software Requirements for operating "SF 50-Download" 4-69 Operation under DOS MS Windows version Operation under MS Windows Transferring a structure configured with an interface component Deleting a structure configured with the EEPROM integrated in the SF 50/DP-Master

327 VISF- 50/DP-Master 4.4 Configuration 4.4 SAMPLE FOR THE CONFIGURATION OF A STRUCTURE USING COM PROFIBUS The following example uses a sample structure to demonstrate configuration using the COM PROFIBUS. Two field bus valve terminals from Festo are used as slave stations with a PROFIBUS-DP connection (FB 9). The following example uses a simple structure to explain the configuration and programming of a PROFIBUS-DP system with an SF 50/DP-Master, consisting of: 1 master station: valve terminal with SF 50/ DP-Master 2 slave stations: valve terminals with FB9 Bus line from Siemens 1 SINEC-L2 bus cable connector (protection class IP 65-9-pin sub-d) for SF 50/DP-Master from Festo 3 bus cable connectors (protection class IP 65-4-pin rounded connector) for FB9 from Festo Programmer, with or without interface component (e.g. MPI) as required Basic requirements: COM PROFIBUS is installed on the programmer Type files for valve terminals with FB 9 are installed (see "FB 9 manual)

328 VISF - 50/DP-Master 4.4 Configuration Procedure Structuring the PROFIBUS-DP system: SF 50 Master station 1 8 x I 8 x I 4 x O SF 50 2 I-valves 2 M-valves FB9 Slave station No. 3 8 x I 8 x I 4 x O FB9 2 I-valves 2 I-valves 2 I-valves 2 I-valves FB9 Slave station No. 6 4 x I 4 x I 4 x O FB9 2 M-valves 2 M-valves 2 M-valves 2 M-valves Fig. 4/10: Structure of a simple PROFIBUS-DP system Using a simple example, the following shows the procedure for configuring a structure with COM PROFIBUS: Start up COM PROFIBUS Enter bus parameters Enter host parameters Enter master parameters Enter slave parameters for valve terminals with FB9 Print equipment documentation and Save and transfer the structure to the integrated EEPROM of the SF 50/DP-Master

329 VISF- 50/DP-Master 4.4 Configuration Starting the COM PROFIBUS To work with COM PROFIBUS: 1. Start up MS Windows 2. Double-click on the symbol for COM PROFIBUS. Result: COM PROFIBUS is opened. 3. Go to File/New 4. Select the "SF 50/DP-Master for the DP-Master and the associated Host. 5. Select number "1 as the station number Fig. 4/11: Selection of the DP-Master 6. Confirm by clicking "OK Result: COM ET 200 Windows creates a window with graphic symbols for the master system with the station number

330 VISF - 50/DP-Master 4.4 Configuration Fig. 4/12: DP-Master system with SF 50/DP-Master

331 VISF- 50/DP-Master 4.4 Configuration Selecting bus parameters To insert the parameters for the bus: 1. Double-click in the user window on the line "Bus designation. Result: The "Bus parameters window appears. 2. Insert a name as the bus designation 3. Select the bus profile "DP with S5-95U 4. Select a baud rate 5. Confirm by clicking "OK Result: The inserted bus parameters are stored and the screen returns to the user window

332 VISF - 50/DP-Master 4.4 Configuration Designation Significance Default settings Bus designation Enter up to 40 characters as a name for the - bus system. Bus profile DP with S5-95U: There is at least one SF 50/DP-Master on the bus DP with S5-95U Baud rate With the baud rate you can select a transfer 1500 kbaud speed of between 9.6 kbaud and 1500 kbaud. Set parameters Using this operating stage, you can change various PROFIBUS-DP parameters (see also the on-line help in COM PROFIBUS). NOTE: In normal cases no changes are necessary. - Table 4/14: Significance of the bus parameters PLEASE NOTE When using the parameterization software COM ET 200 Windows, the following message appears "To create the master, COM ET 200 Windows must comply with the set baud rate. Should the master system be accepted?. This message must be answered with "Yes. The default values are then set at - Bus profile "PROFIBUS-DP and - Baud rate " Finally, select the parameters - Bus profile "DP with S5-95U - Baud rate "

333 VISF- 50/DP-Master 4.4 Configuration Entering host parameters To enter the host specification: 1. Double-click in the user window on the line "Host designation. Result: The window "Host parameters appears Insert a name as the host designation. 3. Leave the power-up delay period as the default value and 4. Confirm by clicking "OK. Result: The host parameters entered are stored and the screen returns to the user window

334 VISF - 50/DP-Master 4.4 Configuration Designation Significance Default settings Host designation Enter up to 40 characters as a name for the - host system. Host type, in the SF 50/DP-Master Master station type and host station type are identical (like the S5-95U/DP-Master from SF 50/ DP-Master Siemens). Power-up delay The booting of the SF 50/DP-Master is maintained 20 s for the time required for all DP slaves configured by COM PROFIBUS addressed by the SF 50/DP-Master. At longest period for any given booting delay period. Reserve inputs With these parameters you can reserve input address space. Reserve outputs With these parameters output address areas can be reserved. Table 4/15: Significance of the Host parameters PLEASE NOTE When using the parameterization software COM ET 200 for Windows v. 2.1, the default value for the power-up delay period is set at "0s. This period cannot be changed (like the S5-95U/DP-Master from Siemens)

335 VISF- 50/DP-Master 4.4 Configuration Entering master parameters To complete the master parameters: 1. Double-click in the user window on the symbol for the SF 50/DP-Master. Result: The "Master parameters window appears. 2. Insert a name as the station designation. 3. Leave the response monitoring for the slaves on the default value "Yes (ticked). 4. Confirm by clicking "OK. Result: The inserted master parameters are saved and the screen returns to the user window

336 VISF - 50/DP-Master 4.4 Configuration Designation Significance Default settings Station designation Enter up to 40 characters as a name for the master system. - Host association Cannot be changed for the SF 50/DP-Master SF 50/ DP-Master Addressing method Cannot be changed for the SF 50/DP-Master Linear Error-reporting Cannot be changed for the SF 50/DP-Master None method Response monitoring for slave With the response monitoring there is the possibility that the DP slave can react to a fault from the DP-Master or to an interruption of data traffic on the bus. If the DP slave is not addressed within the configured response monitoring period, then the DP slave goes into the safe status (all outputs are set to 0 ). If the response monitoring "Yes" is selected (corresponds to a cross in the box), then this condition applies to all the DP slaves that are assigned to the DP-Master. It is however possible, e.g. for commissioning, to switch off the response monitoring for individual DP slaves (slave parameters). Yes Table 4/16: Significance of the master parameters WARNING If the response monitoring is switched off, under certain circumstances in cases of error the outputs of the corresponding DP slaves are not returned to 0. It is therefore recommended that the response monitoring is only switched off during commissioning

337 VISF- 50/DP-Master 4.4 Configuration Entering slave parameters Requirements: The type files for the Festo valve terminals, e.g. FB9 types 03-05, are installed (see relevant manuals). Definition: The slave parameters determine: The family and the type of the DP slave The designation of the DP slave The structure and the relevant DP slave addresses (Configure...) The structure of an eventual parameterizing message (Parameterize...) and Whether the error reporting mode selected for the DP-Master or the response monitoring for this DP slave should be switched off Fig. 4/13: Entering slave parameters

338 VISF - 50/DP-Master 4.4 Configuration Designation Significance Default settings Family Family of the remote peripheral units, - e.g. valves, ET 200B, ET 200X,.... Station type With the station type the precise DP slave type is selected, e.g. recognisable by the DP slave order number or stamp. Designation Enter up to 40 characters as the name for the remote peripheral unit. Response monitoring The response monitoring can be switched on or off for each DP slave. YES Error reporting mode Station number FREEZE capable SYNC capable Configure... PLEASE NOTE If the response monitoring is switched off, then under certain circumstances in cases of error the outputs of the corresponding DP slaves are not returned to 0. It is therefore recommended that the response monitoring is only switched off during commissioning. Not relevant for the SF 50/DP-Master With the PROFIBUS address each DP slave is assigned an individual number on the bus: 3 to 123 for SF 50/DP-Master Not relevant for SF 50/DP-Master - In the Configure window the magnitudes of the input and output ranges for a DP slave are set in the "Identifier and/or S5 addresses are assigned to these inputs and outputs. The precise data for the Configure window can be found in the DP slave manual. None (Allocated PROFIBUS addresses)

339 VISF- 50/DP-Master 4.4 Configuration Parameterize... In the Parameterize window specify - if the DP slave type requires it - the contents of the parameterising message, e.g. areas or diagnostic clearing for analogue DP slaves. The precise data for the Set parameters window can be found in the DP slave manual

340 VISF - 50/DP-Master 4.4 Configuration Selecting slave parameters There are various methods available for entering the slave parameters: using the Menu bar using the Slave window using the DP slave symbol in the user window Fig. 4/14: Entry options for the slave parameters

341 VISF- 50/DP-Master 4.4 Configuration PLEASE NOTE It is possible to switch directly from the graphic configuration mode to the Configure or Parameterize window of the DP slave. Configure window: Press down the Shift key and double-click on the DP slave symbol. Parameterize window: Press down the Ctrl key and double-click on the DP- save symbol. Selecting slave parameters from the menu bar To enter slave parameters for a new DP slave, 1. Select Configure/Slave parameters and confirm the desired PROFIBUS Address by clicking OK. For example: PROFIBUS Address #3 Result: The Slave parameters window appears. 2. Fill in the slave parameters. Comprehensive explanations concerning the slave parameters can be found via the Help button. For example: Selection of family: "Valves Selection of station type: "FB9 Type Confirm the slave parameters by clicking OK and exit from the window

342 VISF - 50/DP-Master 4.4 Configuration Selecting slave parameters with the "Slave window To directly enter the slave parameters for a specific DP-Slave, follow the procedure: 1. Click on the symbol for the desired DP slave family in the "Slave window. Result: The symbol of the selected DP slave family is dragged by the mouse pointer. Fig. 4/15: Selecting DP slave family 2. Click with the left mouse button on the lowest position on the bus. 3. Confirm the desired slave station number by clicking OK. Result: The Slave parameters window appears. 4. Fill in the slave parameters. Comprehensive explanations concerning the slave properties can be found in the Help files. 5. Confirm the slave parameters by clicking OK and exit from the window

343 VISF- 50/DP-Master 4.4 Configuration Selecting slave parameters with the DP slave symbol To directly enter the slave parameters for an existing DP slave, follow the procedure: Fig. 4/16: Selecting slave properties with the DP slave symbol 1. Double-click in the user window on the symbol of the desired DP slave on the bus. Result: The specific Slave parameters window appears for the desired DP slave. 2. Fill in the slave parameters. Comprehensive explanations concerning the slave parameters can be obtained via the Help button. 3. Confirm the slave parameters by clicking OK and exit from the window

344 VISF - 50/DP-Master 4.4 Configuration Configuring the slave parameters For example: To configure a specific field bus valve terminal with a FB 9 as the DP slave, follow the procedure: 1. Double-click in the user window on the symbol of the desired DP slave at the bus. Result: The specific Slave parameters window appears for the desired DP slave. 2. Switch to the Configuring window using the "Configure..." button: FB 9 types Enter the input and output data sizes in the Identifier field (see table 4/17). 4. Enter the individual identifier S5 addresses: - Either by directly entering the desired peripheral byte in the input address slot or

345 VISF- 50/DP-Master 4.4 Configuration output addresses, e.g. P008 for the S5 addresses I8.0...I8.7 or - by automatically allocating addresses by marking the slots used and clicking on the "Auto address button. NOTE An overview of the available and used S5 addresses can be seen by clicking on the "Addresses... button. 5. Confirm the "Configure: FB9 Type window and "Slave parameters by clicking "OK. Identifier Components S5-addresses Slot 0: 8 DI 8-input module I8.0...I8.7 Slot 1: 8 DI 8-input module I9.0...I9.7 Slot 2: 8 DI Status bits I I10.7 Slot 3: 8 DO 4 double pilot valves O8.0...O8.7 Slot 4: 8 DO 4 double pilot valves O9.0...O9.7 Slot 5: 8 DO 4-output module O O10.3 Table 4/17: Entering for the example - valve terminals with PROFIBUS address Configure the second field bus valve terminal FB9 in the same manner (points 1...5). Use the PROFIBUS address #6 and the data in table 4/18. Identifier Components S5-addresses Slot 0: 8 DI 4-input module I I input module I I11.7 Slot 1: 8 DI Status bits I I12.7 Slot 2: 8 DO 8 monostable valves O O11.7 Slot 3: 8 DO 4-output module O O12.3 Table 4/18: Entering for the example - valve terminals with PROFIBUS address #

346 VISF - 50/DP-Master 4.4 Configuration SF 50 Master station 1 Status I I I O SF 50 O O FB9 Slave station No. 3 Slot: I I I O FB9 O O O O FB9 Slave station No. 6 Slot: I I I O FB9 O O O O Fig. 4/17: Address allocation of the total system NOTE Unlike the slot-orientated distribution with the ET 200U from Siemens, the addresses for the FESTO valve terminals are entered using the basic guidelines (see the FB 9 manual)

347 VISF - 50/DP-Master 4.4 Configuration Saving a structure configured with the COM PROFIBUS Saving methods There are various methods of saving the structure configured by COM PROFIBUS in the SF 50/DP master: Action Menu point Reaction Where? Save whole File\Save file or COM PROFIBUS saves the whole PG configuration File\Save file as... bus construction in a program file. Transfer configuration of a master system to SF 50/DP- Master Save the configuration of a master system on the PG/PC Transfer configuration of a master system to the SF 50/DP master File\ Export\ DP-Master... File\ Export\ Binary file... FESTO SF 50-Download (extra software) COM PROFIBUS transfers only the configuration of a Master system via an interface component for PROFIBUS-DP to the SF 50/DP master COM PROFIBUS saves the configuration of a master system in a binary file with the extension "*.2BF. FESTO SF 50-Download transfers a binary file "*.2BF created in the COM PROFIBUS to the SF 50/DP master Through the "L2-DP interface in the built-in EEPROM PG Via the "PG" interface in the built-in EEPROM Table 4/19: Saving a structure configured with COM PROFIBUS

348 VISF - 50/DP-Master 4.4 Configuration Transferring a configured master system using the "SF 50-Download" software from Festo Possible applications of the "SF 50-Download" software SIMATIC Integrated The "SF 50-Download software is a simple commissioning aid used for transfering a configured master system to the built-in EEPROM of the SF 50/DP-Master. A special advantage of this software is that no additional interface components are required for PROFIBUS-DP. The transfer of the configuration data is implemented through the PG interface of the SF 50/DP-Master

349 VISF - 50/DP-Master 4.4 Configuration Requirements for operating "SF 50-Download" "SF 50-Download works in the DOS operating system or under the user interface of MS Windows. DOS version Operating system MS DOS (v. 3.1 or later). To use the "SF 50-Download software with the DOS operating system: Insert the diskette enclosed with this manual into a drive, e.g. drive A Create a new directory with the name FESTO\SF50M on your hard drive Copy all files from the directory: SF50\COMWIN20\DOWNLOAD.DOS on the disk to the newly created directory on the hard drive. Operation under DOS The program can be called up at the DOS prompt from the installation directory FESTO\SF50M as follows: SF50M.BAT [parameter 1] [parameter 2] Parameter 1 = DOS path+binary file name, e.g. C:\S5_DATA\PROJECT\test Parameter 2 = 1 for COM 1 or 2 for COM 2. [parameter 2 is optional, default = 1]. Example: SF50M C:\S5_DATA\PROJECT\test

350 VISF - 50/DP-Master 4.4 Configuration... The binary file test.2bf is transfered via the COM2 interface to the SF 50/DP-Master. The extension "2BF" is applied automatically and must not be entered in parameter 1. MS Windows version MS Windows 3.1 or higher Minimum 386 processor To use the "SF 50-Download software with the MS Windows operating system, Insert the disk enclosed with this manual into a drive, e.g. drive A Select MS Windows in the file manager From the disk supplied, select the file "SETUP.EXE in directory: SF50\COMWIN20\DOWNLOAD.WIN e.g. on drive A: Result: The installation program for "SF 50-Download is opened. Follow the installation instructions Result: SF 50-Download will be installed on the PC or PG

351 VISF - 50/DP-Master 4.4 Configuration Operation under MS Windows Basic requirements: A master system with SF 50/DP-Master has been configured and saved under COM PROFIBUS. 1. Export the PROFIBUS-DP configuration within the program package COM PROFIBUS using the Menu commands -> FILE\EXPORT\binary file. Insert a file name of your choice. The extension "2BF" of the file is automatically added and indicates that this is a binary file. Example: test.2bf 2. Change to the corresponding program group in the program manager, e.g. FESTO software, and 3. Double-click on the symbol for "SF 50-Download Result: The following program window opens: Fig. 4/18: Fig. 4/18: "SF 50 download program window

352 VISF - 50/DP-Master 4.4 Configuration 4. Select COM1 or COM2 for the interface of the PC to which the programming cable for STEP 5 is connected. This will normally be COM1 (Default). 5. Click on the "Download (PG) screen. Result: A window will appear for selecting the new binary file. 6. Selected the dessired binary file. By clicking on the "OK" screen a DOS window is opened and the binary file is transfered to the EEPROM of the SF 50/DP master. The following actions are thereby implemented: Compression of the binary file... PC installs temporary files (name.2cf) Toggling the operating mode from RUN to STOP... LED "RUN" = off, LED "STOP" = red DELETION of node... S5 Program is deleted from the RAM and EEPROM Transfer of configuration from PC to EEPROM... LED "BF" blinks once, LED "STOP" flickers. If the process has been correctly implemented, an error message appears in the DOS window. "Parameter transfer to AG successfully concluded. Press any key to continue." If the process has been incorrectly implemented, the following error message appears on the DOS window Follow the instructions given

353 VISF - 50/DP-Master 4.4 Configuration Transferring a structure configured with an interface component To save the configuration data in the built-in EEPROM, follow the procedure below: 1. Select with the COM PROFIBUS: File\ Export\DP master. 2. Insert the current baudrate of the DP master. (Default value after deletion = 19.2 kbaud). PLEASE NOTE Limitations when using the COM PROFIBUS and the MPI interface: A maximum baudrate of 500 kbaud can be selected in the window "DP card bus parameters" for the MPI card. If the DP master is currently operating at kbaud, the SF 50/DP-Master must be deleted before transfer of the configuration data over the MPI interface (default value after deletion = 19.2 kbaud). Insert the baudrate of 19.2 kbaud in the "DP card bus parameters " window. 3. Insert the current station number of the DP master (default value after deletion = TLN1). Result: The SF 50/DP-Master goes to STOP

354 VISF - 50/DP-Master 4.4 Configuration If the export of the configuration data was successful, the configuration data is compressed and saved in the built-in EEPROM (STOP-LED flickers). If the export of the configuration data was not successful, then the SF 50/DP-Master will continue to work with the old bus parameters of the EEPROM. If the EEPROM is empty, default values are used. After a STOP-RUN transfer, the DP master works with the new configuration data. Deleting a structure configured with the EEPROM integrated in the SF 50/DP master The PROFIBUS-DP configuration data in the built-in EEPROM of the SF 50/DP-Master can be deleted or modified in the following manner: Deletion of the STEP 5 - user program by using the STEP 5 function "Object/Blocks/Delete in the PLC/All blocks/all modules in the operating mode,,stop (see chapter 3.3). Overwriting the data by saving a new configured structure. PLEASE NOTE The standard parameter block of the SF 50/DP- Master is activated after the DELETION, and therefore allows access to the programmer with built-in interface components for the PROFIBUS-DP and COM PROFIBUS on the SF 50/DP-Master

355 VISF - 50/DP-Master 4.4 Configuration Sample program for STEP 5: OB1: Network 1: :JU PB10 :JU PB11 :BE PB10 Network 1 Station #3 -> Station #6 :A I 8.0 When I 8.0 is set := Q 12.0 then set output O 12.0 :BE PB11 Network 1 Station #6 -> Station #3 :A I 11.0 When I 11.0 is set := Q 8.0 then set output O 8.0 :BE

356 VISF - 50/DP-Master 4.4 Configuration

357 VISF - 50/DP-Master 4.5 Diagnosis 4.5 DIAGNOSIS PN

358 VISF - 50/DP-Master 4.5 Diagnosis Contents 4.5 DIAGNOSIS Fault diagnosis in the PROFIBUS-DP system Fault diagnosis using the display elements Diagnosis options in STEP 5- Control program of the SF Station diagnosis Booting the SF 50/DP-Master on the bus Requirements for booting up Booting up of the SF 50/DP-Master Default parameter block Message in the operating system data How the PROFIBUS-DP system functions Current supply / system recovery / RUN<->STOP Reactions depending on response monitoring Reaction times in the PROFIBUS-DP system

359 VISF - 50/DP-Master 4.5 Diagnosis Fault diagnosis in the PROFIBUS-DP system This chapter contains instructions on fault determination through the display elements of the SF 50. In addition, fault diagnosis using a STEP 5 program is described. Fault diagnosis with the display elements SIMATIC Integrated The display elements on the front panel of the SF 50 provide the first information concerning the type of fault. The following figure shows the significance of the fault display elements. SIEMENS RUN STOP BF BF LED display (BUS FAULT = red) PG L2-DP DP master interface for PROFIBUS-DP Fig. 4/19: Fault display elements of the SF

360 VISF - 50/DP-Master 4.5 Diagnosis LED BF LED RUN Off Lights up Blinks Lights up Lights up Off LED STOP Off Off Lights up Significance All configured DP slaves are addressable. At least one DP slave is not addressable. Bus short circuit or missing terminator resistors or configuration error. Off Lights up Lights up Power-up delay or OB21/OB22 Off Off Flickers DP parameter block is being transferred within the SF 50 between the controller and the communications processor or the STEP 5 user program is being saved. Table 4/20: Fault diagnosis with the display elements SF 50 Remedy - Check the DP slaves and evaluate the slave diagnosis. Check the bus cable and the bus structure. After the fault is fixed, the SF 50 system must be switched off and then on again

361 VISF - 50/DP-Master 4.5 Diagnosis Diagnosis options in the STEP 5 control program of the SF 50 It is possible to call up and evaluate specific diagnosis messages in the control program. SIMATIC Integrated The save stations automatically "recognise" any faults and transfer the diagnosis data to the master interface component of the SF 50. The type of message enables the SF 50 to distinguish between diagnosis data and input/output data. It is possible to systematically localise and evaluate a fault by the following methods: Diagnosis Significance Interrogations in STEP 5 "Overview diagnosis" Covers all stations, where IW126 diagnosis data exist "Station diagnosis" Evaluates the type of fault detected in accordance with EN (PROFIBUS-DP) Function module S_DIAG (FB230) Table 4/21: Diagnosis options in STEP

362 VISF - 50/DP-Master 4.5 Diagnosis SIMATIC Integrated Overview diagnosis Each bit in the IW126 diagnosis word is assigned to a slave station. If a slave station recognises a fault, then the corresponding bit is set in the IW126. The bit is reset during the call up of the FB230 function module integrated in the SF 50 and can be interrogated in the user program. The slave stations (slaves SNx...SNy) are assigned to the bits of the IW126 diagnosis word in numerically ascending order of the stations configured by COM PROFIBUS. Byte no.: IB126 IB127 Bit no.: IW126 F F F F F F F F F F F F F F F F Station 8 Station 9 Station 10 Station 11 Station 12 Station 13 Station 14 Station 15 Station 0 Station 1 Station 2 Station 3 Station 4 Station 5 Station 6 Station 7 F = "1" Error message Fig. 4/20: Construction of the IW126 diagnosis message

363 VISF - 50/DP-Master 4.5 Diagnosis Example: Slave stations: Slave number (SN) 5 / 6 / 10 / 12 / 40 / 50 / 77 / 88 / 120 / 123 Slave Bit Physical station SN 5 I126.0 Station 0 SN 6 I126.1 Station 1 SN 10 I126.2 Station 2 SN 12 I126.3 Station 3 SN 40 I126.4 Station 4 SN 50 I126.5 Station 5 SN 77 I126.6 Station 6 SN 88 I126.7 Station 7 SN 120 I127.0 Station 8 SN 123 I127.1 Station 9 Station diagnosis SIMATIC Integrated Station diagnosis is called up by the integrated function module S_DIAG (FB230) in the master interface component of the SF 50 and is made transparent to the user program by means of an assigned data block. DW Significance DL Significance DR 0 Number of the slave station where diagnosis data exist Number of the subsequent diagnosis bytes 1 Station status 1 Station status 2 2 Station status 3 Master station number 3 Manufacturer s identification Further slave-specific diagnosis (unit-, identifier- or channel-related diagnosis, always related to the DP slave) Table 4/22: Structure of the slave diagnosis

364 VISF - 50/DP-Master 4.5 Diagnosis An FB230 is assigned to each station, a data block can be used for many stations. The FB230 is specifically called up in the diagnosis overview (IW126) by the bit assigned to the station. The function module S_DIAG reads the diagnosis data of the parameterised PROFIBUS-DP slave station and stores it in the parameterised data block S_DIAG. Up to 34 bytes of diagnosis data (as specified in PROFIBUS-DP - EN 50170, part 3) can be stored in the data block designated by the transfer parameter, starting with the data word which has also been specified by the transfer parameter. PLEASE NOTE This function module is only relevant for an SB 50 with field bus expansion, namely the SF 50. The data block used for filling the diagnosis data must be compiled in sufficient length before calling up the function module S_DIAG. The minimum length of the data block must be based on the maximum length of the diagnosis information of 17 data words (34 bytes). It is useful to check for the existence of a diagnosis message by interrogating the station diagnosis bits before calling up the FB230 function module

365 VISF - 50/DP-Master 4.5 Diagnosis Parameter Significance Type Allocation S_NR Station no. or Slave number D KY KY=x,y x=0 Direct parametrisation y= Station or slave No. y> First station with diagnosis x<>0 y Indirect parameterisation with indirect parameterisation: irrelevant DBNR Definition of target area D KY KY=x,y Direct parameterisation x= data block number y= data word number The diagnosis data is filed from the data word of the parameterised DB number thus stated Indirect parameterisation x= data block number y= data word number The station number and target area parameters are filed from the data word of the data block stated. The high byte of the station number parameter must have the value zero. Table 4/23: Call-up and parameterisation of the FB

366 VISF - 50/DP-Master 4.5 Diagnosis Example: :A I SN 5 damaged :JC FB230 Call up of the diagnosisblock S_DIAG Name :S_DIAG S_NR : KY0,0 Direct parametrisation, Station 0 (e.g. slave No. #3) on the bus DBNR : KY230,0 diagnosis data will be filed in DB230 from DW0 (36 bytes) :A I SN 6 damaged :JC FB230 Call-up of the diagnosis block S_DIAG Name :S_DIAG S_NR : KY0,1 Direct parametrisation, station 1 (e.g. slave No. #6) on the bus DBNR : KY230,20 diagnosis data will be filed in DB230 from DW20 (36 bytes)

367 VISF - 50/DP-Master 4.5 Diagnosis Booting up the SF 50/DP-Master on the bus Requirements for booting up It is assumed that: The SF 50/DP-Master has been started up without using the DP master interface (see chapter 3). The DP slaves have been wired up. All DP slaves and DP-Master have been connected to the bus cable. The power supply of the DP slaves has been switched on. The DP slaves - where possible - have been switched to RUN

368 VISF - 50/DP-Master 4.5 Diagnosis Booting up the SF 50/DP-Master Stromversorgung für SF 50 Switch on einschalten power supply for SF 50 Betriebsartenschalter Set operating mode auf to STOP schalten Ein-/Ausschalter am SF 50 Is DP-Parametersatz the parameter block available auf EEPROM on EEPROM? vorhanden? No Nein YesJa DP-Parametersatz parameter block wird transfered in das SF to 50SF 50 (BF übertragen LED flickers) (LED BF flimmert) Configured projektierte DP-Slaves slaves werden are entered into diagnosis in Übersichtsdiagnose overview eingetragen Default-Parametersatz Default parameter block is accepted wird eingestellt (see next (siehe page) nächste Seite) Switch Betriebsart operating von mode STOP from in RUN STOP to RUN (automation schalten (AG-Neustart) device new start) Delete Löschen process des Prozeßabbildes, image, DP data, der DPnon-remanent Daten, der nichtremanenten periods, counters, Zeiten, flags in the SF Zähler, 50 Merker im SF 50 SF SF nimmt accepts DP-Slaves the DP in slaves den Bus from auf the diagnosis summary Switch Betriebsart operating von mode STOP from in RUN STOP to RUN (automation schalten (AG-Neustart) device new start) Delete Löschen process des Prozeßabbildes, image, DP data, der DPnon-retentive Daten, der nichtremanenten periods, counters, Zeiten, flags in the SF Zähler, 50 Merker im SF 50 BF LED turns LED off BF erlischt (no DP (kein master DP-Master-Betrieb) operation) SF 50 detects trägt ansprechbare addressable DP-Slaves slaves from the aus diagnosis Übersichtsdiagnose overviewaus Have all Haben DP alle DP-Slaves slaves quittiert? quit? Ja Yes No Nein Booting up Hochlaufverzögerung delay abgelaufen? expired? Yes Ja Nein No BF LED BF turns erlischt; off, data Datenaustausch exchange between zwischen the SF und and dezentraler the remote peripherals Peripherie can kann occur stattfinden Fig. 4/21: Booting up the SF 50/DP-Master

369 VISF - 50/DP-Master 4.5 Diagnosis Default parameter block The default parameter block is accepted by the SF 50/DP-Master, if there are no DP parameter blocks available on the integrated EEPRO M (see figure 4/21). The default parameter block contains: Station number = 1 Baud rate = 19.2 kbaud No DP slave parameterised Highest active station number = 126 Reporting in operating system data The system data word 17 of the SF 50/DP-Master (absolute address: 5D22H) contains the following information concerning the DP parameter block: 00H = Default parameter block is valid 01H = User parameter block is valid The allocation of the remaining systems data can be found in chapter

370 VISF - 50/DP-Master 4.5 Diagnosis How the PROFIBUS-DP system works Power supply / mains power restoration / RUN<->STOP Action First time power supply is turned on Mains power restoration Bus running The following chapter shows how the PROFIBUS-DP system - arranged according to specific events - behaves in relation to the SF 50/DP-Master: Requirements SF 50/DP-Master DP-Slave STOP STOP -> RUN RUN RUN -> STOP STOP -> RUN It is not possible to access the inputs /outputs of the remote peripherals. Diagnosis data, DP inputs and outputs are deleted. Diagnosis data and DP inputs are updated. DP outputs are written. DP outputs are initialized (if the OB 21 start up has been programmed). Diagnosis data, DP inputs and outputs are deleted. Diagnosis data and DP inputs are updated. DP outputs are written. It is not possible to access the inputs/outputs of the remote peripherals. It is possible to access the inputs/ outputs of the remote peripherals. Outputs are set to 0 Inputs are read. Outputs are updated. Inputs are read. Outputs are updated. Outputs are set to 0 Inputs are read. Outputs are updated. Table 4/23: Reactions of the SF 50/DP-Master

371 VISF - 50/DP-Master 4.5 Diagnosis Reactions in relation to response monitoring The following table shows the reactions produced when bus communication to one or more DP slaves is interrupted or when a DP slave fails. Failed DP slaves: response monitoring Reaction of the SF 50/ DP-Master No SF 50/ DP-Master stays in RUN mode Yes SF 50/ DP-Master stays in RUN mode Reaction of the SF 50/ DP-Master and the failed DP slaves SF 50/DP-Master: Inputs are set to 0. Outputs are updated internally DP-Slave: Outputs are frozen. SF 50/DP-Master: Inputs are set to 0. Outputs are updated internally. DP slave: Outputs are set to 0 after the end of the address monitoring period. Reaction of the SF 50/DP-Master and the remaining DP slaves SF 50/DP-Master: Inputs and outputs are further updated. DP slaves: Outputs are further updated. SF 50/DP-Master: Inputs and outputs are further updated. DP slaves: Outputs are further updated. Table 4/24: Reactions in relation to response monitoring

372 VISF - 50/DP-Master 4.5 Diagnosis

373 VISF - 50/DP-Master 4.5 Diagnosis Reaction times in the system Figure 4/22 shows the data paths and table 4/25 shows the delay times between the SF 50/DP-Master and the input and output modules of the remote peripherals. SF 50 master station Slave stations PROFIBUS-DP Fig. 4/22: Data paths in the remote peripheral system with SF 50 1 Through the user program in the PLC 2 Between the CPU and Master interface component of the SF50/DP-Master 3 Via the PROFIBUS-DP between the Master interface component and the DP slave 4 Within the slave interface component 5 Between the slave interface component and the valves and/or input/output components 6 Within the input/output components 7 Via the PROFIBUS-DP between the DP slaves

374 VISF - 50/DP-Master 4.5 Diagnosis Delay time... Relevance... through the user program in the PLC Dependent on the user program... between the PLC and field bus master Only important with high baud rates and word type access to consistent data (e.g. analogue I/O)... via the PROFIBUS-DP Important with high baud rates and comprehensive data messages... within the FB 9 through data messages Dependent on the number of output bytes (coming from the FB 9)... between the FB 9 and valves, or I/O components (via the peripheral bus) Dependent on the number of valves, or I/O components... the input/output modules Dependent on the unit... from FB 9 to ET 200 Negligible Table 4/25: Summary of the delay times

375 Programmable valve terminals with SB 50 / SF 50 control block Part 5: SF 50 / DP slave system description PN

376 PN is shown in: Manual Manual Manual

377 VISF - 50/DP Slave Chapter summary The manual consists of various sections compiled according to the equipment used for the valve terminal: Part 1 Installation guidelines contains information irrespective of the type of valve terminal or node selected. Part 2a Valve terminal type 02 System description of valve terminal type 02 contains all necessary information specifically required for this type of terminal. Part 2b Valve terminal type 03 System description of valve terminal type 03 contains all necessary information specifically required for this type of terminal. Part 3 System description for SB 50 contains all PLC-specific information irrespective of valve terminal type. Part 4 Part 5 Part 6 System description for SF 50 as Master contains additional information that must be observed when using the PROFIBUS-DP. System description for SF 50 as DP-Slave contains additional information that must be observed when using the SF 50/DP slave (SL 50). Appendix contains additional information concerning command sets, abbreviations, accessories, literature, etc. PN I

378 VISF - 50/DP Slave Notes 5-II 9706

379 VISF - 50/DP Slave Contents Contents 5.1 System description SF 50/DP-Slave with PROFIBUS-DP interface Application possibilities using the SF 50/DP-Slave with PROFIBUS-DP interface Structure and operating mode of the SF 50/DP-Slave Display and operating elements Pin assignment of the PROFIBUS-DP interface Data transfer via the PROFIBUS-DP interface of the SF 50/DP-Slave Data transfer properties with the SF 50 as a DP slave Principal operating mode of data transfer Structure of the extended peripheral area of the SF 50/DP-Slave Access to send and receive data Access to user-specific parameterization data Specifying the configuration of the SF 50/DP-Slave with COM ET 200 in the DP-Master Operation of COM ET 200, v. 4.x Operation of COM ET 200 Windows Entering properties of the send and receive data using decimal code configuration bytes Device master file Determining the user-specific parameterization data in the parameter message of the DP-Master PN III

380 VISF - 50/DP Slave Contents 5.4 Parameterising the PROFIBUS-DP interface of the SF 50/DP-Slave in DB Parameterization process DB1 parameters for the SF 50/DP-Slave with PROFIBUS-DP interface Entering parameters in the DB1 and in the SF 50/DP-Slave DB1 parameterization faults for PROFIBUS-DP interface Sample program for the SF 50 as a PROFIBUS-DP slave Cyclic program for the SF 50 as DP slave Commissioning of the SF 50/DP-Slave Starting-up behaviour of the SF 50/DP-Slave Starting-up PROFIBUS-DP Starting-up the SF 50/DP-Slave with STOP-RUN transition STOP-RUN transition of the SF 50/DP-Slave without DB1-changes in the parameter block DPS: STOP-RUN transition of the SF 50/DP-Slave with DB1 changes in the DPS parameter block STOP status of the SF 50/DP-Slave Instructions for the configuration and installation of the SF 50/DP-Slave Requirements for commissioning the SF 50/DP-Slave as a PROFIBUS-DP slave Starting sequence of the SF 50/DP-Slave as PROFIBUS-DP slave Working steps for commissioning the SF 50/DP-Slave as a PROFIBUS-DP slave IV 9706

381 VISF - 50/DP Slave Contents 5.7 Testing and diagnosis Summary ot testing and diagnosis options Fault diagnosis in the user program of the DP-Master General remarks concering diagnosis Special notes concerning diagnosis requirements in Page frame operation General construction of diagnosis for SF 50/DP-Slave Station status and station number of the DP-Master Requesting station status 3 and station number of the DP-Master Requesting manufacturer s indentification Requesting signs of life from the control processor in the SF 50/DP-Slave STOP causes in SF 50/DP-Slave Requesting STOP causes User-specific diagnosis Transferring user-specific diagnosis to DP-Master Evaluation User-specific diagnosis Function of the BF LED on the SF 50/DP-Slave Fault diagnosis in the user program of the SF 50/DP-Slave Status reports" diagnosis byte Error reports diagnosis byte Failure behaviour of the SF 50/DP-Slave Lifesigns of the control processor in the SF 50/DP-Slave DP slave operation monitoring with the DP-Master V

382 VISF - 50/DP Slave Contents 5-VI 9706

383 VISF - 50/DP Slave 5.1 System summary 5.1 SYSTEM SUMMARY PN

384 VISF - 50/DP Slave 5.1 System summary Contents 5.1 System description SF 50/DP-Slave with PROFIBUS-DP interface Application possibilities using the SF 50/DP-Slave with PROFIBUS-DP interface Construction and operating mode of the SF 50/DP-Slave Display and operating elements Pin assignment of the PROFIBUS-DP interface

385 VISF - 50/DP Slave 5.1 System summary 5.1 System description This chapter contains information concerning: the PROFIBUS-DP in general, Performance characteristics and features that are offered by the PROFIBUS-DP interface of the SF 50/DP-Slave and Equipment with which the SF 50/DP-Slave can communicate as a PROFIBUS-DP bus slave. SF 50/DP-Slave with PROFIBUS-DP interface The PROFIBUS-DP interface of the SF 50/DP-Slave offers the following performance characteristics: The SF 50/DP-Slave can in general only be a DP slave on the PROFIBUS-DP. The SF 50/DP-Slave is a DP Standard slave. This means that the PROFIBUS-DP interface complies fully with the PROFIBUS-DP standard (DIN 19245, part 3). The PROFIBUS-DP interface of the SF 50/DP-Slave offers the following features: Intelligent pre-processing is possible. The connection of the SF 50/DP-Slave to the PROFIBUS-DP does not require any knowledge of communication mechanisms

386 SIE MENS PG 24VDC RUN STOP L2-DP FUSE BF S I E M OUT E NDIGITAL S IN S I M A T I C S U 16x24 DC 16 x 24 D C 0,5 A 1 21 RU N L+ L ST OP RU N Battery ST OP 3,4 V mAh.3.3 CO PY ANALOG/.7.7 IN/OUT 9 29 Batter y M M 8x V OFF L L+ 1x V LOW ma V DC COUNTERP G /2 kh z.5.5 INTERRUPT L+ M M 24V DC ES M 8MA VISF - 50/DP Slave 5.1 System summary Application possibilities using the SF 50/DP-Slave with PROFIBUS-DP interface The following figure shows a typical structure of a PROFIBUS-DP. DP-Master is a PLC with PROFIBUS- DP-Master; DP slaves are the SF 50/DP-Slave, S5-95U as DP slave and other field units. SF 50/DP-Slave COM ET200 PG / PC S5-95U Higher-order control unit with PROFIBUS-DP-Master Further field units Fig. 5/1: Equipment configuration The structure guidelines for the system are described in chapter 4. The SF 50/DP-Slave can communicate with the following equipment via the PROFIBUS-DP:

387 VISF - 50/DP Slave 5.1 System summary Devices / component Programmable valve terminal SF 50 with PROFIBUS-DP-Master (see chapter 4.x) Master interface component IM 308-B version 5 (applicable for S5-115U/ H...S5-155U/H) AG S5-95U / DP-Master Master interface component IM 308-C Other automation tools with integrated DP-Master interface PC with communications processor CP 5410 S5-DOS/ST Essential software for commissioning / for testing COM ET 200 (v. 4.0 or later) COM ET 200 (v. 4.0 or later) COM ET200 for WINDOWS (v. 2.x or later) COM ET200 for WINDOWS (v. 1.x or later) COM ET 200 (v. 4.0 or later) Table 5/1: Communications partners for SF 50/DP-Slave Structure and operating mode of the SF 50/DP-Slave This chapter contains information for the structure and operating mode of the SF 50/DP-Slave. The following figure shows the display elements and interfaces of the control block: SIEMENS RUN BF BF LED Display (BUS FAULT = red) STOP PG L2-DP Interface for PROFIBUS-DP Fig. 5/2: Display elements of the SF 50/DP-Slave

388 VISF - 50/DP Slave 5.1 System summary LED display RUN STOP BF Significance - PLC in "RUN" or "START" operating mode - SF 50 in "STOP" or "START" operating mode - Error display of the SF 50 - Program and data are being copied from the EEPROM -> RAM - Communication via the field bus is interrupted or has not yet been established Table 5/2: LED display of the SF 50 Display and operating elements Like the SB 50, the SF 50/DP-Slave has no operating elements. The field bus interface is supplied with power by the power supply of the valve terminal and is switched to RUN or STOP through the programmer and the PLC function "START/STOP" simultaneously with the SB 50. PIN allocation of the PROFIBUS-DP interface View PIN- Signal Name Designation No. 1 2 PE - Protective earth RxD / TxD-P Data line B 4 4 RTS Request to send M5V2 Data earth 7 6 P5V2 Supply Plus RxD / TxD-N - - Data line A - Table 5/3: Pin assignment of the PROFIBUS-DP interface

389 VISF - 50/DP slave 5.2 Data transfer 5.2 DATA TRANSFER PN

390 VISF - 50/DP slave 5.2 Data transfer Contents 5.2 Data transfer via the PROFIBUS-DP interface of the SF 50/DP-Slave Data transfer properties with the SF 50 as a DP slave Principal operating mode of data transfer Structure of the extended peripheral areas of the SF 50/DP-Slave Access to transmitting and receiving data Access to user-specific parameterization data

391 VISF - 50/DP slave 5.2 Data transfer 5.2 Data transfer via the PROFIBUS-DP interface of the SF 50/DP-Slave This chapter contains information concerning: How the data transfer of the SF 50/DP-Slave works in principle, how the extended peripheral areas of the SF 50/DP-Slave are structured and how to access the transmitting and receiving data in the user program. Data transfer properties with the SF 50 as a DP slave The SF 50/DP-Slave can only be a DP slave on the PROFIBUS-DP. The SF 50/DP-Slave prepares data for a DP-Master and can receive and process data from this DP-Master. The baud rate is determined in the DP-Master. The SF 50/DP-Slave accepts the following baud rates: 9.6 kbaud; 19.2 kbaud; kbaud; kbaud; 500 kbaud and 1500 kbaud. The SF 50/DP-Slave can prepare a maximum of 32 bytes of data for collection by the PROFIBUS- DP and receive a maximum of 32 bytes of data via the PROFIBUS-DP. The send and receive data are automatically prepared by the communications processor in the SF 50/DP-Slave, i.e. without the user program. There are extended peripheral areas (for DP only) available for transmitting and receiving data. The user defines and sets out the extended peripheral areas with load and transfer operations from the user program

392 VISF - 50/DP slave 5.2 Data transfer Principal operating mode of data transfer Data exchange between the DP-Master and SF 50 as DP slave is implemented cyclically via the transmitting and receiving buffer. Figure 5/1 shows the basics of data transfer from the SF 50/DP-Slave. EPO extended peripheral area - outputs (for SF 50/DP-Slave - transmitting data) EPI extended peripheral area - inputs (for SF 50/DP-Slave - receiving data) DP-Master Peripheral area Input Output PROFIBUS-DP SF 50/DP-Slave Controller User program EPO EPI Communications processor Transmitting buffer Reception buffer AG cycle DP cycle Fig. 5/3: Operating mode of the data transfer of SF 50 as DP slave Explanation of figure 3.1: The striped area depicts the data range (same striping = same data). The data transfer occurs in two cycles; in the PLC cycle and in DP cycle. PLC cycle: The transmitting data are written by the user program in the extended peripheral area outputs (EPO) of the SF 50/DP-Slave (1)

393 VISF - 50/DP slave 5.2 Data transfer At the cycle control point the communications processor copies the transmitting data from the EPO into the DP transmitting buffer (2). At the same time the communications processor copies the receiving data in the extended peripheral area inputs (EPI) (3). The receiving data stored in the EPI can be evaluated by the user program (4). Data exchange between the controller and communications processor occurs at the cycle control point. DP cycle: The DP-Master sends data to the SF 50/DP-Slave which are stored in the receiving buffer of the communications processor of the SF 50/DP-Slave (5). At the same time the transmitting data of the SF 50/DP-Slave are collected from the DP-Master (6). The data exchange between the DP-Master and DP slave occurs cyclically via the bus, irrespective of the cycle control point of the SF 50/DP-Slave

394 VISF - 50/DP slave 5.2 Data transfer Structure of the extended peripheral area of the SF 50/DP-Slave There are extended peripheral areas available in the SF 50/DP-Slave for the transmitting/receiving of data via the PROFIBUS-DP. The extended peripheral areas of the SF 50/DP-Slave are connected in the SF 50/DP-Slave to the areas of the process image: The process image of the inputs assigns the addresses The extended peripheral area - inputs (EPI) assigns the addresses The process image of the outputs assigns the addresses The extended peripheral area - outputs (EPO) assigns the addresses Please note that the extended peripheral areas are only available on an SF 50/DP-Slave fitted with a PROFIBUS-DP interface. No units in the extended peripheral areas of the SF 50/DP-Slave are addressable. The extended peripheral areas are used solely for storing DP data in the SF 50/DP-Slave. PLEASE NOTE Please note that extended peripheral areas are only available with the SF 50/DP-Slave. No device modules in the extended peripheral areas of the SF 50/DP-Slave are addressable. The extended peripheral areas are used solely for storing DP data in the SF 50/DP-Slave. Table 5/4 gives the precise structure of the extended peripheral areas in the SF 50/DP-Slave. The slave addresses in EPI are read-only access, but the addresses in EPO can be accessed via the user program

395 VISF - 50/DP slave 5.2 Data transfer Absolute address 5700 H : 571F H H : 5738 H 5739 H : 577D H 577E H : 577F H 5780 H : 579F H 57A0 H : 57F9 H 57FA H : 57FF H Address in EPI : : : : Address in EPO : : : Allocation Receiving data (sent from DP-Master) User-specific parameterization data (sent from DP-Master) Empty Diagnosis bytes "Status reports" and "Error reports" Transmitting data (prepared for DP-Master) Empty User-specific diagnosis bytes Table 5/4: Structure of the extended peripheral area of the SF 50/DP-Slave The user defines and sets out the extended peripheral areas with load and transfer operations from the user program

396 VISF - 50/DP slave 5.2 Data transfer Access to transmitting and receiving data The transmitting data must be recorded in the user program of the SF 50/DP-Slave with the transfer operations in the extended peripheral area - outputs (EPO). The following operations, value ranges and data ranges can be used: e.g.: Loading from user program Transferring in EPO Example Explanation Sending small amounts of data (ca Bytes) can be done through the byte or word-wise access in the user program: L IB/QB/IW/QW/ PY/PWI/FY/FW/ DL/DR/DW TPY / TPW LIB5 TPY140 The input byte 5 is transferred to the peripheral byte 140 in EPO Access via the TNB operation*) in the user program is suitable for sending lots of data (max. 32 bytes): TNB (Bytes) (Initial address in EPO is 5780H *) Transfering a data block in bytes (see chapter 3.7) LKH61F KH579C TNB20 Table 5/5: Access to transmitting data in the user program 20 Bytes from the flag byte 63 (MB63...MB44) are transferred to the EPO from peripheral byte 156 (PY156...PY137). Requirements for access to the receiving data: In the diagnosis byte status messages Bit 5=1, i.e. commissioning through the DP-Master has occured and in the diagnosis byte Error messages Bit 4=0, i.e. the receiving data in the SF 50/DP-Slave is valid

397 VISF - 50/DP slave 5.2 Data transfer The receiving data stored in the extended peripheral area - inputs (EPI) must be linked with the load operations in the user program of the SF 50/DP- Slave. The following operations, value ranges and data ranges can be used: Loading from EPI Transferring in the user program Example Explanation Reception of small amounts of data (ca Bytes) can be done through the byte or word-wise access in the user program: LPY / LPW TIB/QB/IW/QW/ PY/PW/FY/FW/ LPY130 TFY200 The peripheral byte 130 in EPI is transferred to the flag byte 200. DL/DR/DW Access via the TNB operation*) in the user program is suitable for receiving lots of data (max. 32 bytes): TNB (Bytes) LKH571D LKH61E6 TNB30 30 Bytes are transferred from the EPI from peripheral byte 157 (PY157...PY128) to the area from the flag byte 230 (FY230...FY201). *) Transferring a data block in bytes Table 5/6: Access to receiving data in the user program A detailed program sample using an SF 50/DP-Slave as a DP slave can be found in chapter

398 VISF - 50/DP slave 5.2 Data transfer Access to user-specific parameterization data The SF 50/DP-Slave obtains a (new) parameterization message from the DP-Master, when: The PROFIBUS-DP is in the booting-up phase or The connection between the DP-Master and the SF 50/DP-Slave was broken (e.g. through a brief removal of the bus cable connector). The parameterization message can contain specified user-specific parameterization data from the DP-Master for the SF 50 as a DP slave (example chap. 5.4). User-specific parameterization data can be used when required, to supply the SF 50/DP-Slave, through the DP-Master, start values (e.g. control parameters for software control in the SF 50/DP-Slave). The userspecific parameterization data are stored in the extended peripheral area - inputs (EPI). Requirements for access to the data: In the Status reports diagnosis byte, bit 5=1 has occured, i.e. commissioning by the DP-Master, and In the Status reports diagnosis byte, bit 3=1 has occured, i.e. user-specific parameterization data are available (chap. 5.7). The user-specific parameterization data are treated like the receiving data, i.e. linked with load operations in the user program

399 VISF - 50/DP slave 5.2 Data transfer The following operations, value ranges and data ranges can be used: Loading from EPI Transferring in the user program Example Explanation Reception of small amounts of data (ca Bytes) can be done through the byte or word-wise access in the user program: LPY / LPW TIB/QB/IW/QW/ PY/PW/FY/FW/ LPY160 TMB200 The peripheral byte 160 in the EPI is transferred to the marker byte 200. DL/DR/DW Access via the TNB operation*) in the user program is suitable for receiving lots of data (max. 25 bytes): TNB (Bytes) LKH572E LKH61D7 TNB15 15 Bytes are transferred from the EPI from peripheral byte 174 (PY174...PY160) in the area from flag byte 215 (MB215...MB201). *) Transfering a data block in bytes Table 5/7: Access to user-specific parameterization data in the user program PLEASE NOTE Bit 3 in the diagnosis byte Status reports is reset during the cycle control point by the operating system. It is therefore important to ensure, within the user program, that bit 3 is evaluated in each program cycle. It is possible that new user-specific parameterization data has been sent from the DP-Master

400 VISF - 50/DP slave 5.2 Data transfer

401 VISF - 50/DP Slave 5.3 Configuration 5.3 CONFIGURATION PN

402 VISF - 50/DP Slave 5.3 Configuration Contents 5.3 Specifying the configuration of the SF 50/DP-Slave with COM ET 200 in the DP-Master Operation of COM ET 200, v. 4.x Operation of COM ET 200 Windows Entering properties of the transmitting and receiving data using decimal code configuration bytes Equipment master data Determining the user-specific parameterization data in the parameter message of the DP-Master

403 VISF - 50/DP Slave 5.3 Configuration 5.3 Specifying the configuration of the SF 50/DP-Slave with COM ET 200 in the DP-Master This chapter describes the configuration of a SF 50/DP-Slave for a DP-Master. It is assumed, to understand this chapter, that the operation of the parameter software "COM ET 200" has been understood by reading the appropriate manuals of the DP-Masters. Operation of COM ET 200, v. 4.x Siemens IM 308-B FESTO SF 50 (see this chapter) Other DP-Masters that can be configured using the COM ET 200, v. 4.x software. Requirements Process the "ET SYSTEM PARAMETERS" mask Call up of the "CONFIGURING" mask 1. Enter of station number (Slave address) (areas can be used) 2. Select "Area" for addressing e.g.: P,Q for IM 308-B (ET System parameter "Dual port RAM addressing" = N) P for SF Select station type "FESTO SF 50 DP" The disc accompanying this manual contains the type files for the SF 50/DP-Slave using COM ET 200, v. 4.x. The type files can be found in the directory A:\SIEMENS\SF50\COMET200\GB under the name FXFB50TE

404 VISF - 50/DP Slave 5.3 Configuration PLEASE NOTE If "FESTO SF 50 DP" does not appear as the station type in the window, the following reasons may apply: Either the relevant type file has not been loaded into the PT/PC or the model file is held in the wrong directory. The type file for the SF 50/DP- Slave is called FXFB50TE.200 and is stored in the COM ET 200, v. 4x directory. 4. Select the initial addresses of the transmitting and receiving data e.g.: DI=8, DQ=8, AI=8, AQ=8 for SF 50 as the DP-Master 5. Enter transmitting and receiving data in the "DP identifier" window - Call up the "DP identifier" mask in the current field 0, 1, 2, 3 using [ F7 ] "HELP" Fig. 5/4: COM ET 200 "Configuring" mask

405 VISF - 50/DP Slave 5.3 Configuration - Enter receiving data from the DP-Master in the fields 0, 1 (transmitting data (outputs) of the SF 50/DP-Slave are the receiving data (inputs) of the DP-Master). - Enter transmitting data from the DP-Master in the fields 2, 3 (receiving data (inputs) of the SF 50/DP-Slave are the transmitting data (outputs) of the DP-Master). The entry fields must be allocated in increasing sequence; fields must not be left out. PLEASE NOTE Only code as many bytes as are required for the actual data transfer. The higher the number of configured bytes, the longer the DP cycle is. The SF 50/DP-Slave can prepare a maximum of 32 bytes of data for collection by the PROFIBUS- DP and receive a maximum of 32 bytes of data via the PROFIBUS-DP. Take these limits into account when coding. For the SF 50/DP-Slave, the "special identification format" (Bit = 00B) cannot be used. COM ET 200, v. 4.0, reduces the consistency of the "total length" to 8 bytes. Take these limits into account when coding. This ends the address assignment using COM ET 200 v. 4.x. After completing the address assignment using COM ET 200 for the SF 50/DP-Slave, the same address identifiers must be entered into the DB1 of the SF 50/DP-Slave. The procedure to follow is described in chapter

406 VISF - 50/DP Slave 5.3 Configuration Handling COM ET 200 for Windows (COM Profibus) The configuration of the SF 50/DP-Slave with the subsequent DP-Master is described in the following manuals: Siemens IM 308-C (Manual on ET 200 Distributed peripheral systems) Siemens AG S5-95U/DP-Master (Manual on ET 200 Distributed peripheral system) FESTO SF 50/DP-Master Other DP-Masters that can be configured using the COM ET 200 Windows. Requirements: Master system has been designed - Bus parameters - Host parameters - Master parameters MASTERSYSTEM window is called up 1. Select "Valves" button and introduce a new slave 2. Enter the slave station number (station number): _(areas can be used) 3. Select "SF 50/DP-Slave" station type The disc accompanying this manual contains the type files for the SF 50/DP-Slave under COM ET 200 for WINDOWS. The type files can be found in the directory A:\SIEMENS\SF50\COMWIN20\SLAVE\GB\FEFB50XE

407 VISF - 50/DP Slave 5.3 Configuration PLEASE NOTE If the "Valves button does not appear in the selections for the slaves or the "SF 50/DP-Slave station type does not appear in the "System parameter window, the following reasons may apply: - Either the relevant type file has not been loaded into the PG/PC or - The type file is held in the wrong directory. The type file for the SF 50/DP-Slave is called FEFB50XE.200 and is stored in the directory \COMWIN20\TYPDAT5X of COM ET 200 for WINDOWS Fig. 5/5: "Configuring" mask in COM ET 200 Windows 4. Enter transmitting and receiving data in the "CON- FIGURING" window