 |
 |
 |
 |
 |
 |
 |
 |
| |
Provision of the basic functionalities and further packages
The basic technology for each software based on Automation Framework is provided by the Automation Framework components 'Component Framework', 'IDE' and 'ObjectStore'. |
| |
|
| |
|
 |
| |
 |
 |
| |
These basic components are shown in the figure above with white background. They are completed by functional components and packages, if required.
|
 |
| |
 |
 |
 |
| |
Component Framework
The Component Framework ...
- is the basis of the application: It manages the components and allows the easy reuse of all Microsoft.NET-based components according to the black box principle: If the interfaces of an integrated component meet the .NET standard, this component can communicate via the Component Framework.
- ensures the same significance of all components used in Automation Framework. That means, there are no certain indispensable components and the creation of your tool or suite is not done by extending a main component by lower-level PlugIns but by the integration of equal components.
- allows the XML-based configuration and extension of your tool or suite (list of used components, menus, toolbars, etc.).
- realizes the communication between integrated components via services (interfaces)... uses existing .NET standards. This guarantees the easy integration of foreign components and ensures the reuse of own components in a foreign context.
- provides an exception handling.
- allows the possible internationalization of your software by providing localization mechanisms for user interface elements.
- provides detailed tracing and exception information and thus simplifies the development of own components.
- manages the startup and shutdown order of the application and ensures that the components are loaded on demand. This reduces the startup time of the software.
- provides a detailed developer documentation including reference information for all public classes.
- provides preconfigured mediator components that are responsible for the data linkage of already existing tools.
|
 |
| |
|
 |
| |
|
 |
| |
 |
 |
 |
| |
Integrated Development Environment Package (IDE)
The Integrated Development Environment Package (IDE) contains the user interface elements, guarantees the consistent look and feel of your new software and provides basic functionalities required to handle controls:
- Configurable menus and toolbars (tool boxes such as the Edit Wizard that can be integrated as a completed component)
- Docking, hiding and moving of controls
- Integration of customer-specific controls and editors
- Output window
- Extendable options in the properties window
- The Engineering Step bar for easily task-oriented switching of the user interface (workspace)
- Progress display in the status bar
|
 |
 |
| |
|
 |
| |
|
 |
 |
 |
| |
The following picture shows some examples of completed components that you can integrate into your software: (1) the standard UI Framework provides menus, toolbars, etc. and also standard functions such as "Search/Replace". (2) the Edit Wizard allows the comfortable editing of graphical and textual code as well as variables. (3) Property window for clear management and definition of objects of any types. (4) Engineering Step bar that allows to dynamically adapt the user interface to your specific task. |
 |
| |
 |
 |
| |
Most of these components are also used in our new .NET-based IEC 61131 programing system MULTIPROG.NET. Further components such as powerful editors are also available (see below).
[MULTIPROG.NET ]
|
 |
| |
 |
 |
 |
| |
 |
ObjectStore
In order to fulfill the absolute demand for a consistent data management within a software platform created with AF application-wide, Automation Framework provides two different mechanisms: ObjectStore and mediator concept. |
 |
| |
The ObjectStore is the basis for the central data management. It builds the technical basis on which specific data models used, for instance, to process device data (e.g. sensor data, I/Os, network configurators, ...) and drive data have been developed. Data storage is done in XML format or in a binary format. Existing devices can be imported, new devices are created using the Catalog Editor and new device classes are specified via UML.
Basic functions of the ObjectStore:
- Full solution handling (opening, closing, saving projects, etc.).
- Data storage in XML format, binary format or SQL.
- Mechanisms to access data and objects.
- ObjectTree (ExpertTree): View on the project and catalog data. Objects can be created, deleted and edited. In addition, cut/copy/paste and drag & drop are possible. Unlimited nesting depth, subtrees are loaded on demand (reduced load time).
- Mediator components that link the ExpertTree with the ObjectStore.
- Integration of external files and folders as copy or reference into the AF data management.
- DeviceModel: Basic model for different automation objects (e.g. Device, MechatronicModule, Topology, etc.).
- Data reduction by Proxy concept.
- Integrated catalog handling for own catalogs and manufacturer catalogs (created with the Catalog Editor). This also includes release and update mechanisms.
|
 |
| |
[Details about data management in AF]
|
 |
| |
|
 |
 |
 |
| |
Editor packages: Independent editor components
The Component Framework can manage several editors in one Multi Document Interface (MDI) area.
The Editor Package by KW-Software provides customizable text editors and graphical editors which can be expanded or specialized according to application-specific needs via XML or C#. Of course, you can also integrate your own editors. |
 |
| |
 |
 |
| |
|
 |
| |
 |
 |
 |
| |
 |
Example: Graphical editor by KW-Software
- Editor for the graphical IEC languages FBD / LD / SFC.
- Separation of graphical data from the user interface
- Mediator component integrates the editor into the Automation Framework
- Undo/Redo
- Autorouting of connection lines
- Zoom functions
- Overview window
- Search and Replace
- Connectors instead of connection lines
- Clipboard
- Insertion of function blocks and variables via drag and drop
- IntelliSense
We use this editor in our new .NET-based IEC 61131 programing system MULTIPROG.NET. |
 |
| |
[Use of the graphical editor in MULTIPROG.NET]
|
 |
| |
|
 |
 |
 |
| |
 |
Example: Text editor by KW-Software
- Adaptation to further programming languages
- Customization via XML and Language Provider components
- Language Manager manages different programming languages
- Automatic compilation in the background
- Syntax highlighting
- Multiple Undo/Redo
- IntelliSense
- Auto Indent
- Auto Complete
- Info tooltips
- Folding
- Bookmarks
We use this editor in our new .NET-based IEC 61131 programing system MULTIPROG.NET. |
 |
| |
[Use of the text editor in MULTIPROG.NET]
|
 |
| |
|
 |
 |
 |
| |
|