The library provides components to facilitate the implementation of an application based on the PackML standard. The names and structure of the data types provided in this library correspond to the definitions in ANSI/ISA TR88.00.02-2015.
Characteristics of the Library
|
Characteristic |
Value |
|---|---|
|
Library title |
PackML |
|
Company |
Schneider Electric |
|
Category |
Application > Solution > Packaging |
|
Component |
Packaging (Application Libraries and Templates > Packaging) |
|
Default namespace |
PackML |
|
Language model attribute |
|
|
Forward compatible library |
Yes (FCL) |
NOTE: For this library, qualified-access-only is set. The POUs, data structures, enumerations, and constants must be accessed using the namespace of the library. The default namespace of the library is PackML.
In conjunction with the library, the example project PackMLExample.project is provided. The example project demonstrates how to implement the components from the PackML library.
Your specific application requirements may be different from those assumed for any related examples, templates or architectures described herein. In that case, you will have to adapt the information provided in this and other related documents to your particular needs. To do so, you will need to consult the specific product documentation of the hardware and/or software components that you may add or substitute for any information specified in this documentation. Pay particular attention and conform to any safety information, different electrical requirements and normative standards that would apply to your adaptation.
|
|
|
REGULATORY INCOMPATIBILITY |
|
Be sure that all equipment applied and systems designed comply with all applicable local, regional and national regulations and standards. |
|
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
|
Step |
Action |
Comment |
|---|---|---|
|
1 |
In the EcoStruxure Machine Expert Logic Builder, execute the command New Project. |
– |
|
2 |
In the New Project dialog box, select From Example from the Project type list. |
– |
|
3 |
On the right-hand side of the New Project dialog box, select All from the Controller list. |
Result: Available examples are listed in the Matching Examples text box. |
|
4 |
Select your example from the Matching Examples list. |
– |
|
5 |
Enter a name for the new project, and select the file location. |
– |
|
6 |
Click the OK button. |
Result: A new project is created based on the selected example. |
The library contains the following function blocks and functions:
|
Function block / function |
Use |
|---|---|
|
Records time and production information. |
|
|
Verifies whether a change of operation mode is possible within the active state and performs consistency verifications on the definition of operation modes. |
|
|
Processes data provided by the administration tags and status tags and provides these to the visualization frames via the visualization interface input/output iq_stVisInterface of type ST_VisInterface. |
|
|
Verifies whether the given command can be accepted in the present state (according to the given operation mode definition). If so, it also returns the target state of the transition triggered by that command. |
|
|
Initializes in which states a change of operation mode is permitted for an operation mode. |
|
|
Initializes which states exist for an operation mode. |
|
|
Writes alarm messages into the administration tags Admin.Alarm[#] and Admin.AlarmHistory[#]. |
|
|
Writes advisory messages into the administration tag Admin.Warning[#]. |
|
|
Obtains the real-time clock (RTC) of the controller and converts it to the data type DateTimeArray. |
|
Enumeration |
Use |
|---|---|
|
Contains the commands to change the state within a given operation mode. Commands are used to transition from a Wait state to other states (for example, the Start command). Additionally, the commands Stop and Abort can be issued during any state (refer to the State Model Diagram). |
|
|
Contains predefined operation modes (for example, Producing). |
|
|
Contains the possible values that indicate the result of operations executed by the function block. |
|
|
Contains the possible states of which an operation mode can be comprised. |
|
Structure |
Use |
|---|---|
|
Provides the variables/tags which contain OEE (Overall Equipment Effectiveness) data (for example, downtime, reasons for downtime, etc). Furthermore production information can be provided by this variable (for example, alarm and state information). |
|
|
Provides the variables which mainly represent the control interface. By using these tags, operation modes can be selected, state transitions can be forced, and recipes as well as formats can be transmitted. |
|
|
Provides information to set an alarm message in the function FC_SetAlarm. |
|
|
Provides information to initialize the operation modes in the function block FB_ModeManager. |
|
|
Provides the variables which contain status information (such as which operation mode is active, which state is active, etc). |
|
|
Structure for visualization. |
|
|
Provides the machine diagnostic message number. |
|
|
Provides the ID and parameter of count products. |
|
|
Provides information of the parameter (id, name, unit, and value). |
|
|
Provides ID and parameter of ingredient |
|
|
Provides information about the downstream (subsequent) PackML machine. |
|
|
Provides information about a product. |
|
|
Provides the information whether the state exists and whether a change of operation mode is possible. The information is used to initialize the operation mode manager. |
|
|
Provides the date and time. |
Background frames
The FR_<BackgroundFrame> visualization frames (for example, FR_Control1024x768) are frames in the background to group the other frames, and to realize control and navigation functionalities.
|
Frame |
|---|
|
FR_Control1024x768 |
|
FR_Nav1024x768 |
|
FR_NavControl1024x768 |
|
FR_Control800x600 |
|
FR_Nav800x600 |
|
FR_NavControl800x600 |
State frames
The FR_<State> visualization frames (for example, FR_Stopped) are frames for each state of a model.
The frames are used by the FR_DynStateModel to display the single states of the state model for operation modes.
|
Frame |
|---|
|
FR_Aborted |
|
FR_Aborting |
|
FR_Clearing |
|
FR_Complete |
|
FR_Completing |
|
FR_Execute |
|
FR_Held |
|
FR_Holding |
|
FR_Idle |
|
FR_Resetting |
|
FR_Starting |
|
FR_Stopped |
|
FR_Stopping |
|
FR_Suspended |
|
FR_Suspending |
|
FR_UnHolding |
|
FR_UnSuspending |
Visualization frames
In addition to the individual tags, functions, and function blocks, the library contains some visualization frames, which dynamically generate an appropriate state model for the operation mode during online operation or display OEE (Overall Equipment Effectiveness) data.
|
Frame |
Use |
|---|---|
|
Displays an alarm list of the active alarms. |
|
|
Displays the alarm history. |
|
|
Displays the time the machine has been running in the present operation mode/state. |
|
|
Dynamically displays the visualization of the state model during online operation. |
|
|
Displays the operation time of the operation modes and their respective states. |
|
|
Displays the product counters of the consumables. |
|
|
Displays the product counters of the goods detected as not acceptable. |
|
|
Displays the product counters of the produced goods. |
|
|
Displays a list of the active advisories. |
|
|
Displays the PackTag Admin.StopReason. |
|
|
Monitors and controls the PackTag Admin.StatesDisabled. |
