[LEAPSECS] embedded data loggers?

[Rob Seaman]

Don’t know if this got through using my new email address.

Have been rummaging around looking at Arduino and/or Raspberry Pi hacks, but the former seems under-powered to run a full NTP instance and the latter is not real-time. Surely there must be an off-the-shelf dohickey that can return (via a unix-style service, for instance) a reliable ~millisecond timestamp corresponding to a trigger?

Or does everybody do rule-of-thumb or after-the-fact calibration of a stream of relative ticks? (The project is intended to get away from such an instance.) Just to be clear, this question is pretty much independent of timescale. Given an event in the real world (for simplicity corresponding to an electrical pulse or high-lo/lo-high transition with some perfectly reasonable amplitude and time constant), what are best practices for associating a well-tempered timestamp?

Rob
—

> Begin forwarded message:
> 
> From: Rob Seaman <seaman at lpl.arizona.edu>
> Subject: embedded data loggers?
> Date: January 10, 2016 at 3:03:49 PM MST
> To: Leap Second Discussion List <leapsecs at leapsecond.com>
> 
> Howdy,
> 
> Any suggestions for simple (read: inexpensive) components that can be embedded in an electronic device to grab timestamps corresponding to pulses or signal transitions? Pulses will occur every few seconds for hours in a row. The basic workflow is that something running under Linux commands an action that later asynchronously causes a pulse, the precise timing of that pulse (milliseconds would be sufficient) should be captured in some fashion that can easily be read, again by Linux, before the next pulse. I’m imagining a sample-and-hold feature, but am open to suggestion. The logger’s clock might be synchronized via NTP, but again, whatever gets the job done.
> 
> Thoughts?
> 
> Rob
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20160110/8910a223/attachment.html>