Unity Pro System Block Library

Transcription

1 Unity Pro System Block Library June

2 2

3 Table of Contents About the Book Part I General information Introduction Chapter 1 Block types and their applications Introduction Block types FFB Structure EN and ENO Chapter 2 Availability of the function block on different hardware platforms Introduction Chapter 3 HALT: Stopping the program Chapter 4 ITCNTRL : Triggering of TIMER type event processing Chapter 5 MASKEVT: Global masking of events Chapter 6 UNMASKEVT: Global unmasking of events Part III Hot Stand By Introduction Chapter 7 HSBY_RD: Reading the Hot Standby command register Chapter 8 HSBY_ST: Reading the Hot Standby status register Chapter 9 Chapter 10 HSBY_WR: Writing to the Hot Standby command register REV_XFER: Writing and reading the two Reverse-Transfer-Registers

4 Part IV SFC Management Introduction Chapter 11 CLEARCHART: Reset all active steps Chapter 12 FREEZECHART: Freeze sequence Chapter 13 INITCHART: Reset all active steps and start sequence normally Chapter 14 RESETSTEP: Reset a specific step in the sequence Chapter 15 SETSTEP: Set a specific step in the sequence Chapter 16 SFCCNTRL: SFC Control Overview Description Parameter description Part V SysClock Introduction Chapter 17 FREERUN: Free-running timer Chapter 18 PTC: Reading the stop date and code Chapter 19 RRTC_DT: Reading the system date Chapter 20 R_NTPC: Network real-time clock function Chapter 21 SCHEDULE: Real-time clock function Chapter 22 WRTC_DT: Updating the system date

5 Appendices Introduction Appendix A System objects At a Glance System bit introduction Description of system bits %S0 to %S Description of system bits %S15 to %S Description of system bits %S30 to %S Description of system words %SW12 to %SW Description of system words %SW48 to %SW Description of System Words %SW60 to %SW63: Glossary Index

6 6

7 About the Book At a Glance Document Scope Validity Note Product Related Warnings User Comments This document describes the functions and function blocks of the System library. This document is valid for Unity Pro Version 2.1. The data and illustrations found in this document are not binding. We reserve the right to modify our products in line with our policy of continuous product development. The information in this document is subject to change without notice and should not be construed as a commitment by Schneider Electric. Schneider Electric assumes no responsibility for any errors that may appear in this document. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us. No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of Schneider Electric. All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to ensure compliance with documented system data, only the manufacturer should perform repairs to components. When controllers are used for applications with technical safety requirements, please follow the relevant instructions. Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results. Failure to observe this product related warning can result in injury or equipment damage. We welcome your comments about this document. You can reach us by at TECHCOMM@modicon.com 7

8 About the Book 8

9 General information I Introduction Overview What's in this Part? This section provides general information on the System library This part contains the following chapters: Chapter Chapter Name Page 1 Block types and their applications 11 2 Availability of the function block on different hardware platforms 19 9

10 General information 10

11 Block types and their applications 1 Introduction Overview What's in this Chapter? This chapter describes the different block types and their applications. This chapter contains the following topics: Topic Page Block types 12 FFB Structure 13 EN and ENO 16 11

12 Block types and their applications Block types Block types Elementary Function Elementary function block Derived function block Procedure Different block types are used in Unity Pro. The general term for all block types is FFB. There are the following types of block: Elementary Function (EF) Elementary Function Block (EFB) Derived Function Block (DFB) Procedure Elementary functions (EF) have no internal status.. If the input values are the same, the value at the output is the same for all executions of the function, e.g. the addition of two values gives the same result at every execution. An elementary function is represented in the graphical languages (FDB and LD) as a block frame with inputs and an output. The inputs are always represented on the left and the outputs always on the right of the frame The name of the function, i.e. the function type, is shown in the center of the frame. The number of inputs can be increased with some elementary functions. Elementary function blocks (EFB) have an internal status. If the inputs have the same values, the value on the output can have another value during the individual executions. For example, with a counter, the value on the output is incremented. An elementary function block is represented in the graphical languages (FDB and LD) as a block frame with inputs and outputs. The inputs are always represented on the left and the outputs always on the right of the frame The name of the function block, i.e. the function block type, is shown in the center of the frame. The instance name is displayed above the frame. Derived function blocks (DFBs) have the same properties as elementary function blocks. They are created by the user in the programming languages FBD, LD, IL and/or ST. Procedures are technical functions. The only difference from elementary functions is that procedures can have more than one output and they support variables of the VAR_IN_OUT data type. Procedures do not return a value. Procedures are a supplement to IEC and must be enabled explicitly. There is no visual difference between procedures and elementary functions. 12

13 Block types and their applications FFB Structure Structure Each FFB is made up of an operation (name of the FFB), the operands required for the operation (formal and actual parameters) and an instance name for elementary/ derived function blocks. Call of a function block in the FBD programming language: Instance Name Operation (FFB name) Operand Formal parameter Actual parameter MY_TON TON ENABLE EXAMP TIME1 EN IN PT ENO Q ET ERROR OUT TIME2 Instance Name Formal call of a function block in the ST programming language: Operands Formal parameters (inputs) Formal parameters (outputs) MY_TON (EN:=ENABLE, IN:=EXAMP, PT:=TIME1, ENO=>ERROR, Q=>OUT, ET=>TIME2); Actual parameters (inputs) Actual parameters (outputs) Operands Operation The operation determines which function is to be executed with the FFB, e.g. shift register, conversion operations. 13

14 Block types and their applications Operand Formal/actual parameters FFB Call in IL/ST The operand specifies what the operation is to be executed with. With FFBs, this consists of formal and actual parameters. Inputs and outputs are required to transfer values to or from an FFB. These are called formal parameters. Objects are linked to formal parameters; these objects contain the current process states. They are called actual parameters. At program runtime, the values from the process are transferred to the FFB via the actual parameters and then output again after processing. The data type of the actual parameters must match the data type of the input/output (formal parameters). The only exceptions are generic inputs/outputs whose data type is determined by the actual parameter. If all actual parameters consist of literals, a suitable data type is selected for the function block. In text languages IL and ST, FFBs can be called in formal and in informal form. Details can be found in the Reference manual. Example of a formal function call: out:=limit (MN:=0, IN:=var1, MX:=5) ; Example of an informal function call: out:=limit (0, var1, 5) ; Note: Take note that the use of EN and ENO is only possible for formal calls. 14

15 Block types and their applications VAR_IN_OUT variable FFBs are often used to read a variable at an input (input variables), to process it and to output the altered values of the same variable (output variables). This special type of input/output variable is also called a VAR_IN_OUT variable. The input and output variable are linked in the graphic languages (FBD and LD) using a line showing that they belong together. Function block with VAR_IN_OUT variable in FBD: MY_EXAMP1 Input1 Input2 Comb_IN_OUT IN1 IN2 IO1 EXAMP1 OUT1 OUT2 IO1 Output1 Output2 Comb_IN_OUT Function block with VAR_IN_OUT variable in ST: MY_EXAMP1 (IN1:=Input1, IN2:=Input2, IO1:=Comb_IN_OUT, OUT1=>Output1, OUT2=>Output2) ; The following points must be considered when using FFBs with VAR_IN_OUT variables: All VAR_IN_OUT inputs must be assigned a variable. Literals or constants cannot be assigned to VAR_IN_OUT inputs/outputs. The following additional limitations apply to the graphic languages (FBD and LD): When using graphic connections, VAR_IN_OUToutputs can only be connected with VAR_IN_OUTinputs. Only one graphical link can be connected to a VAR_IN_OUT input/output. Different variables/variable components can be connected to the VAR_IN_OUT input and the VAR_IN_OUT output. In this case the value of the variables/variable component on the input is copied to the at the output variables/variable component. No negations can be used on VAR_IN_OUT inputs/outputs. A combination of variable/address and graphic connections is not possible for VAR_IN_OUT outputs. 15

16 Block types and their applications EN and ENO Description An EN input and an ENO output can be configured for all FFBs. If the value of EN is "0" when the FFB is called up, the algorithms defined by the FFB are not executed and ENO is set to "0". If the value of EN is "1" when the FFB is called up, the algorithms defined by the FFB are executed. After the algorithms have been executed successfully, the value of ENO is set to "1". If an error occurs when executing these algorithms, ENO is set to "0". If ENO is set to "0" (caused by EN=0 or an error during execution): Function blocks EN/ENO handling with function blocks that (only) have one link as an output parameter: Function_block_1 Function_block_2 EN ENO EN ENO IN1 OUT IN1 OUT IN2 IN2 If EN from FunctionBlock_1 is set to "0", the output connection OUT from FunctionBlock_1 retains the status it had in the last correctly executed cycle. EN/ENO handling with function blocks that have one variable and one link as output parameters: Function_block_1 Function_block_2 EN ENO EN ENO IN1 OUT OUT1 IN1 OUT IN2 IN2 If EN from FunctionBlock_1 is set to "0", the output connection OUT from FunctionBlock_1 retains the status it had in the last correctly executed cycle. The variable OUT1 on the same pin, either retains its previous status or can be changed externally without influencing the connection. The variable and the link are saved independently of each other. 16

17 Block types and their applications Functions/Procedures As defined in IEC , the outputs from deactivated functions (EN-input set to "0") is undefined. (The same applies to procedures.) Here nevertheless an explanation of the output statuses in this case: EN/ENO handling with function/procedure blocks that (only) have one link as an output parameter: Function/Procedure_1 Function/Procedure_2 EN ENO EN ENO IN1 OUT IN1 OUT IN2 IN2 If EN from Function/Procedure_1 is set to "0", the output connection OUT from Function/Procedure_1 is also set to "0". EN/ENO handling with function/procedure blocks that have one variable and one link as output parameters: Function/Procedure_1 Function/Procedure_2 EN ENO EN ENO IN1 OUT OUT1 IN1 OUT IN2 IN2 If EN from Function/Procedure_1 is set to "0", the output connection OUT from Function/Procedure_1 is also set to "0", however the variable OUT1 on the same pin retains its previous value. In this way it is possible for the variable and the link to have different values. The output behavior of the FFBs does not depend on whether the FFBs are called up without EN/ENO or with EN=1. Conditional/ Unconditional FFB Call "Unconditional" or "conditional" calls are possible with each FFB. The condition is realized by pre-linking the input EN. EN connected conditional calls (the FFB is only processed if EN = 1) EN shown, hidden, and marked TRUE, or shown and not occupied unconditional calls (FFB is always processed) Note for IL and ST The use of EN and ENO is only possible in the text languages for a formal FFB call, e.g. MY_BLOCK (EN:=enable, IN1:=var1, IN2:=var2, ENO=>error, OUT1=>result1, OUT2=>result2); Assigning the variables to ENO must be done with the operator =>. With an informal call, EN and ENO cannot be used. 17

18 Block types and their applications 18

19 Availability of the function block on different hardware platforms 2 Availability of the block on the various hardware platforms Introduction Not all blocks are available on all hardware platforms. The blocks available on your hardware platform can be found in the following tables. Note: The functions and function blocks in this library are not defined in IEC Events Availability of the blocks: Block name Block type Premium Quantum HALT Procedure + + ITCNTRL Procedure + + MASKEVT Procedure + + UNMASKEVT Procedure + + Legend: + Yes - No 19

20 Availability of the function block Hot Standby Availability of the blocks: Block name Block type Premium Quantum HSBY_RD EFB CPU HSBY_ST EFB CPU HSBY_WR EFB CPU REV_XFER EFB CPU Legend: + Yes - No SFC Management Availability of the blocks: Block name Block type Premium Quantum CLEARCHART EF + + FREEZECHART EF + + INITCHART EF + + RESETSTEP Procedure + + SETSTEP Procedure + + SFCCNTRL EFB + + Legend: + Yes - No 20

21 Availability of the function block System clock Availability of the blocks: Block name Block type Premium Quantum FREERUN EF TSX P PTC Procedure + + RRTC_DT Procedure + + R_NTPC Procedure + + SCHEDULE Procedure + + WRTC_DT Procedure + + Legend: + Yes - No 21

22 Availability of the function block 22

23 Events II Introduction Overview What's in this Part? This section describes the elementary functions and elementary function blocks of the Events family. This part contains the following chapters: Chapter Chapter Name Page 3 HALT: Stopping the program 25 4 ITCNTRL : Triggering of TIMER type event processing 27 5 MASKEVT: Global masking of events 31 6 UNMASKEVT: Global unmasking of events 33 23

24 Events 24

25 HALT: Stopping the program 3 Description Description of the function The HALT function in an application program can be used to halt its execution (stop all tasks), which effectively freezes the variable objects of this program. In order for execution to resume, a program halted in this way must be initialized (using the INIT command). The instructions that follow the HALT instruction are therefore not executed. Caution; when the PLC is in HALT, all tasks are stopped. Check the behavior of the associated I/Os. The additional parameters EN and ENO can be configured. FBD representation EN HALT ENO LD representation EN HALT ENO 25

26 HALT IL representation ST representation HALT HALT(); 26

27 ITCNTRL : Triggering of TIMER type event processing 4 Description Description of the function The ITCNTRL function is a timer that triggers the TIMER type event processing selected by the EVENT input, when the current value reaches the preset value. The preset and time base values are selected in the event processing properties dialog box. Additional parameters EN and ENO can be configured. Representation in FBD ITCNTRL Enable Reset_Timer Hold_Timer Nb_Task_Event ENABLE RESET HOLD EVENT STATUS VALUE Status_Timer Current_Value 27

28 ITCNTRL Representation in LD ITCNTRL Enable EN ENABLE ENO STATUS Status_Timer Reset_Timer RESET VALUE Current_Value Hold_Timer HOLD Nb_Task_Event EVENT Representation in IL Representation in ST LD Enable ITCNTRL Reset_Timer, Hold_Timer, Nb_task_Event, Status_Timer, Current_Value ITCNTRL(Reset_Timer, Hold_Timer, Nb_task_Event, Status_Timer, Current_Value); 28

29 ITCNTRL Description of the parameters The following table describes the input parameters: Parameter Type Comment Enable BOOL Enable input selected,. on state 1: the event processing is triggered when the timer has elapsed. on state 0: no event is emitted Reset_Timer BOOL On state 1 reset the timer Hold_Timer BOOL On state 1 freeze the timer incrementation. Nb_Task_Event BYTE Input word which determines the TIMER event processing number to be triggered. The following table describes the output parameters: Parameter Type Comment Status_Timer WORD Status word : bit0 = 1 execution delayed by a masking of the interruption. bit 1 =1 event processing number not valid bit 2 = 1 validated timer (Enable input image). bit 3 = 1 "frozen" timer (Hold_Timer input image). bit 4 =1 as soon as ITCNTRL is called the first time with the input Reset_Timer or Hold_Timer at 1 (out-of-phase mode). It is reset to 0 on a cold start. bit 5 = 1 FIFO memory stack of the saturated interruptions. Current_Value TIME Current timer value. This value is increased by 0 to the preset value. When the preset value is reached, it is reset to 0. If the associated TIMER type event processing is confirmed, it is executed. 29

30 ITCNTRL 30

31 MASKEVT: Global masking of events 5 Description Description of the function The MASKEVT function performs global masking of events (1). Events are stored in the PLC's memory, but any associated event processing tasks remain inactive, as long as the masking operation is valid, until the next UNMASKEVT instruction. The additional parameters EN and ENO can be configured. (1) except for interruptions generated by FIPWAY telegrams. FBD representation EN MASKEVT ENO LD representation EN MASKEVT ENO 31

32 MASKEVT IL representation ST representation MASKEVT MASKEVT(); 32

33 UNMASKEVT: Global unmasking of events 6 Description Description of the function The UNMASKEVT function performs global unmasking of events. The events that were stored during the masking period are processed. The event processing mechanism is operational until the next MASKEVT instruction. The additional parameters EN and ENO can be configured. FBD representation UNMASKEVT EN ENO LD representation UNMASKEVT EN ENO IL representation ST representation UNMASKEVT UNMASKEVT(); 33

34 UNMASKEVT 34

35 Hot Stand By III Introduction Overview What's in this Part? This section describes the elementary functions and elementary function blocks of the Hot Stand By family. This part contains the following chapters: Chapter Chapter Name Page 7 HSBY_RD: Reading the Hot Standby command register 37 8 HSBY_ST: Reading the Hot Standby status register 41 9 HSBY_WR: Writing to the Hot Standby command register REV_XFER: Writing and reading the two Reverse-Transfer- Registers 49 35

36 Hot Stand By 36

37 HSBY_RD: Reading the Hot Standby command register 7 Description: HSBY_RD Function description Representation in FBD This EFB allows you to use the Hot Standby function. It searches (together with other EFBs in the Hot Standby family) the configuration of the respective Quantum PLC for the required components. These components always refer to hardware that is actually connected. Therefore the correct behavior of this EFB on the simulators cannot be guaranteed. The EFB HSBY_RD independently checks if a Hot Standby configuration exists (%SW60 (See Detailed Description, p. 116)). If a configuration is present the contents of the command register are given and the HSBY output is set to "1". If there is no Hot Standby configuration present the output is set to "0". EN and ENO can be configured as additional parameters. HSBY_RD_Instance HSBY_RD HSBY INV_KEY PCA_RUN PCB_RUN SBY_OFF EXC_UPD SWP_MB1 SWP_MB2 SWP_MB3 HSBY_ConfigurationFound InvalidateKeypad PLC_A_Running PLC_B_Running StandbyOff ExecUpdate SwapAddressModbusPort1 37

38 HSBY_RD Representation in LD HSBY_RD_Instance HSBY_RD EN ENO HSBY INV_KEY PCA_RUN PCB_RUN SBY_OFF EXC_UPD SWP_MB1 HSBY_ConfigurationFound InvalidateKeypad PLC_A_Running PLC_B_Running StandbyOff ExecUpdate SwapAddressModbusPort1 SWP_MB2 SWP_MB3 Representation in IL Representation in ST CAL HSBY_RD_Instance (HSBY=>HSBY_ConfigurationFound, INV_KEY=>InvalidateKeypad, PCA_RUN=>PLC_A_Running, PCB_RUN=>PLC_B_Running, SBY_OFF=>StandbyOff, EXC_UPD=>ExecUpdate, SWP_MB1=>SwapAddressModbusPort1) HSBY_RD_Instance (HSBY=>HSBY_ConfigurationFound, INV_KEY=>InvalidateKeypad, PCA_RUN=>PLC_A_Running, PCB_RUN=>PLC_B_Running, SBY_OFF=>StandbyOff, EXC_UPD=>ExecUpdate, SWP_MB1=>SwapAddressModbusPort1); 38

39 HSBY_RD Parameter description Description of the output parameters: Parameter Data type Meaning HSBY BOOL "1" = Hot Standby configuration found INV_KEY BOOL "1" = The submenu for the Hot Standby PLC button is disabled. PCA_RUN BOOL "1" = The PLC with the Hot Standby CPU 1. function is "A" on local rack 2. Command Register is selected RUN "0" = The PLC with the Hot Standby CPU 1. function is "A" on local rack 2. Command Register is selected OFFLINE PCB_RUN BOOL "1" = The PLC with the Hot Standby CPU 1. function is "B" on local rack 2. Command Register is selected RUN "0" = The PLC with the Hot Standby CPU 1. function is "B" on local rack 2. Command Register is selected OFFLINE SBY_OFF BOOL "1" = The standby PLC switches to the offline mode as soon as both PLCs receive a different program. EXC_UPD BOOL "1" = Exec-(Operating system-)update in the Standby-PLC is possible with the primary PLC still running. (After Exec-Update the standby PLC changes back to the online mode.) SWP_MB1 BOOL If a switchover has occurred, "1" = No Swap address of Modbus ports 1. "0" = Swap address of Modbus ports 1. SWP_MB2 BOOL Not used. Reserved SWP_MB3 BOOL Not used. Reserved 39

40 HSBY_RD 40

41 HSBY_ST: Reading the Hot Standby status register 8 Description: HSBY_ST Function description Representation in FBD This EFB allows you to use the Hot Standby function. It searches (together with other EFBs in the Hot Standby family) the configuration of the respective Quantum PLC for the required components. These components always refer to hardware that is actually connected. Therefore the correct behavior of this EFB on the simulators cannot be guaranteed. The EFB is used to read the IEC Hot Standby status register (%SW61 (See Detailed Description, p. 116)). If there is no Hot Standby configuration present the HSBY output is set to "0". EN and ENO can be configured as additional parameters. HSBY_ST_Instance HSBY_ST HSBY THIS_OFF THIS_PRY THIS_SBY REMT_OFF REMT_PRY REMT_SBY LOGIC_OK THIS_ISA THIS_ISB HSBY_ConfigurationFound PLC_Offline Primary_PLC Standby_PLC Remote_PLC_Offline PrimaryRemote_PLC StandbyRemote_PLC IdenticalPrograms HSBY_ModuleSwitchA HSBY_ModuleSwitchB 41

42 HSBY_ST Representation in LD HSBY_ST_Instance HSBY_ST EN ENO HSBY THIS_OFF THIS_PRY THIS_SBY REMT_OFF REMT_PRY REMT_SBY LOGIC_OK THIS_ISA THIS_ISB HSBY_ConfigurationFound PLC_Offline Primary_PLC Standby_PLC Remote_PLC_Offline PrimaryRemote_PLC StandbyRemote_PLC IdenticalPrograms HSBY_ModuleSwitchA HSBY_ModuleSwitchB Representation in IL CAL HSBY_ST_Instance (HSBY=>HSBY_ConfigurationFound, THIS_OFF=>PLC_Offline, THIS_PRY=>Primary_PLC, THIS_SBY=>Standby_PLC, REMT_OFF=>Remote_PLC_Offline, REMT_PRY=>PrimaryRemote_PLC, REMT_SBY=>StandbyRemote_PLC, LOGIC_OK=>IdenticalPrograms, THIS_ISA=>HSBY_ModuleSwitchA, THIS_ISB=>HSBY_ModuleSwitchB) 42

43 HSBY_ST Representation in ST Parameter description HSBY_ST_Instance (HSBY=>HSBY_ConfigurationFound, THIS_OFF=>PLC_Offline, THIS_PRY=>Primary_PLC, THIS_SBY=>Standby_PLC, REMT_OFF=>Remote_PLC_Offline, REMT_PRY=>PrimaryRemote_PLC, REMT_SBY=>StandbyRemote_PLC, LOGIC_OK=>IdenticalPrograms, THIS_ISA=>HSBY_ModuleSwitchA, THIS_ISB=>HSBY_ModuleSwitchB); Description of output parameters: Parameter Data type Meaning HSBY BOOL "1" = Hot Standby configuration found THIS_OFF BOOL "1" = This PLC is offline THIS_PRY BOOL "1" = This PLC is the primary PLC THIS_SBY BOOL "1" = This PLC is the standby PLC REMT_OFF BOOL "1" = The other (remote) PLC is offline REMT_PRY BOOL "1" = The other PLC is the primary PLC REMT_SBY BOOL "1" = The other PLC is the standby PLC LOGIC_OK BOOL "1" = The programs for both PLCs are identical and Logic Mismatch is active. THIS_ISA BOOL "1" = This PLC chose the CPU with the lower IP address between both Hot Standby CPUs. This is the Hot Standby CPU "A". THIS_ISB BOOL "1" = This PLC chose the CPU with the higher IP address between both Hot Standby CPUs. This is the Hot Standby CPU "B". 43

44 HSBY_ST 44

45 HSBY_WR: Writing to the Hot Standby command register 9 Description: HSBY_WR Function description This EFB allows you to use the Hot Standby function. It searches (together with other EFBs in the Hot Standby family) the configuration of the respective Quantum PLC for the required components. These components always refer to hardware that is actually connected. Therefore the correct behavior of this EFB on the simulators cannot be guaranteed. The EFB HSBY_WR is used to set different Hot Standby Modes permitted for Hot Standby. Setting the respective modes means a change in the Hot Standby command register (%SW60 (See Detailed Description, p. 116)), which is carried out automatically by the function block. If there is no Hot Standby configuration, the HSBY_ConfigurationFound output is set to "0", otherwise it is set to "1". Note: This function only affects the primary CPU. EN and ENO can be configured as additional parameters. Representation in FBD HSBY_WR_Instance HSBY_WR InvalidateKeypad PLC_A_Running PLC_B_Running SwapAddressModbusPort1 INV_KEY PCA_RUN PCB_RUN SWP_MB1 SWP_MB2 HSBY HSBY_ConfigurationFound SWP_MB3 45

46 HSBY_WR Representation in LD HSBY_WR_Instance HSBY_WR InvalidateKeypad EN INV_KEY ENO HSBY HSBY_ConfigurationFound PLC_A_Running PCA_RUN PLC_B_Running PCB_RUN SwapAddressModbusPort1 SWP_MB1 SWP_MB2 SWP_MB3 Representation in IL CAL HSBY_WR_Instance (INV_KEY:=InvalidateKeypad, PCA_RUN:=PLC_A_Running, PCB_RUN:=PLC_B_Running, SWP_MB1:=SwapAddressModbusPort1, HSBY=>HSBY_ConfigurationFound) Representation in ST HSBY_WR_Instance (INV_KEY:=InvalidateKeypad, PCA_RUN:=PLC_A_Running, PCB_RUN:=PLC_B_Running, SWP_MB1:=SwapAddressModbusPort1, HSBY=>HSBY_ConfigurationFound); 46

47 HSBY_WR Parameter description Description of the input parameters: Parameter Data type Meaning INV_KEY BOOL In the submenu for the Hot Standby PLC button "1" = Changes are disabled. "0" = Changes are allowed. PCA_RUN BOOL "1 -> 0" = The Hot Standby CPU with A function on the local rack is forced into OFFLINE mode. "0 -> 1" = The Hot Standby CPU with "A" function is forced into RUN mode if its own button mode is in RUN mode. PCB_RUN BOOL "1 -> 0" = The Hot Standby CPU with "B" function on the local rack is forced into OFFLINE mode. "0 -> 1" = The Hot Standby CPU with the "B" function is forced into RUN mode if its own button mode is in RUN mode. SWP MB1 BOOL "0" and a switchover happened: The Modbus address on port 1 of the NEW primary PLC changes. new primary PLC address = old primary address new standby PLC address = new primary address "1" and a switchover happened: The Modbus address on Port 1 of the PLC don t changes. new primary PLC address = old primary address new standby PLC address = old primary address SWP_MB2 BOOL Not used. Reserved SWP MB3 BOOL Not used. Reserved Description of the output parameters: Parameter Data type Meaning HSBY BOOL "1" = Hot Standby configuration found. 47

48 HSBY_WR 48

49 REV_XFER: Writing and reading the two Reverse-Transfer- Registers 10 Description: REV_XFER Function description This EFB allows you to use the Hot Standby function. It searches (together with other EFBs in the Hot Standby family) the configuration of the respective Quantum PLC for the required components. These components always refer to hardware that is actually connected. The EFB REV_XFER provides the ability to transmit a 16 bit word from the standby PLC to the primary PLC and vice versa. The two registers transferred by this EFB are %SW62 (See Detailed Description, p. 116) and %SW63 (See Detailed Description, p. 116). REV_XFER must be called up absolutely in the first section of the project executed. The parameter addresses TO_REV1 and TO_REV2 must be in the non-transfer area to prevent an overwriting by the Primary PLC. Note: In the old (Concept) Hot Standby System these two registers (Reverse Transfer Registers) are the first addresses in the non-transfer area. As additional parameters, EN and ENO are projected. Appearance in FBD Appearance: REV_XFER_Instance REV_XFER Standby_PLC_FirstReg Standby_PLC_SecondReg TO_REV1 TO_REV2 HSBY PRY SBY FR_REV1 FR_REV2 HSBY_ConfFlag Primary_PLC_Flag Standby_PLC_Flag FirstRevTransReg SecondRevTransReg 49

50 REV_XFER Appearance in LD Appearance: REV_XFER_Instance REV_XFER Standby_PLC_FirstReg Standby_PLC_SecondReg EN TO_REV1 TO_REV2 ENO HSBY PRY SBY HSBY_ConfFlag Primary_PLC_Flag Standby_PLC_Flag FR_REV1 FirstRevTransReg FR_REV2 SecondRevTransReg Appearance in IL Appearance in ST Appearance: CAL REV_XFER_Instance (TO_REV1:=Standby_PLC_FirstReg, TO_REV2:=Standby_PLC_SecondReg, HSBY=>HSBY_ConfFlag, PRY=>Primary_PLC_Flag, SBY=>Standby_PLC_Flag, FR_REV1=>FirstRevTransReg, FR_REV2=>SecondtRevTransReg) Appearance: REV_XFER_Instance (TO_REV1:=Standby_PLC_FirstReg, TO_REV2:=Standby_PLC_SecondReg, HSBY=>HSBY_ConfFlag, PRY=>Primary_PLC_Flag, SBY=>Standby_PLC_Flag, FR_REV1=>FirstRevTransReg, FR_REV2=>SecondtRevTransReg); 50

51 REV_XFER Parameter description Description of input parameters: Parameter Data type Description TO_REV1 INT Describes the first reverse transfer register if this PLC is the standby PLC. TO_REV2 INT Describes the second reverse transfer register if this PLC is the standby PLC. Description of the output parameters: Parameter Data type Description HSBY BOOL "1" = Hot Standby configuration PRY BOOL 1 = This PLC is the primary PLC. SBY BOOL 1 = This PLC is the standby PLC. FR_REV1 INT Content of first reverse transfer register (%SW62 (See Detailed Description, p. 116)). Output only if HSBY is "1". FR_REV2 INT Content of second reverse transfer register (%SW63 (See Detailed Description, p. 116)). Output only if HSBY is "1". 51

52 REV_XFER 52

53 SFC Management IV Introduction Overview What's in this Part? This section describes the elementary functions and elementary function blocks of the SFC Management family. This part contains the following chapters: Chapter Chapter Name Page 11 CLEARCHART: Reset all active steps FREEZECHART: Freeze sequence INITCHART: Reset all active steps and start sequence normally RESETSTEP: Reset a specific step in the sequence SETSTEP: Set a specific step in the sequence SFCCNTRL: SFC Control 71 53

54 SFC Management 54

55 CLEARCHART: Reset all active steps 11 Description Function description This function is to reset sequences. DANGER Danger of unsafe, dangerous and destructive processes. CLEARCHART should not be used for finding error on controllers of machine tools, process or material management system if the are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. With a 1 signal at the input ClearSequence, the sequence is stopped and all steps are reset. As long as the 1 signal is at the input, the sequence stays in this mode, i.e. it cannot be started. This state remains even if input ClearSequence reverts back to 0. The status (sequence reset) is shown with a 1 signal at the output ClearState. Only when there is a 0 signal at the input ClearSequence, the sequence can be started with the function block SFCCNTRL (See Description, p. 72) (Input INIT), the function INITCHART (See Description, p. 63) or another external step activation command. Since the sequence is permanently reset as long as there is a 1 signal at the input ClearSequence, you should take the following measures to prevent a permanent blocking of the sequence: Conditional call of the function CLEARCHART via the input EN. Conditional call of the function CLEARCHART via e.g. IF statement in the programming language ST. Use edge recognition (R_TRIG) at the input ClearSequence. 55

56 CLEARCHART Note: The output ClearState shows the current state of the sequence, i.e. the sequence can also be reset with the function block SFCCNTRL (See Description, p. 72) (Input CLEAR), the function INITCHART (See Description, p. 63), the procedure RESETSTEP (See Description, p. 67) (reset the last/only active step) or and other control command (external). EN and ENO can be configured as additional parameters. Representation in FBD CLEARCHART SectionName CHARTREF ClearChart CLEAR_I CLEAR_O ClearState Representation in LD CLEARCHART EN ENO SectionName CHARTREF ClearChart CLEAR_I CLEAR_O ClearState Representation in IL LD SectionName CLEARCHART ClearChart ST ClearState Representation in ST ClearState := CLEARCHART (SectionName, ClearChart) ; 56

57 CLEARCHART Parameter description Description of input parameters: Parameter Data type Description CHARTREF SFCCHART_STATE Association with the SFC section to be controlled is done via the name of the section. If an SFC section is created then it is automatically assigned with a variable of data type SFCCHART_STATE. The variable that is created always has the name of the respective SFC section.) CLEAR_I BOOL 0->1: Reset all active steps in the sequence. Description of output parameters: Parameter Data type Description CLEAR_O BOOL 1: Sequence was reset, i.e. the sequence has no active step 57

58 CLEARCHART 58

59 FREEZECHART: Freeze sequence 12 Description Function description The function is to "freeze" the sequence (evaluation of transitions is turned off). DANGER Danger of unsafe, dangerous and destructive processes. FREEZECHART should not be used for finding error on controllers of machine tools, process or material management system if the are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. The current state of the sequence is frozen by a 1 signal at the input FreezeSequence. The status of the transitions is no longer evaluated. Therefore, it is no longer possible to move on in the sequence, even if the transition condition of the "active" transition is true. This function can be used in conjunction with the functions for step-by-step processing (function block SFCCNTRL (See Description, p. 72) (Inputs STEPUN and STEPDEP) or external SFC control command) for error correction. The output SequenceFreezed is 1 when the sequence is frozen. Note: The output shows the current status of the sequence, i.e. the sequence can also be frozen with the function block SFCCNTRL or another external SFC control command. EN and ENO can be configured as additional parameters. 59

60 FREEZECHART Representation in FBD FREEZECHART SectionName CHARTREF FreezeSequence FREEZE_I FREEZE_O SequenceFreezed Representation in LD FREEZECHART EN ENO SectionName CHARTREF FreezeSequence FREEZE_I FREEZE_O SequenceFreezed Representation in IL LD SectionName FREEZECHART SectionName ST SequenceFreezed Representation in ST SequenceFreezed := FREEZECHART (SectionName, FreezeSequence) ; 60

61 FREEZECHART Parameter description Description of the input parameter: Parameter Data type Meaning SectionName SFCCHART_STATE Association with the SFC section to be controlled is done via the name of the section. If an SFC section is created then it is automatically assigned with a variable of data type SFCCHART_STATE. The variable that is created always has the name of the respective SFC section.) FreezeSequence BOOL 1: Freeze sequence (turn off evaluation of transitions) Description of the output parameter: Parameter Data type Meaning SequenceFreezed BOOL 1: Sequence was frozen (evaluation of transitions was turned off) 61

62 FREEZECHART 62

63 INITCHART: Reset all active steps and start sequence normally 13 Description Function description This function is to reset and normally start sequences. DANGER Danger of unsafe, dangerous and destructive processes. INITCHART should not be used for finding error on controllers of machine tools, process or material management system if the are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. In relation to all functions and function blocks for sequence control, INITCHART has the highest priority. Reset sequence With a 1 signal at the input InitSequence, the sequence is stopped and all steps are reset. As long as the 1 signal is at the input, the sequence stays in this mode, i.e. it cannot be started. Since the sequence is permanently reset as long as there is a 1 signal at the input InitSequence, you should take the following measures to prevent a permanent blocking of the sequence: Conditional call of the function INITCHART via the input EN. Conditional call of the function INITCHART via e.g. IF statement in the programming language ST. Use edge recognition (R_TRIG) at the input InitSequence. Start sequence normally With a 1->0 edge at the input InitSequence, the sequence is started normally, i.e. the initial step is activated. This is shown for one cycle with a 1 signal at the output InitState. 63

64 INITCHART Note: The output InitState shows the current status of the sequence, i.e. the sequence can also be normally started with the function block SFCCNTRL (See Description, p. 72) (input INIT) or another external control command. EN and ENO can be configured as additional parameters. Representation in FBD INITCHART SectionName CHARTREF InitializeChart INIT_I INIT_O InitState Representation in LD INITCHART EN ENO SectionName CHARTREF InitializeChart INIT_I INIT_O InitState Representation in IL LD SectionName INITCHART InitializeChart ST InitState Representation in ST InitState := INITCHART (SectionName, InitializeChart) ; 64

65 INITCHART Parameter description Description of input parameters: Parameter Data type Description CHARTREF SFCCHART_STATE Association with the SFC section to be controlled is done via the name of the section. If an SFC section is created then it is automatically assigned with a variable of data type SFCCHART_STATE. The variable that is created always has the name of the respective SFC section.) INIT_I BOOL 0->1: Reset all active steps in the sequence. 1->0: Start standard sequence (set initial step) Description of output parameters: Parameter Data type Description INIT_O BOOL 1: Sequence was started normally (on for only one cycle) 65

66 INITCHART 66

67 RESETSTEP: Reset a specific step in the sequence 14 Description Function description This procedure is to reset a step in a sequence. Note: The procedure can only be used in the operation mode "Multi-Token". This procedure resets the specific step. Since the step stays reset as long as this procedure is running (the procedure is run cyclically), you should take the following measures to prevent a permanent blocking of the sequence: Conditional call of the procedure RESETSTEP via the input EN. Conditional call of the procedure RESETSTEP via e.g. IF statement in the programming language ST. Use edge recognition (R_TRIG) at the input. When the last/only active step of the sequence is reset, the sequence can only be restarted with the function block SFCCNTRL (See Description, p. 72) (input INIT), the function INITCHART (See Description, p. 63) or the procedure SETSTEP (See Description, p. 69) or another external step activation command. DANGER Danger of unsafe, dangerous and destructive processes. RESETSTEP should not be used for finding error on controllers of machine tools, process or material management system if the are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. EN and ENO can be configured as additional parameters. 67

68 RESETSTEP Representation in FBD StepName RESETSTEP STEPNAME Representation in LD EN RESETSTEP ENO StepName STEPNAME Representation in IL Representation in ST Parameter description LD StepName RESETSTEP RESETSTEP (StepName); Description of the input parameter: Parameter Data type Meaning StepName SFCSTEP_STATE Assignment of the step to be reset via the name of the step. (If an SFC step is created then it is automatically assigned with a variable of data type SFCSTEP_STATE. The variable that is created always has the name of the respective SFC step. ) 68

69 SETSTEP: Set a specific step in the sequence 15 Description Function description This procedure is to set a step in a sequence. Note: The procedure can only be used in the operation mode "Multi-Token". This procedure sets the specific step, in addition to the already active step(s). Already active steps are not affected by this procedure. Since the step stays set as long as this procedure is running (the procedure is run cyclically), you should take the following measures to prevent a permanent setting of the sequence: Conditional call of the procedure SETSTEP via the input EN. Conditional call of the procedure SETSTEP via e.g. IF statement in the programming language ST. Use edge recognition (R_TRIG) at the input. DANGER Danger of unsafe, dangerous and destructive processes. SETSTEP should not be used for finding error on controllers of machine tools, process or material management system if the are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. EN and ENO can be configured as additional parameters. 69

70 SETSTEP Representation in FBD StepName SETSTEP STEPNAME Representation in LD EN SETSTEP ENO StepName STEPNAME Representation in IL Representation in ST Parameter description LD StepName SETSTEP SETSTEP (StepName); Description of the input parameter: Parameter Data type Meaning StepName SFCSTEP_STATE Assignment of the step to be set via the name of the step. (If an SFC step is created then it is automatically assigned with a variable of data type SFCSTEP_STATE. The variable that is created always has the name of the respective SFC step. ) 70

71 SFCCNTRL: SFC Control 16 Overview Introduction What's in this Chapter? This chapter describes the SFCCNTRL block. This chapter contains the following topics: Topic Page Description 72 Parameter description 77 71

72 SFCCNTRL Description Function description This function block is to control the execution sequences. For example, you can go through step by step, processing transition conditions can be turned on or off or the sequence can be reset to its initialization state. DANGER Danger of unsafe, dangerous and destructive processes. INIT, CLEAR, DISTRANS, DISACT, STEPUN and STEPDEP should not be used for finding errors when controlling machine tools, processes or material management systems, if they are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. EN and ENO can be configured as additional parameters. Representation in FBD SFCCNTRL_Instance SFCCNTRL SectionName InitializeChart ClearChart DisableTimeCheck DisableTransitions DisableActions StepUnconditional StepTransDependent ResetTimeErrors DisableRemoteControl CalcAllTransitions ResetStepTimes CHARTREF INIT CLEAR DISTIME DISTRANS DISACT STEPUN STEPDEP RESETERR DISRMODE ALLTRANS RESSTEPT INITST CLEARST TIMEDIS TRANSDIS ACTDIS MODECHG STATECHG TIMEERR TERRACT InitState ClearState TimeCheckDisabled TransitionsDisabled ActionsDisabled OperatingModeChanged StatusChanged TimeError PendingTimeError 72

73 SFCCNTRL 73 Representation in LD SFCCNTRL ENO EN SFCCNTRL_Instance SectionName InitializeChart ClearChart ClearState DisableTimeCheck TimeCheckDisabled DisableTransitions TransitionsDisabled DisableActions CHARTREF INIT CLEAR DISTIME DISTRANS DISACT CLEARST TIMEDIS TRANSDIS InitState INITST ActionsDisabled ACTDIS StepUnconditional STEPUN StepTransDependent ResetTimeErrors DisableRemoteControl STEPDEP RESETERR DISRMODE OperatingModeChanged StatusChanged TimeError MODECHG STATECHG TIMEERR PendingTimeError TERRACT CalcAllTransitions ResetStepTimes ALLTRANS RESSTEPT

74 SFCCNTRL Representation in IL Representation in ST CAL SFCCNTRL_Instance (CHARTREF:=SectionName, INIT:=InitializeChart, CLEAR:=ClearChart, DISTIME:=DisableTimeCheck, DISTRANS:=DisableTransitions, DISACT:=DisableActions, STEPUN:=StepUnconditional, STEPDEP:=StepTransDependent, RESETERR:=ResetTimeErrors, DISRMODE:=DisableRemoteControl, ALLTRANS:=CalcAllTransitions, RESSTEPT:=ResetStepTimes, INITST=>InitState, CLEARST=>ClearState, TIMEDIS=>TimeCheckDisabled, TRANSDIS=>TransitionsDisabled, ACTDIS=>ActionsDisabled, MODECHG=>OperatingModeChanged, STATECHG=>StatusChanged, TIMEERR=>TimeError, TERRACT=>PendingTimeError) SFCCNTRL_Instance (CHARTREF:=SectionName, INIT:=InitializeChart, CLEAR:=ClearChart, DISTIME:=DisableTimeCheck, DISTRANS:=DisableTransitions, DISACT:=DisableActions, STEPUN:=StepUnconditional, STEPDEP:=StepTransDependent, RESETERR:=ResetTimeErrors, DISRMODE:=DisableRemoteControl, ALLTRANS:=CalcAllTransitions, RESSTEPT:=ResetStepTimes, INITST=>InitState, CLEARST=>ClearState, TIMEDIS=>TimeCheckDisabled, TRANSDIS=>TransitionsDisabled, ACTDIS=>ActionsDisabled, MODECHG=>OperatingModeChanged, STATECHG=>StatusChanged, TIMEERR=>TimeError, TERRACT=>PendingTimeError) ; 74

75 SFCCNTRL Parameter description Description of input parameters: Parameter Data type Description CHARTREF SFCCHART_ STATE Association with the SFC section to be controlled is done via the name of the section If an SFC section is created then it is automatically assigned with a variable of data type SFCCHART_STATE. The variable that is created always has the name of the respective SFC section.) INIT BOOL 0->1: Reset all active steps in the sequence. 1->0: Start standard sequence (set initial step) CLEAR BOOL 0->1: Reset all active steps in the sequence. DISTIME BOOL 1: Turn off time monitoring DISTRANS BOOL 1: Turn of evaluation of the transitions (freeze sequence) DISACT BOOL 1: Turn off processing of the actions and reset all actions in the sequence STEPUN BOOL 0->1: Activate the next step, independent of the transition condition STEPDEP BOOL 0->1: Activate the next step, dependent on the transition condition RESETERR BOOL 0->1: Reset the time monitoring error. DISRMOTE BOOL 1: Prevent control of the sequence using processing parameters of the Online Animation Panel ALLTRANS BOOL 1: Calculate all transition sections RESSTEPT BOOL 0->1: Deactivate and reset time calculation 1->0: Restart time calculation 75

76 SFCCNTRL Description of output parameters: Parameter Data type Description INITST BOOL 1: Sequence was started normally (on for only one cycle) CLEARST BOOL 1: Sequence was reset, i.e. the sequence has no active step TIMEDIS BOOL 1: Time monitoring was turned off TRANSDIS BOOL 1: Evaluation of the transitions was turned off ACTDIS BOOL 1: Processing of the actions was turned off and all actions in the sequence were reset MODECHG BOOL 1: Operation mode of the sequence was changed (on for only one cycle) STATECHG BOOL 1: Status of the sequence was changed (on for only one cycle) TIMEERR BOOL 1: Error in the time monitoring has occurred (on for only one cycle) TERRACT BOOL 1: There is currently an error in the time monitoring 76

77 SFCCNTRL Parameter description General DANGER Danger of unsafe, dangerous and destructive processes. INIT, CLEAR, DISTRANS, DISACT, STEPUN and STEPDEP should not be used for finding errors when controlling machine tools, processes or material management systems, if they are running. Failure to follow this precaution will result in death, serious injury, or equipment damage. CHARTREF Association with the SFC to be controlled. If an SFC section is created then it is automatically assigned with a variable of data type SFCCHART_STATE. The variable that is created always has the name of the respective SFC section. This variable is used for assigning the function block SFCCNTRL to the SFC section to be controlled. 77

78 SFCCNTRL INIT Reset sequence and start normally. This input to the function block has the highest priority, above all other inputs. Reset sequence With a 0->1 Edge at the input, the sequence is stopped and all steps are reset. No operator access is possible. This status remains as long as the input is 1. The status (sequence reset) is shown with a 1 signal at the output CLEARST. Start sequence normally With a 1->0 edge at the input, the sequence is started normally, i.e. the initial step is activated. This is shown for one cycle with a 1 signal at the output INITST. Interaction of INIT, CLEAR, INITST and CLEARST: INIT CLEAR INITST (2) (2) (6) (4) (5) (1) (3) (1) (7) CLEARST (4) Interaction of INIT, CLEAR, INITST and CLEARST: Phase Description 1 If there is a 0->1 edge at input INIT, all steps in the sequence are reset and the output CLEARST is set to 1. 2 If there is a 1->0 edge at input INIT, the initial step in the sequence is set, the output INITST is set to 1 for one cycle and the output CLEARST is set to 0. 3 If there is a 0->1 edge at input INIT, all steps in the sequence are reset and the output CLEARST is set to 1. 4 A 1->0 edge at input CLEAR, has no influence on the state of the sequence or the outputs of the function block. 5 If the sequence is already in the status "reset", a 0->1 edge at input INIT, has no influence on the state of the sequence or the outputs of the function block. 6 If the sequence is already in the status "reset", a 0->1 edge at input CLEAR, has no influence on the state of the sequence or the outputs of the function block. 7 If there is a 1->0 edge at input INIT, the initial step in the sequence is set, the output INITST is set to 1 for one cycle and the output CLEARST is set to 0. This is also true when the input CLEAR is 1. 78