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

Search:

Type: Posts; User: defragster

Search: Search took 0.03 seconds.

  1. Changed to the INT pin - RISING or FALLING the...

    Changed to the INT pin - RISING or FALLING the same ...

    Moved the T_4.1 from my desk - to a new hub and then a cable farther away. Wires are the 6" jumpers to pins on the T_4.1 and the DEMO board....
  2. I saw the INT pin setup - but went with CLKOUT as...

    I saw the INT pin setup - but went with CLKOUT as it was working at 32K on startup. It may be the CLKOUT isn't meant to be used this way. Will use that code line and move to INT pin.
  3. @mnissov: thanks, I just got busy here ... so not...

    @mnissov: thanks, I just got busy here ... so not reading prior notes well enough ... will look into what I can do here to see the RTC improve.
    Since the RV-3028 there is 'suboptimal' with no...
  4. Can't post whole sketch ... is it unsightly. I...

    Can't post whole sketch ... is it unsightly.
    I did make these adjustments to get my numbers down:


    ...
    if (0 == firstAdjust) {
    period = period - err * 0.75;
    }
    // period = period -...
  5. I'll look more tomorrow and see if there is a...

    I'll look more tomorrow and see if there is a more stable result using the other pin if that is an option.

    What RV-3028 board do you have? Their DEMO board is what I got. What i2c setup did you...
  6. @mnissov - FedEx delivered the RV-3028 Demo board...

    @mnissov - FedEx delivered the RV-3028 Demo board today { thank @BriComp }
    - out of the box the chip was running clock output pin at 32769. Keyed that into the code {1,000,000.0/32,769.0 us) and it...
  7. @mnissov - actually a good outcome ... from...

    @mnissov - actually a good outcome ... from Teensy and software POV :) Great to have it resolved. If you had posted a picture would before and after show where the noise came from?

    @manitou -...
  8. @mnissov - will go back to the necro thread...

    @mnissov - will go back to the necro thread linked above if I update the PPS/intervalTimer code. It won't be any good for microsPPS() unless the PPS is reliable - or deals with misses. With an RTC...
  9. @mnissov : Opened/soldered/wired the SparkFun GPS...

    @mnissov : Opened/soldered/wired the SparkFun GPS Logger Shield to a T_4.1. Got Space Data Fix in the window, saw UART strings and went to the indicated code and made what seem to be improvements. ...
  10. Interrupts are a mixed blessing with 'shared...

    Interrupts are a mixed blessing with 'shared data/purpose'. Same PRI means one can delay the other - diff PRI means one can interrupt the other :)

    Not questioning RTC accuracy/correctness - saw...
  11. Just in case it helps with time sync and...

    Just in case it helps with time sync and analysis.
    Code used above came from this 2 year old @PaulStoffregen post "Here's a little program to automatically adjust the IntervalTimer period.":...
  12. Just seeing this ... not seeing all code where...

    Just seeing this ... not seeing all code where 'micros_from_second' is accessed.
    Is this _isr on the same priority as the others? So they cannot interrupt each other and have the second change a...
Results 1 to 12 of 12