SIMATIC ODK 1500S V2.5 SP4 Programming and Operating Manual

Quick guide from the manual

The Open Development Kit (ODK) 1500S allows you to program custom functions and generate files that can be called directly by STEP 7. The general development workflow involves:

• Implement: Write your function in Visual Studio (for Windows/PLCSIM) or Eclipse (for Realtime).
• Create: Generate the DLL or SO file and the corresponding SCL file.
• Import: Import the SCL file into your STEP 7 project.
• Write: Integrate the ODK instructions into your user application.
• Load: Load the user program into the CPU and the DLL/SO file into the target system.

Product Overview

ODK 1500S supports two main environments:

• Windows Environment: Executes on a Windows PC, allowing access to Windows resources and external hardware/software components. Uses DLL files.
• Realtime Environment: Executes directly on the CPU, allowing synchronous function calls. Uses SO files.

Installation and Licensing

Before installation, ensure your PC meets the system requirements (Windows 8.1/10/11, 4GB RAM, Intel Core i5). The installation includes project templates for Visual Studio and Eclipse. A product-specific license key is required, managed via the Automation License Manager.

Developing CPU Function Libraries

The interface description is defined in the <project>.odk file. Key parameters include:

• Context: Defines if the library runs in 'user' or 'system' context (Windows) or 'realtime' context.
• STEP7Prefix: Defines the string preceding your functions in STEP 7.
• Trace: Enables/disables trace functionality for debugging.

Executing Functions

Functions are loaded and unloaded using specific instructions in the STEP 7 user program:

• <STEP7Prefix>_Load: Activates the loading of the CPU function library.
• <STEP7Prefix>_Unload: Unloads the library.
• <STEP7Prefix>SampleFunction: Executes the custom function.

Debugging and Troubleshooting

The ODK supports remote debugging via Visual Studio for Windows-based libraries. For Realtime environments, a Post Mortem analysis tool is available to evaluate system state after an exception. Use the GetTrace function block to read trace buffers for diagnostic purposes.