raspberry pi 3 b clock problems using .tv_usec

Question

code works fine when .tv_usec is replaced with .tv_sec

need more accuracy seconds to at lest to decimal points

wording if this my be an issue with the pis clock

code eventually to be used to calculate bpm but currently used to calculate time between clicks

gboolean tapTemp(GtkButton *button, gpointer user_data)
{
//errorMsg = bmp;

    if(tapdown)
    {

            tapdown = false;

            clock_gettime(CLOCK_REALTIME, &beetTime);

            time_difference = beetTime.tv_nsec;// - start_time;
            bpm = time_difference -  start_time; //time_difference;



            errorMsg = bpm;
    }
    else
    {
            tapdown = true;
            clock_gettime(CLOCK_REALTIME, &beetTime);
            start_time = beetTime.tv_nsec;
            errorMsg2 = start_time;
    }

 }

Are you sure that tv_usec exists? I can't find it's definition here: https://linux.die.net/man/3/clock_gettime. Try using tv_nsec instead. — BKovac, Mar 14 '17 at 17:19

score 0 · Accepted Answer · answered Mar 14 '17 at 18:48

0

tv_nsec will wrap back to zero every second - to make a continually incrementing time combine with tv_sec, e.g. thistime = beetTime.tv_secs+0.001*(beetTime.tv_nsec/1000000) to get the nearest millisecond.

answered Mar 14 '17 at 18:48

DisappointedByUnaccountableMod

6,656
4
18
22

raspberry pi 3 b clock problems using .tv_usec

1 Answers1