9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] "gpio device" for Plan 9
Date: Tue, 31 Dec 2013 17:03:22 -0500	[thread overview]
Message-ID: <34994d01ee44c5a5102bcea63e1e7e46@mikro> (raw)
In-Reply-To: <CANZw+5f32zEzoH5oiK_XF25aU_fcTFUZ8yN3kS0BwO=aWodGMQ@mail.gmail.com>

> Of things interrelated, I wish to sample a 10kHz square wave into a GPIO,
> which I am certain the RPi will do, see my earlier post with link to RPi
> forums. This will be a constant signal (an output of a GPSDO, with
> potentially a rubidium oscillator backup). So while the 10kHz is constant,
> the users input is not, and I wish to correlate in time the users input to
> the rising edge of the 10kHz signal, as it is then to be sent over a
> network with the time data of the event.
[...]
>
> I could be wildly off here Erik in my way of thinking, but my motivation is
> to extend the syncfs module to correlate precisely in time. The example
> system used by the Indiana University had no synchronisation across the
> network - presumably the only synchronised filesystem was the local
> filesystem on the cart robot? I will also be writing some kind of memory
> bounding for the ramfs. So, the events themselves are asynchronous and
> non-deterministic, however the clock source against which the events are
> placed in time is deterministic, and allows for easy reference and auditing.
>
> Perhaps there is a better way of doing this, I am not sure. Remember, I am
> an outsider to Plan 9 ways of thinking, although I am mostly unspoiled by
> Linux ways of thinking. To be precise, my ways of thinking are MSDOS, if
> that is at all possible in this day and age. I accept any and all better
> suggestions.

it seems that the system timer is already 1mhz.  but i suppose the issue is
that there is no external reference.  do you think you could get .1 ppm
time resolution with ntp between raspberry pis?  if not, i don't think i know
enough about your setup to say much of use other than to note frequency
is not directly related to precision.  if local timing can is stable to .1ppm for
a longish period of time, then a low-frequency strobe of high precision and
known timing could be enough.  the bbc does this with the tone at the top
of the hr.

- erik



  reply	other threads:[~2013-12-31 22:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29 22:04 Krystian Lewandowski
2013-12-29 22:34 ` erik quanstrom
2013-12-30  7:32 ` Skip Tavakkolian
2013-12-30 22:38   ` Shane Morris
     [not found] ` <35A33F66-EF03-4659-ABA1-F25082DBFE41@gmail.com>
2013-12-31 17:46   ` Krystian Lewandowski
2013-12-31 19:18     ` erik quanstrom
2013-12-31 19:37       ` Shane Morris
2013-12-31 19:48         ` Skip Tavakkolian
2013-12-31 19:50         ` erik quanstrom
2013-12-31 20:45           ` Shane Morris
2013-12-31 22:03             ` erik quanstrom [this message]
2013-12-31 22:17               ` Shane Morris
2013-12-31 22:52                 ` erik quanstrom
2013-12-31 22:57           ` Krystian Lewandowski
2013-12-31 23:16             ` Shane Morris
2013-12-31 23:35               ` Shane Morris
2014-01-01  0:04               ` Krystian Lewandowski
2014-01-01  0:12                 ` Shane Morris
2014-01-01  1:12     ` Matthew Veety
2014-01-01 11:38     ` Richard Miller
2014-01-01 22:16     ` erik quanstrom
2014-02-28 23:30       ` Krystian Lewandowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=34994d01ee44c5a5102bcea63e1e7e46@mikro \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).