Transcription

1 Weihenstephan Standards for S / S Program and State Management Siemens Industry Online Support

2 Warranty and liability Warranty and liability Note The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These Application Examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these Application Examples and other Siemens publications e.g. Catalogs the contents of the other documents have priority. We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of the Siemens AG. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions only form one element of such a concept. Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems, machines and components should only be connected to the enterprise network or the internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place. Additionally, Siemens guidance on appropriate security measures should be taken into account. For more information about industrial security, please visit Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under Entry-ID: , V1.0, 02/2017 2

3 1 Library Overview Table of contents Warranty and liability Library Overview Different user scenarios Hardware and software requirements Library resources List of the blocks LWeihStd_ProgramStateManager (FB 30450) LWeihStd_ConfigureDisabledPrograms (FC 30450) LWeihStd_ConfigureDisabledStates (FC 30451) PLC data types PLC tags Working with the Library Integrating the library into STEP Integrating the library blocks into STEP Notes and Support Related literature Contact History Entry-ID: , V1.0, 02/2017 3

4 1 Library Overview 1 Library Overview What you get This document describes the Program and State Management part of the LWeihStd block library. The block library provides you with the tested code with clearly defined interfaces. They can be used as a basis for your task to be implemented. A key concern of the document is to describe all blocks of the block library the functionality implemented through these blocks. Furthermore, this documentation shows possible fields of application and helps you integrate the library into your STEP 7 project using step-by-step instructions. Scope of application STEP 7 Professional V13 SP1 S CPU as of firmware S CPU as of firmware Entry-ID: , V1.0, 02/2017 4

5 1 Library Overview 1.1 Different user scenarios 1.1 Different user scenarios Possible application for the LWeihStd library A production machine consists of different machine programs (e.g. maintenance or production program) and states (e.g. stopped or aborting). The machine state can be controlled with commands (e.g. start or stop). The library LWeihStd provides a standardized program and state manager to control a machine. User defined code can be filled in an easy to use template structure. In addition a machine HMI or an upper level system (MES) can be connected by using the standardized machine interface. The Weihenstephan program and state manager is harmonized with the OMAC mode and state model. The goal of the harmonization is to ensure that the preparation of a machine for connection of a PDA (Production Data Acquisition) system in accordance with the Weihenstephan Standards also complies with OMAC (Open Modular Architecture Controls) requirements. Figure 1-1: Scenario overview (WS Protocol Version 08) More information on the Weihenstephan Standards for the food and beverage packaging industry can be found at the according homepage ( Entry-ID: , V1.0, 02/2017 5

6 1 Library Overview 1.1 Different user scenarios The following section shows a scenario for a possible application of the LWeihStd library: Scenario General information The LWeihStd library contains a function block for the program and state management according to WS Pack Version 08. Programs Production, Startup, Rundown, Clean, Changeover, Maintenance, Break and user-defined programs. Uniform states within a program Defined states, such as Stopped, Starting, Operating, Aborting, etc. can be used to handle the machine states within an operating mode. Users can individually remove states that are not used in compliance with the Weihenstephan guidelines. The machine functionality to be executed in the particular programs and states must be programmed by the user for the specific application. Programs and states according to WS Pack Version 08 The standard programs and the user-defined programs with their associated states defined by WS Pack V08 are listed in this section. The state machines of the Production, Startup, Rundown, Clean, Changeover, Maintenance, Break and the user-defined programs are typically a subset of the state machine of the Production program. Which states are used in the individual programs is not standardized and users can define them as required. The state model for the Production program should be considered as the maximum quantity structure, which can be reduced, but should not be increased. This means that the state machine of the Production program is always used and for smaller quantity structures, individual states are directly run-through or skipped. Figure 1-2: Example of a state machine for the Production program Entry-ID: , V1.0, 02/2017 6

7 1 Library Overview 1.1 Different user scenarios Figure 1-3: Example of a state machine for the Maintenance program Programs Table 1-1 Description of possible programs Number Program Description 0 Undefined (No Program) A machine was turned on, but no program for a special application function has been selected. Undefined may also be used to provide the information that a machine is ready for action, but not required ( No Order, No Activity ). 1 Production The machine is functioning as designed by the manufacturer. 2 Start Up Although the machine is functioning as designed by the manufacturer, it is running a startup program which ensures full production after a warm-up period as stipulated by regulations or for safety considerations, or in conjunction with container buffering machines. 4 Run Down Although the machine is functioning as designed by the manufacturer, it is running a stop program which ensures production stop after a run-down period as stipulated by regulations or for safety considerations, or in conjunction with container buffering machines. 8 Clean The machine is running the cleaning program. This program can consist of program steps which can be controlled independently of each another, for example the program step flush for the filling or closing machine, or the program headspace disinfection for the cleaning machine. 16 Changeover The machine is running the changeover program in which automatic machine adjustments are made depending on specific parameters. 32 Maintenance The machine is running the maintenance program in which the maintenance and service work are carried out. 64 Break The machine is running the break program. This ensures there is startup of the machine in accordance with regulations after a break UserProgram01 UserProgram09 The requirements for user-defined programs differ depending on the machine and application. Entry-ID: , V1.0, 02/2017 7

8 1 Library Overview 1.1 Different user scenarios States Table 1-2 Description of possible states Number State Description 0 Undefined Not a valid state. 1 Stopped The machine has electrical power, but is in a stationary state. This state allows the machine to communicate, but it is not yet initialized or ready to carry out its intended function. 2 Starting The machine is in production start. This is not to be confused with program Start up. An example might be the self test of a packing robot, which tests the functionality of the individual servo motors through a movement test. 4 Prepared The machine is ready to carry out its intended function. However, it is in a waiting state which was not recognized as a lack or tailback state and can automatically start again. 8 Lack The machine is not carrying out its intended function due to a lack detected by the sensor system in the inlet of the machine (Machine Stop). In machines which have multiple inlets, the lack state concerns the main inlet, namely concerns the goods (bottles, crates) which are transported to the filling machine (main machine) or from the filling machine. The lack in the inlet is an external failure, however due to its importance for the visualization and the technical reporting it is recorded separately. 16 Tailback The machine is not carrying out its intended function due to a tailback detected by the sensor system in the outlet of the machine (Machine Stop). In machines which have multiple outlets, the tailback state concerns the main outlet, namely concerns the goods (e. g. product, bottles, crates) which are transported to the filling machine (main machine) or from the filling machine. The tailback in the outlet is an external failure, however due to its importance for the visualization and the technical reporting it is recorded separately. 32/64 Lack/Tailback branch line The machine is not carrying out its intended function due to a lack in the secondary inlet or a tailback in the secondary outlet of the machine (Machine Stop). This state can only occur only in machines which have 2 or more inlets or outlets, whereby the secondary flow leads to resp. from a downstream or upstream machine in the filling system (e. g. packing or palletizing machine). The secondary flow concerns the goods (e. g. packaged good, packaging, packaging aid) which are transported away from the filling machine (main machine). The lack/tailback in the secondary flow is an external failure, however due to its importance for the visualization and the technical reporting it is recorded separately. Lacks/Tailbacks caused by other media (e. g. lack of compressed air) not processed in another machine of the packaging plant does not follow the state Lack or Tailback. 128 Operating The machine is carrying out its intended function (DIN EN 292-1). 256 Stopping The machine is being transferred to the stopped state (Stopped) by a controlled stop routine. This is not to be confused with the program Production Start Up / Run Down. Rather it concerns the internal machine routines for reaching a stationary state. An example would be the positioning of the packing head of a packing robot in the park position. Entry-ID: , V1.0, 02/2017 8

9 1 Library Overview 1.1 Different user scenarios 512 Aborting The machine is in the time period between the occurrence of the failure and the resulting end state (Emergency Stop) Equipment Failure Failure, which occurs in the machine itself and leads to a machine stop (in accordance with DIN 8782). In the operating state Equipment Failure the machine does not carry out its intended function (Machine Stop) due to an unpermitted deviation from the SET-state (Failure notice). The unpermitted deviation is parameterized in the controls as equipment failure External Failure A failure which is not attributable to the machine but which nonetheless leads to a machine stop (in accordance with DIN 8782). In the operating state External Failure, the machine does not carry out its intended function (Machine Stop) due to an unpermitted deviation from the SET-state (Failure notice) detected by the control system sensors. The unpermitted deviation is parameterized in the controls as an external failure. The external failures Lack, Tailback, and Lack/Tailback in Branch Line are recorded separately and therefore are not assigned to this operating state. Other lack or tailback situations are however considered External Failures (E.g. lack of compressed air) Emergency Stop State that occurs after pressing the emergency stop switch or the activation of another safety guard of a machine (E.g. door in safety circuit). A "safe mode" (Safe Motion), in which a machine continues to operate does not match the state Emergency Stop Holding The machine is in the time period between the holding and the resulting end state (Held, Equipment Failure, External Failure) Held The machine is not carrying out its intended function due to an unpermitted deviation from the SET-state detected by a control system sensor. The operator intervenes and stops the machine manually (E. g. by handoff). The cause of failure is classed by the operator as either equipment failure or external failure Idle The machine is ready to carry out its intended function. It is however in a waiting state and must first be brought into operation by the operators or by external automatic release Unholding The machine is in the time period between the release of held (Held, Equipment Failure, External Failure) by the operator and the resulting end state (Operating) Suspending The machine is in the time period between the initiation of Suspending and the resulting end state (Prepared, Lack, Tailback, Lack Branch Line or Tailback Branch Line) Unsuspending The machine is in the time period between the release of being suspended (Prepared, Lack, Tailback, Lack Branch Line or Tailback Branch Line) and the resulting end state (Operating) Resetting The machine is in the time period between the release after a stop (Stopped) and the resulting end state (Idle) Clearing The machine is in the time period between the release after an Emergency Stop by the operator and the resulting end state (Stopped). NOTE The program Undefined can t be disabled and includes always the full state machine. Entry-ID: , V1.0, 02/2017 9

10 1 Library Overview 1.1 Different user scenarios Control Commands Table 1-3 Possible control commands Number Control command 0 Undefined 1 Reset 2 Start 4 Stop 8 Hold 16 Unhold 32 Suspend 64 Unsuspend 128 Abort 256 Clear Program transitions Permitted change of the program Changing the program is only permitted in wait states (state type: Wait, e.g. Stopped, Idle, Prepared, Aborted, Held). The program change is only possible if the wait state also exists in the requested program. State transitions Examples of change a state Reason IDs A change is made from the Idle state to the Starting state with the Start command. If the current state is Operating and you want to change into a Suspended sub state (Prepared, Lack, Tailback, Lack Branch Line, and Tailback Branch Line) you must send Suspend command and in addition the respective reason ID (Table 1-4). If the current state is Starting, Operating or is in one of the Suspended branch states and you want to change into a Held sub state (Held, Equipment Failure, External Failure) you must send Hold command and in addition the respective reason ID (Table 1-4). Table 1-4 Possible reason IDs Number Reason ID 0 No Reason 1 Prepared 2 Lack 4 Tailback 8 Lack Branch Line 16 Tailback Branch Line 32 Held 64 Equipment Failure 128 External Failure Entry-ID: , V1.0, 02/

11 1 Library Overview 1.2 Hardware and software requirements 1.2 Hardware and software requirements Requirements for this library Hardware To be able to use the functionality of the library described in this document, the following hardware and software requirements must be met: Table 1-1 Hardware components No. Component Article number Alternative 1. CPU PN 6ES7513-1AL00-0AB0 Other S CPU with FW V Or CPU 1215C 6ES7215-1AG40-0XB0 Other S CPU with FW V4.1.1 Software Table 1-2 Software components No. Component Article number Quantity 3. Step7 Professional V13 SP1 6ES Or Step7 Basic V13 SP1 6ES Library resources What will you find in this section? Overall size The following section gives you an overview of the size of the blocks of the LWeihStd library needed for program and state management in the main and load memory. The overall size of all blocks used for program and state management of the LWeihStd library in the main memory is 13 Kbytes and 156 Kbytes in the load memory. Size of the individual blocks 1 Table 1-3 Size of blocks Block Symbol Size in main memory [Kbytes] Size in load memory [Kbytes] FB LWeihStd_ProgramStateManager FC LWeihStd_ConfigureDisabledPrograms FC LWeihStd_ConfigureDisabledStates DB instlweihstd_programstatemanager Instance data blocks (prefix instlweihstd_) are not delivered with the library. They will be generated automatically with the call of a function block. Entry-ID: , V1.0, 02/

12 2.1 List of the blocks What will you find in this section? This chapter lists and explains all blocks of the LWeihStd library used for program and state management. Before that, however, you are informed of the blocks that are essentially involved in the implementation of the functionality. 2.1 List of the blocks The following table lists all blocks of the LWeihStd library used for program and state management. Table 2-1 Blocks of the library Block Symbol Classification FB LWeihStd_ProgramStateManager In-house development FC LWeihStd_ConfigureDisabledPrograms In-house development FC LWeihStd_ConfigureDisabledStates In-house development Entry-ID: , V1.0, 02/

13 The following table explains all blocks of the LWeihStd library used for program and state management LWeihStd_ProgramStateManager (FB 30450) Figure Figure 2-1: Block diagram of LWeihStd_ProgramStateManager LWeihStd_ProgramStateManager UDInt Program ProgramCurrent UDInt ProgramChangeRequest ProgramRequested UDInt UDInt CntrlCmd ProgramChangeInProcess CmdChangeRequest StateCurrent UDInt UDInt ReasonID StateRequested UDInt enableeaninterface StateChangeInProcess ProductionProgramRequest ProductionProgramActive StartUpProgramRequest StartUpProgramActive RunDownProgramRequest RunDownProgramActive CleanProgramRequest CleanProgramActive ChangeoverProgramRequest ChangeoverProgramActive MaintenanceProgramRequest MaintenanceProgramActive BreakProgramRequest BreakProgramActive UserProgram01Request UserProgram01Active UserProgram02Request UserProgram02Active UserProgram03Request UserProgram03Active UserProgram04Request UserProgram04Active UserProgram05Request UserProgram05Active UserProgram06Request UserProgram06Active UserProgram07Request UserProgram07Active UserProgram08Request UserProgram08Active UserProgram09Request UserProgram09Active Entry-ID: , V1.0, 02/

14 ResetCmdRequest StoppedStateActive StartCmdRequest StartingStateActive StopCmdRequest PreparedStateActive HoldCmdRequest LackStateActive UnholdCmdRequest TailbackStateActive SuspendCmdRequest LackBranchLineStateActive UnsuspendCmdRequest TailbackBranchLineStateActi ve AbortCmdRequest OperatingStateActive ClearCmdRequest StoppingStateActive PreparedReasonID AbortingStateActive LackReasonID EquipmentFailureStateActive TailbackReasonID ExternalFailureStateActive LackBrLineReasonID EmergencyStopStateActive TailbackBrLineReasonID HoldingStateActive HeldReasonID HeldStateActive EquipmentFailureReasonID IdleStateActive ExternalFailureReasonID UnholdingStateActive SC SuspendingStateActive "LWeihStd_typ emanagerconfi guration" configuration UnsuspendingStateActive ResettingStateActive ClearingStateActive StatesDisabled diagnostics UDInt "LWeihStd_typ emanagerdiag nostics" Entry-ID: , V1.0, 02/

15 Principle of operation The function block LWeihStd_ProgramStateManager is the main block of Program and State Management part of LWeihStd library. It manages the transitions between the programs and states according to the Weihenstephan standard. Note If you want to use the boolean interface particularly in ladder, set input enableeaninterface := TRUE. Note The number of programs can be changed by changing the constant LWEIHSTD_MAX_PROGRAMS_UPPER_LIM. In this case the number of the inputs has to be changed respectively. Function characteristics Figure 2-2: Timing diagram of the LWeihStd_ProgramStateManager function block CntrlCmd Start Reset Stop CmdChangeRequest SC StateCurrent StateRequested Starting Idle Resetting Stopped Stopping Operating Idle Stopped StateChangeInProcess 1) 2) 3) 4) 5) 6) 7) 8) 9) 1. If CmdChangeRequest is not set, every CntrlCmd is ignored. 2. If CmdChangeRequest is set to TRUE and a valid CntrlCmd (in this case Reset) is set, the StateChangeInProcess bit is set and the StateRequested (in this case Idle) value is set (only wait states possible). A valid CntrlCmd is always necessary if the current state is a wait state. If the current state is an acting state (here Resetting), a rising edge at input SC is necessary to leave the state. If CmdChangeRequest is FALSE, the CntrlCmd (here Start) has already been set in the acting state (here Resetting) and the wait state (Idle) is reached through a rising edge at the input SC, the next acting state will not be reached automatically. For the change in the next wait state (here Operating) is a rising edge at CmdChangeRequest needed. 3. The StateChangeInProcess bit remains set until StateCurrent gets the same value as StateRequested. The StateRequested changes from Operating to Stopped, because in Starting state a valid Stop command was set. Entry-ID: , V1.0, 02/

16 Input parameters 4. The SC input is not level sensitive. If the SC input is already set when reaching the acting state, the Program and State Manager stays in the acting state as long as a rising edge at SC input is detected. 5. The SC command is not related to the CmdChangeRequest input. Even if CmdChangeRequest is FALSE, a state change can happen from acting to a wait state. 6. A new CntrlCmd can also be set if CmdChangeRequest is FALSE. If CmdChangeRequest changes to TRUE and the control command is valid in this wait state, the state will be changed. 7. If no valid control command for the current state is written to input, edges at CmdChangeRequest are ignored. To change from a wait to an acting state, CmdChangeRequest has to be TRUE and the according CntrlCmd has to be written to input CntrlCmd. 8. If no acting state is active the rising edge at the SC input is ignored. 9. If an invalid CntrlCmd is written to input CntrlCmd and CmdChangeRequest is set to TRUE, the control command is ignored and an entry is written to the diagnostics buffer of the FB. Table 2-2 LWeihStd_ProgramStateManager input parameters Parameter Data type Description Program UDInt Requested program if enableeaninterface = FALSE (default: LWEIHSTD_PROGRAM_UNDEFINED) ProgramChangeRequest TRUE: Request program if enableeaninterface = FALSE CntrlCmd UDInt Requested control command if enableeaninterface = FALSE (default: LWEIHSTD_CMD_UNDEFINED) CmdChangeRequest TRUE: Enable change into requested state if enableeaninterface = FALSE ReasonID UDInt Requested reasonid if enableaninterface = FALSE (default: LWEIHSTD_REASONID_NO_REASON) enableeaninterface TRUE: Enable boolean interface ProductionProgramRequ est TRUE: Request change to program Production if enableeaninterface = TRUE StartUpProgramRequest TRUE: Request change to program Startup if enableeaninterface = TRUE RunDownProgramReque st TRUE: Request change to program Rundown if enableeaninterface = TRUE CleanProgramRequest TRUE: Request change to program Clean if enableeaninterface = TRUE Entry-ID: , V1.0, 02/

17 Parameter Data type Description ChangeoverProgramReq uest MaintenanceProgramRe quest TRUE: Request change to program Changeover if enableeaninterface = TRUE TRUE: Request change to program Maintenance if enableeaninterface = TRUE BreakProgramRequest TRUE: Request change to program Break if enableeaninterface = TRUE UserProgram01Request TRUE: Request change to user-defined program 01 if enableeaninterface = TRUE UserProgram02Request TRUE: Request change to user-defined program 02 if enableeaninterface = TRUE UserProgram03Request TRUE: Request change to user-defined program 03 if enableeaninterface = TRUE UserProgram04Request TRUE: Request change to user-defined program 04 if enableeaninterface = TRUE UserProgram05Request TRUE: Request change to user-defined program 05 if enableeaninterface = TRUE UserProgram06Request TRUE: Request change to user-defined program 06 if enableeaninterface = TRUE UserProgram07Request TRUE: Request change to user-defined program 07 if enableeaninterface = TRUE UserProgram08Request TRUE: Request change to user-defined program 08 if enableeaninterface = TRUE UserProgram09Request TRUE: Request change to user-defined program 09 if enableeaninterface = TRUE ResetCmdRequest TRUE: Request control command Reset if enableeaninterface = TRUE StartCmdRequest TRUE: Request control command Start if enableeaninterface = TRUE StopCmdRequest TRUE: Request control command Stop if enableeaninterface = TRUE HoldCmdRequest TRUE: Request control command Hold if enableeaninterface = TRUE UnholdCmdRequest TRUE: Request control command Unhold if enableeaninterface = TRUE Entry-ID: , V1.0, 02/

18 Parameter Data type Description SuspendCmdRequest TRUE: Request control command Suspend if enableeaninterface = TRUE UnsuspendCmdRequest TRUE: Request control command Unsuspend if enableeaninterface = TRUE AbortCmdRequest TRUE: Request control command Abort if enableeaninterface = TRUE ClearCmdRequest TRUE: Request control command Clear if enableeaninterface = TRUE PreparedReasonID TRUE: Request reasonid Prepared if enableeaninterface = TRUE LackReasonID TRUE: Request reasonid Lack if enableeaninterface = TRUE TailbackReasonID TRUE: Request reasonid Tailback if enableeaninterface = TRUE LackBrLineReasonID TRUE: Request reasonid Lack Branch Line if enableeaninterface = TRUE TailbackBrLineReasonID TRUE: Request reasonid Tailback Branch Line if enableeaninterface = TRUE HeldReasonID TRUE: Request reasonid Held if enableeaninterface = TRUE EquipmentFailureReason ID TRUE: Request reasonid Equipment Failure if enableeaninterface = TRUE ExternalFailureReasonID TRUE: Request reasonid External Failure if enableeaninterface = TRUE SC State Change from FALSE to TRUE (rising edge) triggers state complete signal configuration "LWeihStd_typeMa nagerconfiguration" FB configuration Output parameters Table 2-3 LWeihStd_ProgramStateManager output parameters Parameter Data type Description ProgramCurrent UDInt Current program (default: LWEIHSTD_PROGRAM_UNDEFINED) ProgramRequested UDInt Requested program (default: 0) ProgramChangeInProces Program change in process Entry-ID: , V1.0, 02/

19 s Parameter Data type Description StateCurrent UDInt Current State (default: LWEIHSTD_STATE_STOPPED) StateRequested UDInt Requested State (default: 0) StateChangeInProcess State change in process ProductionProgramActive TRUE: Program Production is currently active StartUpProgramActive TRUE: ProgramStartup program is currently active RunDownProgramActive TRUE: Program Run Down program is currently active CleanProgramActive TRUE: Program Clean program is currently active ChangeoverProgramActi ve MaintenanceProgramActi ve TRUE: Program Changeover program is currently active TRUE: Program Maintenance program is currently active BreakProgramActive TRUE: Program Break program is currently active UserProgram01Active TRUE: User-defined program 01 is currently active UserProgram02Active TRUE: User-defined program 02 is currently active UserProgram03Active TRUE: User-defined program 03 is currently active UserProgram04Active TRUE: User-defined program 04 is currently active UserProgram05Active TRUE: User-defined program 05 is currently active UserProgram06Active TRUE: User-defined program 06 is currently active UserProgram07Active TRUE: User-defined program 07 is currently active UserProgram08Active TRUE: User-defined program 08 is currently active UserProgram09Active TRUE: User-defined program 09 is currently active StoppedStateActive TRUE: State Stopped is currently active StartingStateActive TRUE: State Starting is currently active PreparedStateActive TRUE: State Prepared is currently active Entry-ID: , V1.0, 02/

20 Parameter Data type Description LackStateActive TRUE: State Lack is currently active TailbackStateActive TRUE: State Tailback is currently active LackBranchLineStateActi ve TailbackBranchLineState Active TRUE: State Lack Branch Line is currently active TRUE: State Tailback Branch Line is currently active OperatingStateActive TRUE: State Execute is currently active StoppingStateActive TRUE: State Stopping is currently active AbortingStateActive TRUE: State Aborting is currently active(default: FALSE) EquipmentFailureStateAc tive ExternalFailureStateActiv e EmergencyStopStateActi ve TRUE: State Equipment Failure is currently active TRUE: State External Failure is currently active TRUE: State Emergency Stop is currently active HoldingStateActive TRUE: State Holding is currently active HeldStateActive TRUE: State Held is currently active IdleStateActive TRUE: State Idle is currently active UnholdingStateActive TRUE: State Unholding is currently active SuspendingStateActive TRUE: State Suspending is currently active UnsuspendingStateActiv e TRUE: State Unsuspending is currently active ResettingStateActive TRUE: State Resetting is currently active ClearingStateActive TRUE: State Clearing is currently active StatesDisabled UDInt Disabled states in current program (default: 0) diagnostics "LWeihStd_typeMa nagerdiagnostics" Diagnostics information of FB Entry-ID: , V1.0, 02/

21 Status and error displays Table 2-4 LWeihStd_ProgramStateManager diagnostics messages Status Meaning Remedy / notes 16#00 MSG_NO_MESSAGE Initial value 16#01 MSG_PROGRAM_CHANGED_SUCCESSFULLY Program changed successfully 16#02 MSG_STATE_CHANGED_SUCCESSFULLY State changed successfully 16#03 MSG_PROGRAM_ALREADY_ACTIVE Requested program already active 16#80 MSG_PROGRAM_NOT_DEFINED Program not defined 16#81 MSG_CMD_NOT_DEFINED Control command not defined 16#82 MSG_REQ_PROGRAM_NOT_CONFIGURED Requested program not configured 16#83 MSG_PROGRAM_TRANSITION_NOT_ALLOWED Program transition not allowed 16#84 MSG_CMD_NOT_ALLOWED Control command in this state not allowed 16#85 MSG_SC_NOT_ALLOWED SC in this state not allowed 16#86 MSG_STATE_CONFIG_FORCED State configuration forced to Weihenstephan standard (corrected configuration -> FB output DisabledStates) Entry-ID: , V1.0, 02/

22 2.2.2 LWeihStd_ConfigureDisabledPrograms (FC 30450) Figure Figure 2-3: Block diagram of LWeihStd_ConfigureDisabledPrograms LWeihStd_ConfigureDisabledPrograms ProductionProgramDisable disabledprograms Array[0.."LWEIHSTD_MAX_ PROGRAMS_UPPER_LIM"] of StartUpProgramDisable RunDownProgramDisable CleanProgramDisable ChangeoverProgramDisable MaintenanceProgramDisable BreakProgramDisable UserProgram01Disable UserProgram02Disable UserProgram03Disable UserProgram04Disable UserProgram05Disable UserProgram06Disable UserProgram07Disable UserProgram08Disable UserProgram09Disable Principle of operation This function allows the user to set the program configuration for the FB LWeihStd_ProgramStateManager easily. Of course it is also possible to set the program configuration directly in the FB LWeihStd_ProgramStateManager configuration. With the function the user has to set the associated inputs for the different programs to TRUE, e.g. MaintenanceProgramDisable := TRUE for disabling the program Maintenance. To write the program configuration from the function output to the according Program and State Manager, the output disabledprograms has to be connected to the configuration of the corresponding FB LWeihStd_ProgramStateManager. Entry-ID: , V1.0, 02/

23 NOTE The number of programs can be changed by changing the constant LWEIHSTD_MAX_PROGRAMS_UPPER_LIM. In this case the number of the inputs has to be changed respectively. Input parameters Table 2-5 LWeihStd_ConfigureDisabledPrograms input parameters Parameter Data type Description ProductionProgramDisable TRUE: Disable program Production StartUpProgramDisable TRUE: Disable program Start Up RunDownProgramDisable TRUE: Disable program Run Down CleanProgramDisable TRUE: Disable program Clean ChangeoverProgramDisable TRUE: Disable program Changeover MaintenanceProgramDisable TRUE: Disable program Maintenance BreakProgramDisable TRUE: Disable program Break UserProgram01Disable TRUE: Disable user-defined program 01 UserProgram02Disable TRUE: Disable user-defined program 02 UserProgram03Disable TRUE: Disable user-defined program 03 UserProgram04Disable TRUE: Disable user-defined program 04 UserProgram05Disable TRUE: Disable user-defined program 05 UserProgram06Disable TRUE: Disable user-defined program 06 UserProgram07Disable TRUE: Disable user-defined program 07 UserProgram08Disable TRUE: Disable user-defined program 08 UserProgram09Disable TRUE: Disable user-defined program 09 Output parameters Table 2-6 LWeihStd_ConfigureDisabledPrograms output parameters Parameter Data type Description disabledprograms Array[0.."LWEIHSTD_MAX_PRO GRAMS_UPPER_LIM"] of Disabled program configuration Index meaning see Table 1-1 Description of possible programs Example: Program Changeover Value 16 means the 5 th bit is set. Internally the ENCO instruction is used to evaluate the bit position: ENCO("LWEIHSTD_PROGRAM_CHA NGEOVER"). That means program Changeover can be configured using index 5 in array disabledprograms. Entry-ID: , V1.0, 02/

24 2.2.3 LWeihStd_ConfigureDisabledStates (FC 30451) Figure Figure 2-4: Block diagram of LWeihStd_ConfigureDisabledStates LWeihStd_ConfigureDisabledStates PreparedDisable disabledstates UDInt LackDisable TailbackDisable LackBranchLineDisable TailbackBranchLineDisable EquipmentFailureDisable ExternalFailureDisable HoldingDisable HeldDisable UnholdingDisable SuspendingDisable UnsuspendingDisable Principle of operation This function allows the user to set the state configuration for every program in LWeihStd_ProgramStateManager easily. Of course it is also possible to set the state configurations directly in the FB LWeihStd_ProgramStateManager configuration. With the function the user has to set the associated inputs for the different states to TRUE, e.g. LackDisable := TRUE for disabling the state Lack. The function generates a double integer value which represents the state configuration for one program. This value is bit coded and means that every bit represents a switch where states can be dis- or enabled for a program, e.g. disabling the state Held (value 16384) the bit number 14 has to be set to TRUE. As can be seen in the example the state numbers according to the Weihenstephan standard also define the bit numbers in the double integer value. See Table 1-2 Description of possible states To write the state configuration from the function output to the according Program and State Manager, the output disabledstates has to be connected to the configuration of the corresponding FB LWeihStd_ProgramStateManager. Entry-ID: , V1.0, 02/

25 NOTE According to the Weihenstephan standard some states are mandatory and cannot be disabled. If they are nevertheless disabled the Program and State Manager will enable these states automatically and provides the corrected configuration as a double integer value at output StatesDisabled. The same can happen to states that are declared as initial states. Input parameters Table 2-7 LWeihStd_ConfigureDisabledStates input parameters Parameter Data type Description PreparedDisable TRUE: Disable State Prepared LackDisable TRUE: Disable State Lack TailbackDisable TRUE: Disable State Tailback LackBranchLineDisable TRUE: Disable State Lack Branch Line TailbackBranchLineDisable TRUE: Disable State Tailback Branch Line EquipmentFailureDisable TRUE: Disable State Equipment Failure ExternalFailureDisable TRUE: Disable State External Failure HoldingDisable TRUE: Disable State Holding HeldDisable TRUE: Disable State Held UnholdingDisable TRUE: Disable State Unholding SuspendingDisable TRUE: Disable State Suspending UnsuspendingDisable TRUE: Disable State Unsuspending Output parameters Table 2-8 LWeihStd_ConfigureDisabledStates output parameters Parameter Data type Description disabledstates UDInt Disabled states configuration for one program Entry-ID: , V1.0, 02/

26 2.2.4 PLC data types LWeihStd_typeManagerConfiguration This type contains parameter to set the FB configuration. The parameter InitialProgram is the program with this the FB starts. If there is no valid program configured the default value 2 (program Start Up) is set automatically by the ProgramStateManager FB. The parameter initialheldsubstate is the default substate, which will be reached if no valid reason ID is set and hold command is sent. The parameter initialsuspendsubstate is the default substate, which will be reached if no valid reason ID is set and suspend command is sent. Note The initial held substate is automatically available in all programs where at least one state of the held tree is configured. Parts of the held tree are the states External Failure, Equipment Failure, Held, Holding and Unholding. If no valid value for initial held substate is set, the Held substate is automatically chosen as initial held substate internally. Note The initial suspended substate is automatically available in all programs where at least one state of the suspended tree is configured. Parts of the suspended tree are the states Lack, Tailback, Lack Branch Line, Tailback Branch Line, Prepared, Suspending and Unsuspending. If no valid value for initial suspended substate is set, the Prepared substate is automatically chosen as initial suspended substate internally. Entry-ID: , V1.0, 02/

27 Table 2-9: LWeihStd_typeManagerConfiguration Parameter Data type Description initialprogram UDInt Start program when FB is enabled: 1=Production, 2=Start Up, 4=RunDown, 8=Clean, 16=Changeover, 32=Maintenance, 64=Break, 128=User Program 01,..., 32768=User Program 09 (default: LWEIHSTD_PROGRAM_STARTUP) initialsuspendedsubstate UDInt Suspended substate when no ReasonID is set: 4=Prepared, 8=Lack, 16=Tailback, 32=Lack Br Line, 64=Tailback Br Line (default: LWEIHSTD_STATE_PREPARED) initialheldsubstate UDInt Held Substate when no ReasonID is set: 1024=Equipment Failure, 2048=External Failure, = Held (default: LWEIHSTD_STATE_HELD) disabledprograms disabledstatesinprograms Array[0.."LWEIHSTD_MAX _PROGRAMS_UPPER_LI M"] of Array[0.."LWEIHSTD_MAX _PROGRAMS_UPPER_LI M"] of UDInt TRUE: Disable Program xx Example: Program Changeover Value 16 means the 5 th bit is set. Internally the ENCO instruction is used to evaluate the bit position: ENCO("LWEIHSTD_PROGRAM_CHANGEOV ER"). That means program Changeover can be configured using index 5 in array disabledprograms. TRUE: Disable states in program (bit number = state number) (default: 0) Example: State 16384=Held is configured in bit 14. Entry-ID: , V1.0, 02/

28 LWeihStd_typeManagerDiagnostics This type contains diagnostics information for the ProgramStateManager FB. Table 2-10 LWeihStd_typeManagerDiagnostics Parameter Data type Description bufferindex Int Index of actual buffer entry (default: 0) buffer Array[0.."LWEIHSTD_DIAG_ BUFFER_UPPER_LIM"] of "LWeihStd_typeManagerDia gnosticentry" Diagnostics information Buffer LWeihStd_typeManagerDiagnosticEntry An entry in the diagnostic buffer will be made when a message occurs. Table 2-11 LWeihStd_typeManagerDiagnosticEntry Parameter Data type Description Timestamp DTL Timestamp for this entry (default: DTL# :00:00) ProgramCurrent UDInt Current Program (default: 0) StateCurrent UDInt Current state (default: 0) Program UDInt Requested Program (default: 0) CntrlCmd UDInt Requested control command (default: 0) ReasonID UDInt Requested reason ID (default: 0) SC State complete signal Message Byte Message for this entry (default: 16#00) Entry-ID: , V1.0, 02/

29 2.2.5 PLC tags Programs The PLC tag table LWeihStd_Manager includes user constants for programs, states, control commands and array boundaries. Table 2-12 Constants for programs Value Constant Meaning 0 LWEIHSTD_PROGRAM_UNDEFINED LWeihStd program Undefined 1 LWEIHSTD_PROGRAM_PRODUCTION LWeihStd program Production 2 LWEIHSTD_PROGRAM_STARTUP LWeihStd program Startup (OMAC PackMLV30 user-defined mode 01) 4 LWEIHSTD_PROGRAM_RUNDOWN LWeihStd program Rundown (OMAC PackMLV30 user-defined mode 02) 8 LWEIHSTD_PROGRAM_CLEAN LWeihStd program Clean (OMAC PackMLV30 user-defined mode 03) 16 LWEIHSTD_PROGRAM_CHANGEOVE R 32 LWEIHSTD_PROGRAM_MAINTENANC E LWeihStd program Changeover (OMAC PackMLV30 user-defined mode 04) LWeihStd program Maintenance 64 LWEIHSTD_PROGRAM_BREAK LWeihStd program Break (OMAC PackMLV30 user-defined mode 05) 128 LWEIHSTD_PROGRAM_USER_01 LWeihStd user-defined program 01 (OMAC PackMLV30 unit Mode Manual) 256 LWEIHSTD_PROGRAM_USER_02 LWeihStd user-defined program 02 (OMAC PackMLV30 user-defined mode 06) 512 LWEIHSTD_PROGRAM_USER_03 LWeihStd user-defined program 03 (OMAC PackMLV30 user-defined mode 07) 1024 LWEIHSTD_PROGRAM_USER_04 LWeihStd user-defined program 04 (OMAC PackMLV30 user-defined mode 08) 2048 LWEIHSTD_PROGRAM_USER_05 LWeihStd user-defined program 05 (OMAC PackMLV30 user-defined mode 09) 4096 LWEIHSTD_PROGRAM_USER_06 LWeihStd user-defined program 06 (OMAC PackMLV30 user-defined mode 10) 8192 LWEIHSTD_PROGRAM_USER_07 LWeihStd user-defined program 07 (OMAC PackMLV30 user-defined mode 11) LWEIHSTD_PROGRAM_USER_08 LWeihStd user-defined program 08 (OMAC PackMLV30 user-defined mode 12) LWEIHSTD_PROGRAM_USER_09 LWeihStd user-defined program 09 (OMAC PackMLV30 user-defined mode 13) Entry-ID: , V1.0, 02/

30 States Table 2-13 Constants for states Value Constant Meaning 0 LWEIHSTD_STATE_UNDEFINED LWeihStd state Undefined 1 LWEIHSTD_STATE_STOPPED LWeihStd state Stopped 2 LWEIHSTD_STATE_STARTING LWeihStd state Starting 4 LWEIHSTD_STATE_PREPARED LWeihStd state Prepared (OMAC PackMLV30 state Suspended + Alarm ID) 8 LWEIHSTD_STATE_LACK LWeihStd state Lack (OMAC PackMLV30 state Suspended + Alarm ID) 16 LWEIHSTD_STATE_TAILBACK LWeihStd state Tailback (OMAC PackMLV30 state Suspended + Alarm ID) 32 LWEIHSTD_STATE_LACK_BRANCH_LI NE 64 LWEIHSTD_STATE_TAILBACK_BRANC H_LINE LWeihStd state Lack branch line (OMAC PackMLV30 state Suspended + Alarm ID) LWeihStd state Tailback branch line (OMAC PackMLV30 state Suspended + Alarm ID) 128 LWEIHSTD_STATE_OPERATING LWeihStd state Operating (OMAC PackMLV30 state Execute) 256 LWEIHSTD_STATE_STOPPING LWeihStd state Stopping 512 LWEIHSTD_STATE_ABORTING LWeihStd state Aborting 1024 LWEIHSTD_STATE_EQUIPMENT_FAIL URE 2048 LWEIHSTD_STATE_EXTERNAL_FAILU RE 4096 LWEIHSTD_STATE_EMERGENCY_ST OP LWeihStd state Equipment failure (OMAC PackMLV30 state Held + Alarm ID) LWeihStd state External failure (OMAC PackMLV30 state Held + Alarm ID) LWeihStd state Emergency stop (OMAC PackMLV30 state Aborted) 8192 LWEIHSTD_STATE_HOLDING LWeihStd state Holding LWEIHSTD_STATE_HELD LWeihStd state Held (OMAC PackMLV30 state Held + Alarm ID) LWEIHSTD_STATE_IDLE LWeihStd state Idle LWEIHSTD_STATE_UNHOLDING LWeihStd state Unholding LWEIHSTD_STATE_SUSPENDING LWeihStd state Suspending LWEIHSTD_STATE_UNSUSPENDING LWeihStd state Unsuspending LWEIHSTD_STATE_RESETTING LWeihStd state Resetting LWEIHSTD_STATE_CLEARING LWeihStd state Clearing Entry-ID: , V1.0, 02/

31 Control commands Table 2-14 Constants for control commands Value Constant Meaning 0 LWEIHSTD_CMD_UNDEFINED LWeihStd control command Undefined 1 LWEIHSTD_CMD_RESET LWeihStd control command Reset 2 LWEIHSTD_CMD_START LWeihStd control command Start 4 LWEIHSTD_CMD_STOP LWeihStd control command Stop 8 LWEIHSTD_CMD_HOLD LWeihStd control command Hold 16 LWEIHSTD_CMD_UNHOLD LWeihStd control command Unhold 32 LWEIHSTD_CMD_SUSPEND LWeihStd control command Suspend 64 LWEIHSTD_CMD_UNSUSPEND LWeihStd control command Unsuspend 128 LWEIHSTD_CMD_ABORT LWeihStd control command Abort 256 LWEIHSTD_CMD_CLEAR LWeihStd control command Clear Array boundaries Table 2-15 Constants for Array boundaries Value Constant Meaning 14 LWEIHSTD_DIAG_BUFFER_UPPER_LI M 15 LWEIHSTD_MAX_PROGRAMS_UPPER _LIM Diagnostic buffer array upper boundary (0- based) (Maximum number of programs - 1) -> Array[0..LWEIHSTD_MAX_PROGRAMS_UP PER_LIM] Entry-ID: , V1.0, 02/

32 3 Working with the Library 3.1 Integrating the library into STEP 7 3 Working with the Library What will you find in this section? This chapter consists of instructions for integrating the LWeihStd library into your STEP 7 project and instructions for using the library blocks. 3.1 Integrating the library into STEP 7 The table below lists the steps for integrating the LWeihStd library into your STEP 7 project. Subsequently, you can use the blocks of the LWeihStd library. Note The following section assumes that a STEP 7 project exists. Table 3-1: Integrating the library into STEP 7 No. Action 1. Extract the library LWeihStd_V1_x_x.zip to a local folder. 2. In TIA Portal select Options -> Global libraries -> Open library 3. Browse to the file LWeihStd.al13. It can be found in the subfolder LWeihStd of the extracted zip file. 4. Open the global library in read-only mode. 5. The LWeihStd library is now available in the task card Global libraries Entry-ID: , V1.0, 02/

33 3 Working with the Library 3.2 Integrating the library blocks into STEP Integrating the library blocks into STEP 7 The table below lists the steps for integrating the blocks of the LWeihStd library into your STEP 7 program. Figure 3-1: Integrating the library blocks into STEP 7 Table 3-2: Integrating the library blocks into STEP 7 No. Action Note 1. Copy the LWeihStd_ProgramStateManager FB in subfolder 01_ProgramStateManagement -> S7-1200/S > LWeihStd_Blocks with Drag & Drop into the Program blocks in the PLC. Alternatively copy the whole folder LWeihStd_Blocks with Drag & Drop into the Program blocks in the PLC. In this case also additional and optional blocks of LWeihStd library are available in the user program (e.g. LWeihStd_ConfigureDisabledPrograms, LWeihStd_ConfigureDisabledStates). 2. Copy the folder LWeihStd_Tags in subfolder 01_ProgramStateManagemnt -> S7-1200/S with Drag & Drop into the PLC tags in the PLC. 3. Copy the folder LWeihStd_Types in subfolder 01_ProgramStateManagement -> S7-1200/S with Drag & Drop into the PLC data types in the PLC. 4. Now the blocks can be configured and called in the user program. Copy program blocks Copy PLC tags Copy PLC data types Entry-ID: , V1.0, 02/

34 4 Notes and Support 4 Notes and Support What will you find in this section? This chapter provides further support in handling the described LWeihStd library. Entry-ID: , V1.0, 02/

35 5 Related literature 5 Related literature Table 5-1 Topic \1\ Siemens Industry Online Support \2\ Download page of this entry \3\ Weihenstephan Standards Title / Link \4\ OMAC website Contact Siemens AG Digital Factory Division Factory Automation Production Machines DF FA PMA APC Frauenauracher Str Erlangen, Germany mailto: tech.team.motioncontrol@siemens.com 7 History Table 7-1 Version Date Modifications V1.0 01/2016 First version V1.0 02/2017 Adapted to LWeihStd V1.0.3 Entry-ID: , V1.0, 02/