SIMATIC WinAC ODK

Overview

WinAC ODK V4.2 supports the development of custom-designed applications for WinAC RTX with a high-level language development tool such as Microsoft Visual Studio. WinAC RTX provides 3 different interfaces for this:

• The Custom Code Extension (CCX) interface allows the direct start-up of high-level language applications or functions which are available in the form of DLLs for Windows or real-time DLLs for IntervalZero RTX, the real-time kernel used by WinAC RTX. Implementation as a DLL gives the developer complete access to the operating system APIs, software interfaces of other programs, or even resources of the PC (drivers, HW). These DLLs are developed with the aid of the ODK.
• The Shared Memory Extension (SMX) interface allows the fast exchange of data between the PLC program of the WinAC RTX and a user application. The Shared Memory can be addressed from the PLC in the I/O area and can be used, for example, in the same manner as a DP-DP coupler with a 4 KB I/O area.
• The Controller Management Interface (CMI) provides all of the functions of the WinAC panel for the customer application. This allows the WinAC RTX to be operated completely via a customer application such as a visualization program.
  

Creation of WinAC ODK applications

WinAC ODK applications are created using Microsoft Visual Studio. Depending on the interface runtime environment, it is possible to use different programming languages:

• CCX and SMX applications under IntervalZero RTX: Visual C++
• CCX, SMX and CMI applications under Windows: Visual C++, C#, Visual Basic

If a CCX or SMX application is supposed to work with WinAC RTX in real-time, an IntervalZero SDK (from IntervalZero Inc.) that matches the version of the real-time kernel used by WinAC RTX is required.

For ease of understanding and a quick start in an ODK application, the creation of CCX and SMX applications is supported by a wizard. Some programming examples are also included in the delivery kit.

Custom Code Extension Interface (CCX)

Applications that use the CCX interface can run both in Windows and in the IntervalZero RTX context, which means that, in principle, there are no restrictions with regard to the language elements used when programming this application.

CCX applications are executed as DLLs under Windows or real-time DLLs under Ardence RTX.

The application programmer is supported by a wizard when creating the following application types and functions:

• Synchronous start of the ODK application:
  The code is executed as part of the PLC code.
• Asynchronous start:
  The code is started in parallel to the PLC and is executed in the background.
• Continuous process:
  The ODK application runs parallel to the PLC and alerts the PLC program by calling up an alarm OB

Special system function blocks are available at the PLC end for starting the CCX application and starting its functions.

Shared Memory Extension Interface (SMX)

WinAC RTX provides a Shared Memory area which can be accessed as required by both the PLC application program and the SMX application. This type of coupling allows for very efficient exchange of data and a far-reaching uncoupling of the PLC variant from the SMX application which is also accessing data.

From the viewpoint of WinAC RTX, the Shared Memory is located in the I/O address area with 4 KB each the input and output. Access is possible using load/transfer commands. Access functions are available at the SMX application end.

Just as for the CCX interface, a wizard supports the creation of SMX applications.

Some typical applications for the SMX interface are:

• Data archiving
• Fast data coupling to software for optimizing production
• Simple, fast data interface to operating software with Visual Basic or C#
  

Controller Management Interface (CMI)

The CMI allows the WinAC CPU panel functionality to be integrated into a PC application. The following panel functions can be carried out by the PC application (examples):

• Starting and shutting down the controller.
• Operating the (RUN/STOP) key-operated switch.
• Status LED display.
• Loading user programs

This allows for flexible integration of WinAC into the overall application:

• Starting and stopping the controller in relation to other applications, e.g. defining the start sequence when starting up the PC.
• Automatic reload of updated PLC user programs ("machine update" by OEM).
  

Distribution of the WinAC ODK application

WinAC ODK is only needed for the development of applications (development license). No additional licenses are required by WinAC for applications created using ODK (runtime licenses).

At the WinAC Software PLC or Slot PLC end, such an application is integrated with the usual SIMATIC PLC programming languages.

• The PLC programmer can also use these applications without having higher-level programming languages expertise. For the PLC programmer, the ODK application looks like a function of the PLC.
• To make it easier for the PLC programmer to use the application, a STEP 7 library can be created, which provides simple FC/FB calls for handling the ODK application.