Status Messages - Siemens SIMATIC S7-1500 Produktinformation

Using ODK_DTL
Use the ODK data type "ODK_DTL" only as last parameter je InOut-Identifier in a function:
ODK_RESULT Sample1([IN] ODK_INT32 inInt, [IN] ODK_DTL inDTL
, [OUT] ODK_INT32 outInt, [OUT] ODK_DTL outDTL
, [INOUT] ODK_INT32 inoutInt, [INOUT] ODK_DTL inoutDTL);
Loading and calling an ODK application
To ensure the execution of an ODK application in the real-time environment, observe the following recommendations:
● The ODK application should be loaded in a StartupOB.
● Do not execute any ODK function during a loading process.
Executing ODK calls parallel in the real-time-environment
When using CPU version V1.7, you must not execute more than one ODK call at the same time.
Code generator does not output any messages
The code generator generates error messages for your ODK project.
If an array range is defined after the data type (for example: ODK_DOUBLE[10] myReal) instead of after the tag name, the
code generator can no longer process this file.

Status messages

Status 0x8099 for "Load" instruction (real-time-environment)
An ODK application is loaded by calling the "
returned through the output parameter after the load process.
The following table shows information on the value STATUS 0x8099 for the development of an ODK application for the real-
time environment:
DONE BUSY ERROR
0 0 1
Status 0x80C2" for "Load", "Execute" and "Unload" instruction (real-time environment)
The value STATUS 0x80C2 does not exist for the development of an ODK application for the real-time environment.
Status 0x80A4" for "Unload" instruction (real-time-environment)
The table below shows the information on the value STATUS 0x80A4 for the development of an ODK application for the
real-time environment:
DONE BUSY ERROR
0 0 1
Amendments to ODK 1500S V.10
A5E35341074-AB, 06/2015
<STEP7Prefix>
STATUS Meaning
0x8099 CPU version V1.7:
ODK application could not be loaded because the instruction was not called
from OB1 or OB100.
CPU version V1.8:
The ODK application could not be loaded because the instruction was not
called in an OB with lowest priority. Use a startup OB (such as OB100) or a
program cycle OB (for example, OB1).
STATUS Meaning
0x80A4 ODK application could not be unloaded. A communication error between the
CPU and ODK occurred during execution of the "OnUnload()" function.
_Load" instruction in the STEP 7 user program. Information is
13