The step-by-step development of a modular system will be used to demonstrate functional configuration. The resulting modular system is used to create a Feeder station, a demo assembly developed at the Esslingen University of Applied Sciences:
This film shows a cycle of the demo assembly in operation.
The tutorial is structured so that each chapter can be completed on its own (see figure below). Once the example machine has been visualized, the next step is to create a mechatronic modular system (feeder). The modular system for the feeder can be expanded to include disciplines. These can be created separately from each other. The purpose of every discipline is to create files such as a list of components or a schematic diagram.
Presentation of the example machine (Example Feeder):
- The diagram of the example machine serves as the basis for the Functional assembly.
- The functional assembly is used to create the abstract Mod. system.
- Next, the resulting architecture model is visualized (Architecture model).
Once the example machine has been visualized, the development of the Mechatronic is described as follows:
- In the first step, the basic architecture is defined (Create a mechatronic architecture model).
- Building on this, the components required for the feeder are specified (Develop mechatronic modular system).
- This then serves as the basis for configuring the feeder mechatronically (Configuration).
- The Generation of variants via disabler and the Generation of variants via parameterization are explained in separate sections.
A list of actuator and sensor components is used as an example to demonstrate how it is possible to create a text file from the mechatronic model using the Text discipline:
- The ListOfComponents is to be seen as the created results of a new discipline (see Task: Generate a ListOfComponents).
- The ListOfComponents discipline is then added to the existing mechatronic model for the feeder (Adding the ListsofComponents discipline to the mechatronic model).
- How it possible to use the plug-socket concept to create a list of components that differs in structure from the functional layer is demonstrated in the section Mechatronic model: Generating non-functional structures.
The ECAD discipline shows how a schematic for EPLAN Electric P8 can be created on the basis of the mechatronic model.
- The first step is to Create EPLAN Electric P8 components for this discipline.
- The EPLAN Electric P8 discipline is then added to the existing mechatronic model for the feeder (Adding the schematic discipline to the mechatronic model).
- The test at the end of the chapter Use formulas for plugs, sockets, and PLC inputs shows how to create a schematic that is aligned to the installed components on the basis of the plug-socket concept.
The Pro Panel discipline shows how a schematic for EPLAN Pro Panel can be created on the basis of the mechatronic model.
- The first step is to Creating EPLAN Pro Panel discipline components for this discipline.
- The EPLAN Pro Panel discipline is then added to the existing mechatronic model for the feeder (Expanding the mechatronic model with EPLAN Pro Panel components).
- The test at the end of the section on Setting a disabler for digital input cards shows how a cabinet that is adapted to the installed components can be created with the aid of the disabler concept.
The PLC discipline is used to show how to create a program for SIMATIC Step 7 based on the mechatronic model. This discipline is divided into four sections:
- The first section shows how a Step7 program is to be created for the Feeder example machine (Task 1 - Creating the Step 7 program for Feeder).
- In the second section addresses for the inputs and outputs are assigned (Task 2 - Allocating addresses for the inputs and outputs).
- The third section shows how a symbol table is created (Task 3 - Creating the symbol table).
- The last section shows how interrupt messages are inserted into the STEP 7 program (Task 4 - Inserting fault messages into the Step 7 code).
The Office discipline shows how to create a list of actuators and sensors in table form as a Word file on the basis of the mechatronic model:
- Word components are created first for this discipline (Creating Word components).
- The Word ListOfComponents is then added to the existing mechatronic model for the feeder (Adding ListofComponents to the mechatronic model).
- How it possible to use the plug-socket concept to create a list of components that differs in structure from the functional layer is demonstrated in the section Mechatronic model: Generating non-functional structures.
The GRAPH2D discipline does not reference the model of the example machine; for this reason, it has its own separate mechatronic model. The discipline shows to configure the office infrastructure with the help of the graphical diagram.
- A diagram configuration is created from the ground up (Create new diagram configuration).
- Container objects (floor, room) are defined as polygons and linked with Form-UIs to enable data to be entered (Expanding the configuration with nodes for floor and room and Configuration of tooltips for displaying Form-UIs).
- Devices and persons can be added as images to rooms. These can be linked using connections. Data can be added to these objects by way of Form-UI calls (Configuring connections).
- The devices receive slave objects with which they can be tagged and through which they can be linked in order to map an IT landscape (Configuring slave-nodes as labels).
- Container objects, devices, persons, and connections are assembled in a tool palette (Configuration of palette entries).
- Commands allow the creation of nodes from the project tree and the instantiation of new nodes and edges from the tool palette (Commands for inserting room components (RoomComponent) from the project tree and Test 7 - Insertion of nodes and connections from the palette).
The project generation via import shows how a complete configuration of the Feeder station is created on the basis of the mechatronics modular system via import wizard.
- The import of IMX and XML files is used to show how a configuration is created.
- it is shown how individual components are installed in the configuration on placeholders through the import of IMX and XML files.
- The import of an IMX file is used to show how components are placed on placeholders and extension points.
- In the completed configuration parameter values are et through the import of CSV files. This is shown with individual parameters of different types, but also with a parameter of the Map type that is filled with key-value pairs.
- A further scenario shows how the imports are triggered by means of actions in a configuration UI, instead of via the import wizard.
The application of the Job Server shows how a configuration of the Feeder station is created on the basis of the mechatronical modular system by the Job Server or, respectively, by the Worker registered at it.
- A Job definition is created in order to create a configuration via fileTrigger.
- It is shown how the Job definition is extended in order to store the created configuration in a specific local folder.
- The next step shows how the IMX file to be imported is changed in order to place components on placeholders and extension points.
- A further scenario shows how a Job is started from the browser in order to create a configuration of the Feeder station.
- The last section shows how key-value pairs are transferred to the URL by means of POST Job parameters in order to store these in a parameter in the configuration.
More: