STW TC1, User Manual

Page: 202 / 374

7 Teleservice Application Framework
User Manual 202/374
Output Information
Return Value Description
C_NO_ERR Function executed without error, trigger time was activated successfully
C_COM D-Bus communication error
C_UNKNOWN_ERR NULL pointer error
C_RANGE opcn_LogJobName is out of range
C_NOACT Error occurred because the logger job name was invalid, trigger time interval is to
short, data logger configuration does not exist, DLC file is corrupt or logger already
exists
Example
// Global module
T_DBUS_Util mt_DBUS_Util;
sint32 s32_Retval;
s32_Retval = ylogd_set_trigger_time (&mt_DBUS_Util, "TC3_Logger", 500);
if (s32_Retval == C_NO_ERR)
{
// Go on
}
7.3.6.2.6 ylogd_set_buffered_logging
Function Description
sint32 ylogd_set_buffered_logging (const T_DBUS_Util * const opt_DBusInstance, const charn
* const opcn_LogJobName, const uint32 ou32_LoggingBufferSize)
The function sets the number of records to buffer. All logging data will be sent to this buffer.
If the log is triggered with ylogd_trigger_bufferd_log (see " ylogd_trigger_buffered_log " on page 227), the
buffered data will be placed in the log file, and then normal logging will continue.
When log job is activated, instead of creating a file, entries are stored in a ring buffer, replacing the oldest entry
when buffer is full. All normal log entry rules are in effect.
NOTE:
Log job activation will fail if the application is unable to allocate buffer memory.