Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: mlu

Search: Search took 0.00 seconds.

  1. Replies
    14
    Views
    7,284

    For measuring the time error, with zero...

    For measuring the time error, with zero compensation, you can use any intervall, like 10s
    or 100 to get some more resolution.

    For checking the precision after calibration you must either use an...
  2. Replies
    14
    Views
    7,284

    your measurement intervall in seconds should be a...

    your measurement intervall in seconds should be a multiple of the value of the compensation
    intervall, CIR+1, this will ensure that the compensations are aligned with your measurements.

    If I am...
  3. Replies
    14
    Views
    7,284

    Of course you are right micros() is correct. ...

    Of course you are right micros() is correct.

    Now if the GPS PPS and the RTC give the same number of MCU micros
    over 10 sec then RTC and GPS are synchronized and the error is 0.
    Your measurements...
  4. Replies
    14
    Views
    7,284

    For measuring the quotient between GPS PPS and...

    For measuring the quotient between GPS PPS and RTC seconds the MCU clock, miilis()
    should give you better than 0.5 ppm resolution, including digitisation errors and loop initialisation and such, ...
  5. Replies
    14
    Views
    7,284

    Perhaps its as simple as using ...

    Perhaps its as simple as using


    second(Teensy3Clock.get())

    to read the RTC second without any resync issues.
  6. Replies
    14
    Views
    7,284

    The syncronisation to the RTC is done every 300...

    The syncronisation to the RTC is done every 300 seconds as seen in the now() function (in Time.cpp).


    static uint32_t syncInterval = 300; // time sync will be attempted after this many seconds
    ...
Results 1 to 6 of 6