RE: Time required to send a mesh message from client to server

Mela — Wed, 02 Jun 2021 13:10:35 GMT

Thanks for the quick reply and for your help, much appreciated.

RE: Time required to send a mesh message from client to server

Hung Bui — Wed, 02 Jun 2021 12:20:40 GMT

Hi Mela,

If you have a look into the log.h you can find this:

/**
 * Prints a log message.
 * @param[in] source Log source
 * @param[in] level  Log level
 * @param[in] ...    Arguments passed on to the callback (similar to @c printf)
 */
#define __LOG(source, level, ...)                                       \
    if ((source & g_log_dbg_msk) && level <= g_log_dbg_lvl)             \
    {                                                                   \
        log_printf(level, __FILENAME__, __LINE__, log_timestamp_get(), __VA_ARGS__); \
    }

And this:

static inline uint32_t log_timestamp_get(void)
{
#if defined(HOST)
    #if defined(__linux__)
        struct timespec now;
        clock_gettime(CLOCK_REALTIME, &now);
        return (now.tv_sec * 1000000UL) + (now.tv_nsec / 1000UL);
    #else
        return 0;
    #endif
#else
    return NRF_RTC1->COUNTER;
#endif
}

So what you see in the log is the RTC's counter. And RTC1 by default is initialized with prescaler = 0. so the frequency is 32.768kHz.
So each second this counter counts 32768 unit.
Use this you can do calculation and can convert it to second and minute etc. But note that the counter is 24 bits, so it wraps around every 512 seconds. You would need to use some more variable to count if you want to count minutes and hours etc. It's up to you to modify the log_timestamp_get() function to add more info.