7 Teleservice Application Framework
User Manual 207/374
7.3.6.2.8 ylogd_set_save_condition
Function Description
sint32 ylogd_set_save_condition (const T_DBUS_Util *const opt_DBusInstance, const charn *
const opcn_LogJobName, const charn * const opcn_DatapoolName, const charn * const
opcn_ListName, const charn * const opcn_VariableName, const charn * const opcn_Logic,
const uint32 ou32_Hysteresis, const uint32 ou32_Threshold, const charn * const
opcn_Concatenation)
This function adds a new save condition to the log job opcn_LogJobName:
if (VARIABLE ('<='or '>= or '==' or '!=') (os32_Threshold +/- os32_Hysteresis))
then
condition is true, value will be logged.
When a save condition is already defined the actual save condition will always be concatenated with the
previous save conditions result. The Variable which shall be used for the condition has to be set by
opcn_DatapoolName, opcn_ListName and opcn_VariableName
The testing logic is defined by: opcn_Logic which can be '!=', '==', '<=', '>='
The variable is checked against the following parameters: os32_Threshold +/- os32_Hysteresis
If there are more than one condition set, then each condition result will be logically linked with his previous
result by opcn_Concatenation ('AND', 'OR' and 'EXOR')).
Information Flow
Input Information
holds all D-Bus information
maximum
MAX_DL_NAME_LENGTH
pointer to the log job name
maximum
MAX_DP_NAME_LENGTH
pointer to the data pool name
maximum
MAX_DP_NAME_LENGTH
pointer to the variable list name
maximum
MAX_DP_NAME_LENGTH
pointer to the variable name
maximum
MAX_DL_LOGIC_LENGTH
pointer to logical operator like '<=', '>=', '!=' and
'=='
pointer to the hysteresis of the variable we
expect to log
For an illustration of the logging sequence see How the logger mechanism works (see "Introduction"
on page 189).