Concept IEC Block Library Part: DIAGNO

Transcription

1 Concept IEC Block Library Part: DIAGNO 840 USE eng Version Schneider Electric All Rights Reserved

2 2

3 Table of Contents Part I About the Book General information about the DIAGNO function block library Overview Chapter 1 Parameterizing functions and function blocks Parameterizing functions and function blocks Chapter 2 Diagnostics Overview System diagnostics Process diagnostics Part II EFB descriptions Overview Chapter 3 ACT_DIA: Action diagnostics Chapter 4 DYN_DIA: Dynamic diagnostics Chapter 5 ERR2HMI: Error to HMI Chapter 6 ERRMSG: Message for error buffer overflow Chapter 7 GRP_DIA: Signal group monitoring Chapter 8 LOCK_DIA: Locking diagnostics Chapter 9 PRE_DIA: Monitoring of process requirements Chapter 10 REA_DIA: Reaction diagnostics Chapter 11 XACT: Extended locking/action diagnostics Chapter 12 XLOCK: Extended locking diagnostics

4 Chapter 13 XACT_DIA: Extended action diagnostics Chapter 14 XDYN_DIA: Extended dynamic diagnostics Chapter 15 XGRP_DIA: Extended signal group monitoring Chapter 16 XLOCK_DIA: Extended locking diagnostics Chapter 17 XPRE_DIA: Extended process requirement monitoring Chapter 18 XREA_DIA: Extended reaction diagnostics Glossary Index

5 About the Book At a Glance Document Scope Validity Note This documentation is designed to help with the configuration of functions and function blocks. This documentation applies to Concept 2.6 under Microsoft Windows 98, Microsoft Windows 2000, Microsoft Windows XP and Microsoft Windows NT 4.x. Note: There is additional up to date tips in the README data file in Concept. Related Documents Title of Documentation Reference Number Concept Installation Instructions 840 USE Concept User Manual 840 USE Concept EFB User Manual 840 USE Concept LL984 Block Library 840 USE User Comments We welcome your comments about this document. You can reach us by at TECHCOMM@modicon.com 840 USE October

6 About the Book USE October 2002

7 General information about the DIAGNO function block library I Overview At a Glance What s in this Part? This section contains general information about the DIAGNO function block library. This part contains the following chapters: Chapter Chapter Name Page 1 Parameterizing functions and function blocks 9 2 Diagnostics USE October

8 General information USE October 2002

9 Parameterizing functions and function blocks 1 Parameterizing functions and function blocks 840 USE October

10 Parameterization General Each FFB consists of an operation, the operands needed for the operation and an instance name or function counter. FFB (e.g. ON-delay) Item name/ Function counter (e.g. FBI_2_22 (18)) Operation (e.g. TON) Operand Formal parameter (e.g. IN,PT,Q,ET) Actual parameter Variable, element of a multi-element variable, literal, direct address (e.g. ENABLE, EXP.1, TIME, ERROR, OUT, %4:0001) FBI_2_22 (18) TON ENABLE EXP.1 TIME EN IN PT ENO Q ET ERROR OUT %4:00001 Operation The operation determines which function is to be executed with the FFB, e.g. shift register, conversion operations. Operand The operand specifies what the operation is to be executed with. With FFBs, this consists of formal and actual parameters USE October 2002

11 Parameterization Formal/actual parameters The formal parameter holds the place for an operand. During parameterization, an actual parameter is assigned to the formal parameter. The actual parameter can be a variable, a multi-element variable, an element of a multi-element variable, a literal or a direct address. Conditional/ unconditional calls "Unconditional" or "conditional" calls are possible with each FFB. The condition is realized by pre-linking the input EN. l Displayed EN conditional calls (the FFB is only processed if EN = 1) l EN not displayed unconditional calls (FFB is always processed) Note: If the EN input is not parameterized, it must be disabled. Any input pin that is not parameterized is automatically assigned a "0" value. Therefore, the FFB should never be processed. Calling functions and function blocks in IL and ST Information on calling functions and function blocks in IL (Instruction List) and ST (Structured Text) can be found in the relevant chapters of the user manual. 840 USE October

12 Parameterization USE October 2002

13 Diagnostics 2 Overview At a Glance What do we mean by system diagnostics? What do we mean by process diagnostics? What s in this Chapter? Two subjects are summarized under the subject diagnostics: l System Diagnostics l Process Diagnostics System diagnostics deals with the analysis of the PLC status. It is part of the delivered system and always works without any programming. The process diagnostics observes the external PLC environment and recognizes whether or not the process devices are functioning in the specified mode. This chapter contains the following topics: Topic Page System diagnostics 14 Process diagnostics USE October

14 Diagnostics System diagnostics System diagnostics capabilities Mode of operation for system diagnostics Message display Concept offers the following self test capabilities: l Gathering of error conditions from bus modules l I/O l Communication l Comparing of programmed configuration with current configuration of bus modules l Parameter check of the function blocks These system diagnoses are part of the delivered system and always work without any programming. Error situations that arise outside the system, specifically in elementary function blocks, are automatically saved and will be displayed upon request. A message will automatically appear if there is at least one error message. Error messages have a number that identifies their type. Error messages from the programming unit are displayed as text in the "Event viewer". Double-clicks on the list text open the image of the section, where the respective EFB is located. Status information is also displayed automatically. Exceeding the time limits in the Steps of the SFC utilizes the same options, except that the step name is displayed instead of the EFB item name and that the open section is the respective SFC section USE October 2002

15 Diagnostics Process diagnostics Process diagnostics capabilities Mode of operation for process diagnostics Diagnostic base EFBs The process diagnostics observe the external PLC environment and report whether or not the process devices are functioning in default mode. The default behavior is set in the programming phase of the system and is reflected in the diagnostic functions of the runtime system. These diagnostic functions operate with a small subset of the input/output signals of the total process. In the actual process, this subset represents physically existing devices such as cylinders or motors together with their assigned limit switches. The process diagnostics is implemented with the use of EFBs. One special EFB is provided for each diagnostics type. The USR (user runtime system) downloads each EFB with the current parameters, which could also be the result of a link, only once. They can be executed several times and have separate data areas for each Instance. The diagnostic base EFBs are in the group "Diagnostics". The following diagnostic base EFBs are available: l ACT_DIA (See ACT_DIA: Action diagnostics, p. 19) Action diagnostics with optional motor-like behavior or pulse behavior l DYN_DIA (See DYN_DIA: Dynamic diagnostics, p. 27) Dynamic diagnostics l GRP_DIA (See GRP_DIA: Signal group monitoring, p. 41) Signal group monitoring l LOCK_DIA (See LOCK_DIA: Locking diagnostics, p. 45) Locking diagnostics without reaction input l PRE_DIA (See PRE_DIA: Monitoring of process requirements, p. 51) Monitoring of process requirements l REA_DIA (See REA_DIA: Reaction diagnostics, p. 55) Reaction diagnostics 840 USE October

16 Diagnostics Extended diagnostics EFBs The extended diagnostics EFBs are in the group "Extended". These function blocks can be used for visualization of the diagnostics in conjunction with one of the following programs: l Diagnostics Viewer in Concept (Online Online-Diagnostics...) l various diagnostics software Note: This additional diagnostic information can only be utilized when using function blocks in the FBD (Function Block Dialog) programming language. The following extended diagnostics EFBs are available: l XACT (See XACT: Extended locking/action diagnostics, p. 59) Extended combination of locking and action diagnostics l XACT_DIA (See XACT_DIA: Extended action diagnostics, p. 71) Extended action diagnostics with optional motor-like behavior or pulse behavior l XDYN_DIA (See XDYN_DIA: Extended dynamic diagnostics, p. 79) Extended dynamic diagnostics l XGRP_DIA (See XGRP_DIA: Extended signal group monitoring, p. 85) Extended signal group monitoring l XLOCK (See XLOCK: Extended locking diagnostics, p. 65) Extended locking diagnostics with reaction input l XLOCK_DIA (See XLOCK_DIA: Extended locking diagnostics, p. 89) Extended locking diagnostics without reaction input l XPRE_DIA (See XPRE_DIA: Extended process requirement monitoring, p. 95) Extended monitoring of process requirements l XREA_DIA (See XREA_DIA: Extended reaction diagnostics, p. 99) Extended reaction diagnostics USE October 2002

17 EFB descriptions II Overview At a Glance These EFB descriptions are documented in alphabetical order. Note: The number of certain EFB inputs can be increased up to a maximum of 32 by vertically modifying the size of the FFB symbol. Refer to the description of the individual EFBs to determine which ones are concerned. 840 USE October

18 EFB descriptions What s in this Part? This part contains the following chapters: Chapter Chapter Name Page 3 ACT_DIA: Action diagnostics 19 4 DYN_DIA: Dynamic diagnostics 27 5 ERR2HMI: Error to HMI 33 6 ERRMSG: Message for error buffer overflow 37 7 GRP_DIA: Signal group monitoring 41 8 LOCK_DIA: Locking diagnostics 45 9 PRE_DIA: Monitoring of process requirements REA_DIA: Reaction diagnostics XACT: Extended locking/action diagnostics XLOCK: Extended locking diagnostics XACT_DIA: Extended action diagnostics XDYN_DIA: Extended dynamic diagnostics XGRP_DIA: Extended signal group monitoring XLOCK_DIA: Extended locking diagnostics XPRE_DIA: Extended process requirement monitoring XREA_DIA: Extended reaction diagnostics USE October 2002

19 ACT_DIA: Action diagnostics 3 Overview At a Glance What s in this Chapter? This chapter describes the ACT_DIA block. This chapter contains the following topics: Topic Page Brief description 20 Representation 21 Detailed description 21 ACT_DIA: M behavior 22 ACT_DIA: I behavior 23 ACT_DIA: MI behavior USE October

20 ACT_DIA: Action diagnostics Brief description Function description The function block ACT_DIA is used for action diagnostics. Action diagnostics is initiated when the defined action becomes active. This action initiates an operation in the process. This operation has to trigger a set reaction. This reaction mostly occurs with a set delay. However, if the reaction does not occur within the tolerance time DTIME, an error situation arises and the error output ERR becomes active. Contrary to the Locking diagnostics, in which the trigger of the diagnostics must remain active at all times, the behavior of the trigger (action) in action diagnostics can vary. There are 3 different types of behavior: l M behavior l I behavior l MI behavior These alternatives vary in the behavior of the diagnostics if the action signal becomes "0" before an authorized value is placed at the reaction input. The monitoring is performed cyclically. The activation of the diagnostics and at the same time the distribution of the cycle load can be achieved through the enable signal "ED". Note: NEVER use diagnostic EFBs in DFBs. EN and ENO can be projected as additional parameters USE October 2002

21 ACT_DIA: Action diagnostics Representation Symbol Block representation: ACT_DIA ED ERR TIME DTIME ACT REACT SWITCH Parameter description Block parameter description: Parameter Data type Meaning ED Enable diagnostics DTIME TIME Tolerance time ACT Action signal REACT Reaction signal SWITCH M/I switch; 0: M behavior, 1: I behavior, 0/1: MI behavior ERR Error message; 0: no error; 1: Error Detailed description Parameterization In order to control the different modes of behavior (M, I, MI), the appropriate value must be set at SWITCH. Behavior SWITCH M behavior 0 I behavior 1 MI behavior 0 -> 1 (value modification within selected time) 840 USE October

22 ACT_DIA: Action diagnostics ACT_DIA: M behavior Motor-like behavior Timing diagram If the ACT input becomes "1" and REACT does not, the internal counter will be started. If the action becomes inactive during processing, the monitoring time is stopped/ reset or in the event of an error, the error processing is stopped. When the default time at the DTIME input has expired, the ERR output will display an error; it remains active until ACTION becomes "0", REACT becomes "1" or the diagnostics is deactivated. If the tolerance time (DTIME) is entered as "0", an error message is displayed as soon as an error situation occurs. An example for the process of an action diagnostics with M behavior is given in the timing diagram. M behavior timing diagram ED ACT REACT DTIME (2) (1) (3) (1) (4) (1) (1) (5) (6) (5) (7) ERR SWITCH 1. The internal time will start when ACT is "1" and REACT is "0". 2. The internal time is stopped/reset when ACT is "0". 3. The internal time is stopped/reset when REACT becomes "1". 4. Once the reaction has been detected, it is insignificant whether or not ACT is active. 5. If the internal time reaches the DTIME value, an error is reported. 6. The error is cancelled and the internal time stopped/reset when REACT becomes "1". 7. The error is cancelled and the internal time stopped/reset, if the enable signal ED is "0" USE October 2002

23 ACT_DIA: Action diagnostics ACT_DIA: I behavior Pulse behavior Timing diagram After a transition of the action signal has been detected, diagnostics is activated and the monitoring time will start. The valency of the action signal is no longer significant. When the default time at the DTIME input has expired, the ERR output will display an error; it remains active until REACT becomes "1" or diagnostics is deactivated. The diagnostics will only be terminated (different from the M behavior) with the incoming defined reaction. In order to allow the diagnostics to be terminated in case of error, the ED enable signal has to be projected. If the tolerance time (DTIME) is entered as "0", an error message is displayed as soon as an error situation occurs. An example for the process of an action diagnostics with I behavior is given in the timing diagram. I behavior timing diagram ED ACT REACT (5) (6) DTIME (1) (2) (1) (1) (3) (4) (3) (7) ERR SWITCH 1. The internal time will start when ACT is "1" and REACT is "0". 2. The internal time is stopped/reset when REACT becomes "1". 3. If the internal time reaches the DTIME value, an error is reported. 4. The error is cancelled and the internal time stopped/reset when REACT becomes "1". 5. If the action diagnostics are still in progress (e.g., error handling), a positive transition of the action has no significance. 6. If the action diagnostics are still in progress (e.g., error handling), a negative transition of the action has no significance. 7. The error is cancelled and the internal time stopped/reset, if the enable signal ED is "0". 840 USE October

24 ACT_DIA: Action diagnostics ACT_DIA: MI behavior MI behavior In the MI behavior, the monitoring begins with M behavior. If the SWITCH signal becomes active during monitoring (transition), the diagnostics switches to I behavior. This is a one-time switch and it is not possible to change back to M behavior during this monitoring cycle. Since action diagnostics with I behavior can only be terminated via the defined reaction or the ED enable signal, the enable signal has to be projected in the MI behavior as well. If the tolerance time (DTIME) is entered as "0", an error message is displayed as soon as an error situation occurs. An example for the process of an action diagnostics with MI behavior is given in the timing diagram USE October 2002

25 ACT_DIA: Action diagnostics Timing diagram MI behavior timing diagram M behavior I behavior M behavior ED (9) ACT REACT (1) (5) (7) (4) (8) DTIME (2) (3) (6) ERR SWITCH 1. The internal time will start when ACT is "1" and REACT is "0". 2. If the internal time reaches the DTIME value, an error is reported. 3. With M behavior, the error will be cancelled, and the internal time stopped/reset when ACT becomes "0". 4. If SWITCH is "1" and ACT becomes "1", the diagnostics will switch from M behavior to I behavior. The internal time will also start when ACT is "1" and REACT is "0". 5. If the action diagnostics is still in progress (e.g. internal time started) during I behavior, a negative transition of the action has no significance. 6. If the internal time reaches the DTIME value, an error is reported. 7. If the action diagnostics is still in progress (e.g. internal time started) during I behavior, a positive transition of the action has no significance. 8. The error is cancelled and the internal time stopped/reset, if the enable signal ED is "0". 9. If the enable signal ED returns to "1" or REACT becomes "1", a switch from I behavior to M behavior occurs. 840 USE October

26 ACT_DIA: Action diagnostics USE October 2002

27 DYN_DIA: Dynamic diagnostics 4 Overview At a Glance What s in this Chapter? This chapter describes the DYN_DIA block. This chapter contains the following topics: Topic Page Brief description 28 Representation 29 Detailed description USE October

28 DYN_DIA: Dynamic diagnostics Brief description Function description The function block DYN_DIA is used for dynamic diagnostics. Some processes require that LOCK_DIA (Locking diagnostics), ACT_DIA (Action diagnostics) and REA_DIA (reaction diagnostics) are combined into one unit that monitors the momentary condition of the diagnostics. This is only possible using a special function block, which internally manages the current diagnostics status. To prevent this function block becoming too complex, only one ED enable signal and one ERR error output were defined. The monitoring is performed cyclically. Activation of the diagnostics and, at the same time, distribution of the cycle load can be achieved through the enable signal ED. Note: NEVER use diagnostic EFBs in DFBs. EN and ENO can be projected as additional parameters USE October 2002

29 DYN_DIA: Dynamic diagnostics Representation Symbol Block representation: DYN_DIA ED ERR TIME DTIMEL TIME DTIMEA TIME DTIMER TRIGR ACT UNLOCK REACT SWITCH STOP Parameter description Block parameter description: Parameter Data type Meaning ED Enable diagnostics DTIMEL TIME Tolerance time LOCK_DIA (locking diagnostics) DTIMEA TIME Tolerance time ACT_DIA (action diagnostics) DTIMER TIME Tolerance time REA_DIA (reaction diagnostics) TRIGR Trigger UNLOCK Locking REACT Reaction signal SWITCH M/I switch; 0: M behavior, 1: I behavior, 0/1: MI behavior STOP Stop signal ERR Error message; 0: No error; 1: Error ACT Action enabling 840 USE October

30 DYN_DIA: Dynamic diagnostics Detailed description Parameterization Note: The ACT output is created from TRIGR and UNLOCK with a logical AND. Other inputs (e.g. ED) have no effect on this. Representation of the relevant inputs for the ACT output TRIGR UNLOCK AND ACT The parameterization of the individual diagnostics types can be found in the descriptions for LOCK_DIA, ACT_DIA and REA_DIA. An individual tolerance time (DTIMEL, DTIMEA, DTIMER) can be parametered for every diagnostics type. An example for the process of dynamic diagnostics is given in the timing diagram USE October 2002

31 DYN_DIA: Dynamic diagnostics Timing diagram Timing diagram for dynamic diagnostics Locking diagnostics Action diagnostics M behavior I beh. ED Reaction Diagnostics TRIGR UNLOCK (3) ACT (7) REACT (9) DTIMER DTIMEL DTIMEA (1) (10) ERR (2) (4) (5) (8) (11) SWITCH (6) (12) STOP 1. The internal time starts when TRIGR is "1" and UNLOCK is "0". 2. If the internal time reaches the DTIMEL value, an error will be reported. 3. If UNLOCK becomes "1", the error will be cancelled, the internal time is stopped/ reset, and ACT becomes "1". Activating the action switches to the action diagnostics. As the reaction has still not occurred, the internal time is started. 4. If the internal time reaches the DTIMEA value, an error will be reported. 5. With M behavior, the error will be cancelled, and the internal time stopped/reset when ACT becomes "0". 6. If SWITCH becomes "1" and ACT is "1", a switch from M behavior to I behavior occurs. The internal time will also start when ACT is "1" and REACT is "0". 7. If the action diagnostics is still in progress (e.g. internal time started), a negative transition of the action has no significance. 8. If the internal time reaches the DTIMEA value, an error will be reported. 9. If REACT becomes "1", the internal time is stopped/reset. By activating the reaction, the reaction diagnostics is switched. 10.The internal time will start when REACT becomes "0". 840 USE October

32 DYN_DIA: Dynamic diagnostics 11.If the internal time reaches the DTIMER value, an error will be reported. 12.The error will be cancelled and the internal time is stopped/reset when STOP becomes "1". By activating the stop signal, the locking diagnostics is switched again USE October 2002

33 ERR2HMI: Error to HMI 5 Overview At a Glance What s in this Chapter? This chapter describes the ERR2HMI block. This chapter contains the following topics: Topic Page Brief description 34 Representation USE October

34 ERR2HMI: Error to HMI Brief description Function description The function block ERR2HMI is used to make error data from the internal PLC error buffer, which is detected by the diagnostic EFBs and the sequential function chart, available for diagnostic display in visualization. The PLC error buffer is part of the runtime system and provides no interface for direct external access. EFBs, that read data from the error buffer and forward it to the corresponding receiver, are used to make the error data available for visualization. The diagnostics communicates with the block via both the PCV_IN and PCV_OUT data structures. Jobs are assigned to the block in PCV_IN. The result is written to PCV_OUT by the block. PCV_OUT is read by the diagnostic display. Only one ERR2HMI block may be projected per diagnostic display. Note: NEVER use diagnostic EFBs in DFBs. EN and ENO can be projected as additional parameters. Representation Symbol Block representation: ERR2HMI PCV_IN STR_IN STR_OUT PCV_OUT MODE INT Parameter description Block parameter description: Parameters Data type Meaning STR_IN PCV_IN Input data structure STR_OUT PCV_OUT Output data structure MODE INT 0 = active, 1 = communication interrupted Description of the PCV_IN elements: Element Data type Meaning Job INT Processing job for block Parameter INT Parameters for specific jobs, e.g., error selection USE October 2002

35 ERR2HMI: Error to HMI Description of the PCV_OUT elements: Element Data type Meaning response INT Processing status: 0 = o.k. counter INT Write counter of error buffer st_feld [1]... st_feld [64] INT Status fields for the 64 possible error entries length INT Length of error entry class INT Error class type INT Error type drop INT Drop number q_status INT Acknowledgement status m_status INT Message status t_comes DINT Time stamp when error event occurs t_comes_ms INT Time stamp when error event occurs blob_id INT Internal ID character t_goes DINT Time stamp when error event ends t_goes_ms INT Time stamp when error event ends scan_index INT Reference to diagnostic block blob_adr DINT internal address blob_gen_time DINT Time of generation trans_id INT References to transition nmb_signals INT Number of error signals error_list [1]... fehler_liste [20] INT Reference to faulty signals Note: Both data structures, PCV_IN and PCV_OUT, are only used for communication with the diagnostic display and may not be manipulated by the user. 840 USE October

36 ERR2HMI: Error to HMI USE October 2002

37 ERRMSG: Message for error buffer overflow 6 Overview At a Glance What s in this Chapter? This chapter describes the ERRMSG block. This chapter contains the following topics: Topic Page Brief description 38 Representation 39 Detailed description USE October

38 ERRMSG: Message for error buffer overflow Brief description Function description The function block ERRMSG is used to display error buffer status information. A display shows whether there has been a buffer overflow, and a counter measures the number of lost entries. These values are standardized during the initialization of the error buffer (load program, reset error buffer). Note: NEVER use diagnostic EFBs in DFBs. EN and ENO can be projected as additional parameters USE October 2002

39 ERRMSG: Message for error buffer overflow Representation Symbol Representation of the block: ERRMSG Clear ErrCount INT Overflow OvlCount INT MsgValid LastMsg INT Parameter description Block parameter description: Parameters Data type Meaning Clear A 0 -> 1 edge standardizes the inputs to: l ErrCount = current value l Overflow = 0 l OvlCount = 0 l MsgValid = 0 l LastMsg = 0 ErrCount INT Shows the number of current entries in the error buffer Overflow 1 = An error should be entered in the buffer, but there is no space available for this entry. The output is reset when an error entry is deleted, thus making room for a new entry. OvlCount INT Shows how often the overflow output has been set, i.e. how many entries into the error buffer were lost. MsgValid 1 = The error displayed in LastMsg is current. 0 = The error displayed in Last Msg is no longer valid. LastMsg INT Display of the last Status (See Error buffer status, p. 40) encountered in the error buffer. The display remains until a standardization (input clear) is performed. The display s validity is shown in MsgValid. 840 USE October

40 ERRMSG: Message for error buffer overflow Detailed description Function description Error buffer status Error messages and error withdrawal can appear several times in one cycle, and the queries to the error buffer entries are added. This leads to an update of the output couple LastMsg and MsgValid respectively. The EFB reads the displayed values from the buffer at the point of execution, and thus displays a momentary record which cannot make every state in the buffer available. As the number of overflows (data loss) is summed up at the OvlCount output, this value can still be read later. The following messages have been defined: Value Meaning Message in the event viewer 0 no error Buffer full Insufficient memory for error buffer Diagnostics not installed Error buffer is not present Memory error Memory management error Error index invalid Incorrect error ID MMI not logged in Incorrect MMI ID MMI log-on not possible (too many MMI) MMI calculation terminated Diagnostics data (BLOB) not found BLOB not loaded Block instance not found No error data present for this element USE October 2002

41 GRP_DIA: Signal group monitoring 7 Overview At a Glance What s in this Chapter? This chapter describes the block. This chapter contains the following topics: Topic Page Brief description 42 Representation 42 Detailed description USE October

42 GRP_DIA: Signal group monitoring Brief description Function description The GRP_DIA function block is used for signal group monitoring. The monitoring is performed cyclically. The activation of the Diagnostics and thereby the distribution of the cycle load can be achieved through the enable signal "ED". Note: NEVER use diagnostic EFBs in DFBs. EN and ENO can be projected as additional parameters. Representation Symbol Block representation: GRP_DIA ED ERR TIME DTIME IN1 IN2 : : IN30 Parameter description Description of block parameter: Parameters Data type Meaning ED Enable diagnostics DTIME TIME Tolerance time IN1 1. Signal IN2 2. Signal : : : IN Signal ERR Error message; 0: no error; 1:error USE October 2002

43 GRP_DIA: Signal group monitoring Detailed description Parameterization The inputs IN1 and IN2 are monitored whether more than one input is "1". Deactivating the diagnostics or the attached correct values at the inputs will reset the internal counter to "0". When the default time at the DTIME input has expired, the ERR output displays an error; it remains active until less than two inputs are "1" or the diagnostics is deactivated. If a tolerance time (DTIME) of "0" is entered, an error message appears immediately if more than one input becomes "1". An example for the process of signal group monitoring is given in the timing diagram. Timing diagram Signal group monitoring timing diagram ED IN1 IN2 DTIME (1) (2) (3) (6) (4) (5) (7) (8) ERR 1. The internal time is started when IN1 and IN2 simultaneously become"1". 2. The internal time is stopped/reset when IN1 becomes "0". 3. The internal time is started when IN1 and IN2 simultaneously become"1". 4. If the internal time reaches the DTIME value, an error will be reported. 5. The error is cancelled and the internal time is stopped/reset when IN1 becomes "0". 6. The internal time is started when IN1 and IN2 simultaneously become"1". 7. If the internal time reaches the DTIME value, an error will be reported. 8. The error is cancelled and the internal time stopped/reset, if the enable signal ED is "0". 840 USE October

44 GRP_DIA: Signal group monitoring USE October 2002

45 LOCK_DIA: Locking diagnostics 8 Overview At a Glance What s in this Chapter? This chapter describes the LOCK_DIA block. This chapter contains the following topics: Topic Page Brief description 46 Representation 47 Detailed description USE October

46 LOCK_DIA: Locking diagnostics Brief description Function description The LOCK_DIA function block is used for locking diagnostics and to enable the action. Locking Diagnostics is activated when the input with the TRIGR signals becomes active. In control networks the trigger signal TRIGR (e.g. step counter, manual key) does not necessarily initiate the execution of an action directly, but is generally combined with locks from the process. It is therefore possible, that the action ACT only becomes active after a time delay or not at all. It is the task of lock diagnostics, to check whether UNLOCK is enabled within a tolerance time DTIME when the trigger signal is active. In this case the lock diagnostics enables the action ACT. In this instance the trigger signal TRIGR must be active throughout the entire time. An error situation exists, if the lock enabler UNLOCK does not appear within the time period (lock not free). In this instance the action output ACT does not become active, and the error output ERR is set. This error message is terminated when the trigger signal TRIGR is inactive or the lock enabler UNLOCK becomes active. The lock diagnostics is terminated with an active action output ACT. The monitoring is performed cyclically. Activation of the diagnostics and thereby distributing the cycle load can be achieved through the enable signal ED. The ED enable signal refers only to the activation of the diagnostics and has no effect on the ACT output. Note: Contrary to the LOCK-DIA function block, the XLOCK function block has a REACT input that allows the ACT output to be switched off or prevents its activation, respectively, without a locking error being reported. Note: NEVER use diagnostic EFBs in DFBs. The parameters EN and ENO can additionally be projected USE October 2002

47 LOCK_DIA: Locking diagnostics Representation Symbol Block representation: LOCK_DIA ED ERR TIME DTIME TRIGR ACT UNLOCK Parameter description Block parameter description: Parameters Data type Meaning ED Enable diagnostics DTIME TIME Tolerance time TRIGR Trigger signal UNLOCK Lock ERR Error message; 0: no error; 1: Error ACT Action output 840 USE October

48 LOCK_DIA: Locking diagnostics Detailed description Parameterization Note: The output is created with a logical AND from TRIGR and UNLOCK. Other inputs (e.g. ED) have no effect on this. Representation of the relevant inputs for the ACT output TRIGR UNLOCK REACT AND ACT If the TRIGR input (trigger signal) becomes "1" and UNLOCK doesn t, the internal counter will be started. When the default time at the DTIME input has expired, the ERR output will display an error; it remains active until TRIGR becomes "0", ACT becomes "1" or diagnostics is deactivated. If the trigger time (DTIME) is entered as "0", an error message is displayed as soon as an error situation occurs. An example for the process of a lock diagnostic is given in the timing diagram USE October 2002

49 LOCK_DIA: Locking diagnostics Timing diagram Locking diagnostics timing diagram ED TRIGR (7) UNLOCK DTIME (1) (1) (1) (1) (4) (5) (4) (8) ERR ACT (2) (3) (2) (6) (9) (6) 1. The internal time starts when TRIGR is "1" and UNLOCK is "0". 2. The internal time is stopped/reset and ACT becomes "1" when UNLOCK becomes "1". 3. ACT becomes "0" when UNLOCK becomes "0". 4. If the internal time reaches the DTIME value, an error will be reported. 5. The error is cancelled and the internal time stopped/reset when TRIGR becomes "0". 6. ACT becomes "0" when TRIGR becomes "0". 7. If UNLOCK is "1" and TRIGR is "0", the internal time does not start. 8. The error is cancelled and the internal time stopped/reset, if the enable signal ED becomes "0". 9. If TRIGR and UNLOCK are "1" and ED is "0", action becomes "1". ED has no effect on the ACT signal. 840 USE October

50 LOCK_DIA: Locking diagnostics USE October 2002

51 PRE_DIA: Monitoring of process requirements 9 Overview At a Glance What s in this Chapter? This chapter describes the PRE_DIA block. This chapter contains the following topics: Topic Page Brief description 52 Representation 52 Detailed description USE October

52 PRE_DIA: Monitoring of process requirements Brief description Function description The function block PRE_DIA is used for the monitoring process requirements. Process requirements are process characteristics that are absolutely necessary for the operation of the machine or system (e.g. coolant, emergency stop). General requirements are for example requirements for machine operating modes or basic settings The absence of such requirements is monitored. The monitoring is carried out cyclically. The activation of the diagnostics and thereby the distribution of the cycle load can be achieved through the enable signal ED. The number of inputs IN can be increased up to 30 by vertically modifying the size of the block. Note: NEVER use diagnostic EFBs in DFBs. EN and ENO can be projected as additional parameters. Representation Symbol Block representation: PRE_DIA ED ERR TIME DTIME IN1 IN2 : : IN30 Parameter description Block parameter description: Parameters Data type Meaning ED Enable diagnostics DTIME TIME Tolerance time IN1 1. Process requirement : : : IN Process requirement ERR Error message; 0: no error; 1: Error USE October 2002

53 PRE_DIA: Monitoring of process requirements Detailed description Parameterization If at least one of the signals connected to INx becomes "0" and the diagnostics is active, the internal counter will be started. Note: Please note that all visible and unlinked inputs are automatically assigned a "0", i.e. create only as many IN inputs as are actually needed. The deactivation of the diagnostics or of the attachment of the correct input value stops the counter (the requirements may contain errors during the tolerance time) and sets the counter back to "0". When the default time at the DTIME input has expired, the ERR output displays an error; it remains active until the requirements are "1" or the diagnostic is deactivated. If the tolerance time entered is DTIME "0", there is an immediate error message when the static conditional values (INx) become "0". An example showing the process of monitoring the process requirements can be found in the timing diagram. Timing diagram Timing diagram monitoring process requirements ED IN1 IN2 DTIME (1) (2) (1) (5) (3) (4) (3) (6) ERR 1. The internal time will start when IN2 becomes "0". 2. The internal time is stopped/reset when IN2 becomes "1". 3. If the internal time reaches the DTIME value, an error will be reported. 4. The error is cancelled and the internal time is stopped/reset when IN2 becomes "1". 5. The internal time will start when IN1 becomes "0". 6. The error is cancelled and the internal time stopped/reset, if the enable signal ED becomes "0". 840 USE October

54 PRE_DIA: Monitoring of process requirements USE October 2002

55 REA_DIA: Reaction diagnostics 10 Overview At a Glance What s in this Chapter? This chapter describes the REA_DIA block. This chapter contains the following topics: Topic Page Brief description 56 Representation 56 Detailed description USE October

56 REA_DIA: Reaction diagnostics Brief description Function description The function block REA_DIA is used for reaction Diagnostics. Once the expected reaction has occurred in the Action diagnostic, the reaction diagnostics check whether the process contains the status. The process reaction, defined as a term or a signal, is checked through the reaction diagnostics to determine whether the status is stable. During technical processes, it is possible that reactions change momentarily (e.g. hitting limit switches). In order for the reaction diagnostics not to activate the error message ERR directly in such a case, a tolerance time DTIME can be defined. An error signal occurs if this time is exceeded. The error signal becomes inactive when the reaction returns to the setpoint status or when the stop condition is met. The stop condition terminates reaction diagnostics. Monitoring is performed cyclically. Activation of the diagnostics and, at the same time, distribution of the cycle load can be achieved through the enable signal ED. Note: NEVER use diagnostic EFBs in DFBs. The parameters EN and ENO can additionally be projected. Representation Symbol Block representation: REA_DIA ED ERR TIME DTIME REACT STOP Parameter description Block parameter description: Parameters Data type Meaning ED Enable diagnostics DTIME TIME Tolerance time REACT Reaction signal STOP Stop signal ERR Error message; 0: no error; 1: Error USE October 2002

57 REA_DIA: Reaction diagnostics Detailed description Parameterization Timing diagram If the REACT input becomes "0", the internal counter will be started. When the default time at the DTIME input has expired, the ERR output will display an error; it remains active until REACT becomes "1", STOP becomes "1" or the diagnostic is deactivated. If the tolerance time (DTIME) is entered as "0", an error message is displayed as soon as an error situation occurs. An example for the process of a reaction diagnostic is given in the timing diagram. Reaction diagnostics timing diagram ED REACT DTIME (1) (2) (1) (3) (4) (1) (3) (1) (3) (6) (7) (8) ERR STOP (5) 1. The internal time will start when REACT becomes "0". 2. The internal time is stopped/reset when REACT becomes "1". 3. If the internal time reaches the DTIME value, an error will be reported. 4. The error is cancelled and the internal time stopped/reset when REACT becomes "1". 5. The error will be cancelled and the internal time is stopped/reset when STOP becomes "1". 6. The error is cancelled and the internal time stopped/reset, if the enable signal ED becomes "0". 7. If REACT becomes "1", when STOP is "1", the reaction diagnostic is not started. 8. If subsequently REACT becomes "0", the internal time is not started, even if STOP is "0" again. 840 USE October

58 REA_DIA: Reaction diagnostics USE October 2002

59 XACT: Extended locking/action diagnostics 11 Overview At a Glance What s in this Chapter? This chapter describes the XACT block. This chapter contains the following topics: Topic Page Brief description 60 Representation 62 Detailed description USE October

60 XACT: Extended locking/action diagnostics Brief description Function description The XACT function block provides a combination of locking and action Diagnostics. The Locking diagnostics are activated when the input with the TRIGR signals becomes active. In control networks the trigger signal TRIGR (e.g. step counter, manual key) does not necessarily initiate the execution of an action directly, but is generally combined with locks from the process. It is therefore possible that the action ACT only becomes active after a time delay or not at all. It is the task of lock diagnostics to check whether UNLOCK is enabled within a tolerance time (DTIMEL) when the trigger signal is active. In this case the lock diagnostics enable the action ACT. In this instance the trigger signal TRIGR must be active throughout the entire time. An error situation exists if the lock enabler UNLOCK does not appear within the time period, (lock not free). In this instance the action output ACT does not become active and the error output ERR is set. In addition, the logic at the UNLOCK input is analyzed and the error is entered in the error buffer. This error information is then displayed in a diagnostic signal on an attached MMI. This error message is terminated when the trigger signal TRIGR becomes inactive or the lock enabler UNLOCK becomes active. The REACT input provides for the ACT output to be switched off or, respectively, prevents its activation without a locking error being reported. Note: Please be sure that the REACT input is not negated. To switch off the action, REACT must have the value "1". An active ACT output terminates the locking diagnostics and starts the action diagnostics. The action diagnostics will be initiated when the defined ACT action becomes active. This action initiates an operation in the process, e.g. an output is set for putting the motor into standby operation. This operation has to trigger a specific reaction. This reaction mostly occurs with a set delay. However, if the reaction does not occur within the tolerance time DTIMEA, an error situation arises and the error output ERR becomes active. In addition, the logic at the REACT input is analyzed and the error is entered in the error buffer. This error information is then displayed in a diagnostic signal on an attached MMI. Monitoring is performed cyclically. Activation of the diagnostics and, at the same time, distribution of the cycle load can be achieved through the enable signal ED. The ED enable signal refers only to the activation of the diagnostics and has no effect on the ACT output of the locking diagnostics. A positive edge of the ED enable signal (regardless at what time), or the locking signal UNLOCK becoming inactive while the TRIGR signal is active (in the action diagnostics phase), resets the function block and starts it in the locking diagnostics state USE October 2002

61 XACT: Extended locking/action diagnostics Note: If in Concept in dialog Project Code generation options... you select the option Include diagnostics information, the function block provides additional diagnostics codes which can be evaluated using diagnostics software. The function block, however, only makes the diagnostics codes available, if it is used in the FBD programming language. Note: NEVER use diagnostic EFBs in DFBs. The parameters EN and ENO can additionally be projected. 840 USE October

62 XACT: Extended locking/action diagnostics Representation Symbol Block representation: XACT ED ERR TIME DTIMEL TIME DTIMEA INT STATION TRIGR ACT UNLOCK REACT Parameter description Block parameter description: Parameters Data type Meaning ED Enable diagnostics DTIMEL TIME Tolerance time for locking diagnostics DTIMEA TIME Tolerance time for action diagnostics STATION INT Drop number (if no entry is made, drop number "0" will be used). TRIGR Trigger signal UNLOCK Lock REACT Reaction input ERR Error message; 0: no error; 1: Error ACT Action output USE October 2002

63 XACT: Extended locking/action diagnostics Detailed description Locking diagnostics parameterization Note: The ACT output is created with a logical AND from TRIGR and UNLOCK. REACT must not be active in this situation. Other inputs (e.g. ED) have no effect on this. Representation of the relevant inputs for the ACT output TRIGR UNLOCK REACT AND ACT If the TRIGR input (trigger signal) becomes "1" and UNLOCK does not, the internal counter will be started. When the default time at the DTIMEL input has expired, the ERR output will display an error; it remains active until TRIGR becomes "0", ACT becomes "1" or the diagnostics are deactivated. If the trigger time (DTIMEL) is entered as "0", an error message is displayed as soon as an error situation occurs. A detailed example showing the process of locking diagnostics can be found in the locking diagnostics timing diagram. An active ACT output terminates the locking diagnostics and starts the action diagnostics. Action diagnostics parameterization If the ACT output becomes "1" and REACT does not, the internal counter will be started. If the action becomes inactive during processing, the monitoring time is stopped/ reset or in the event of an error, the error processing is stopped. When the default time at the DTIMEA input has expired, the ERR output will display an error; it remains active until ACT becomes "0", REACT becomes "1" or the diagnostics are deactivated. If the tolerance time (DTIMEA) is entered as "0", an error message is displayed as soon as an error situation occurs. An example for the process of lock / action diagnostics is given in the timing diagram. 840 USE October

64 XACT: Extended locking/action diagnostics Timing diagram Locking / action diagnostics timing diagram Locking diagnostics Action diagnostics Locking Action Diagnostics Diagnostics ED (6) TRIGR UNLOCK ACT (3) (3) EACT DTIMEL DTIMEA (1) (1) (2) (4) (5) (2) (4) (5) ERR 1. The internal time starts when TRIGR is "1" and UNLOCK is "0". 2. If the internal time reaches the DTIMEL value, an error will be reported. 3. If UNLOCK becomes "1", the error will be cancelled, the internal time is stopped/ reset, and ACT becomes "1". By activating the action, the action diagnostics are switched. As the reaction has not yet occurred, the internal time is started. 4. If the internal time reaches the DTIMEA value, an error will be reported. 5. The error is cancelled and the internal time stopped/reset when ACT becomes "0". 6. When ED becomes "0", the function block is reset and locking diagnostics will start USE October 2002

65 XLOCK: Extended locking diagnostics 12 Overview At a Glance What s in this Chapter? This chapter describes the XLOCK block. This chapter contains the following topics: Topic Page Brief description 66 Representation 67 Detailed description USE October

66 XLOCK: Extended locking diagnostics Brief description Function description The function block XLOCK is used for locking diagnostics and for enabling the action. Locking diagnostics are activated when the input with the TRIGR signals becomes active. In control networks the trigger signal TRIGR (e.g. step counter, manual key) does not necessarily initiate the execution of an action directly, but is generally combined with locks from the process. It is therefore possible that the action ACT only becomes active after a time delay or not at all. It is the task of lock diagnostics to check whether UNLOCK is enabled within a tolerance time DTIME when the trigger signal is active. In this case the lock diagnostics enable the action ACT. In this instance the trigger signal TRIGR must be active throughout the entire time. An error situation exists if the lock enable UNLOCK does not appear within the time period, (lock not freed). In this instance the action output ACT does not become active and the error output ERR is set. In addition, the logic at the UNLOCK input is analyzed and the error is entered in the error buffer. This error information is then displayed in a diagnostic signal on an attached MMI. This error message is terminated when the trigger signal TRIGR is inactive or the lock enable UNLOCK becomes active. Contrary to the LOCK_DIA and XLOCK_DIA function blocks, the XLOCK function block has a REACT input that allows the ACT output to be switched off or prevents its activation, respectively, without a locking error being reported. Note: Please be sure that the REACT input is not negated. To switch off the action, REACT must have the value "1". The lock diagnostics terminate with an active action output ACT. Monitoring is performed cyclically. Activation of the diagnostics and, at the same time, distribution of the cycle load can be achieved through the enable signal ED. The ED enable signal refers only to the activation of the diagnostics and has no effect on the ACT output. Note: If, in Concept, in the dialog Project Code generation options... you select the option Include diagnostics information, the function block provides additional diagnostics codes which can be evaluated using diagnostics software. The function block, however, only makes the diagnostics codes available, if used in the FBD programming language. Note: NEVER use diagnostic EFBs in DFBs. The parameters EN and ENO can additionally be projected USE October 2002