User Documentation

Data recorder
System manual
2696790000/02/04.2020
86
*****************************************************************************
* interface functions
*/
ModuleInitFunc moduleInit = &ModuleInit;
ModuleStartFunc moduleStart = &ModuleStart;
ModuleStopFunc moduleStop = &ModuleStop;
ModuleExitFunc moduleExit = &ModuleExit;
HookClientFunc moduleCallback = &ModuleCallback;
/
*****************************************************************************
* macros
*/
#define ReturnIfNot(cond) \
if (!(cond)) { LogApiTrace(traceid, "### ReturnIfNot@line %d ###",
__LINE__);return;}
/
*****************************************************************************
* constants
*/
static const char scProfileName[] = "TestDataRecAppP1";
static const char scVarNameTemp[] = "temperature";
static const char scVarNamePres[] = "pressure";
/
*****************************************************************************
* static variables
*/
static int32_t sTemp;
static float sPres;
static DataRecApiProfileId sP1Id;
static DataRecApiVarId sTempId;
static DataRecApiVarId sPresId;
General instructions
Automatic recordings are to be configured in C-applications with the
DataRecApiSetRecContext function. The function defines a task context for
the recording based on the following information:
● Temporal distance of the individual recordings in μs
● Task priority of the individual recordings (from 1 = high to 31 = low)
● CPU task binding (starting from 0, or -1, for system-side selected stan-
dard binding)
With these settings a task is generated on the system-side, which is queued
under the usual application tasks in regards to intermittency and priority. To
fulfill certain requirements on the determinism of the recording, the interac-
tion of this task with the remaining application tasks is to be taken into ac-
count. For example, if the time stamps of the data detect unwanted “jitter,”
the selection of the above parameters is to be reconsidered. Furthermore,
the priority should not be too high, the distance should not be too short and
the quantity of data should not be too large in order to prevent a blocking of
real-time-critical tasks.