Technical extreme quibble: In order to get approximately 1 kHz clocks a timer, not atypically running off a US TV receiver color subcarrier crystal, is divided by 3580. This obviously gives a frequenc

#future

I've run across a reference of an ntp server that maintains time by fiddling with the counter settings. If you have a 3.57954545454 MHz timer oscillator (5e6/88*63) then it fiddles the time keeping di

#future

As long as the temperature is fairly stable a PC can do remarkably with a normal NTP installation. The Linux PC used as a router here maintains our ntp install and maintains time within +/- 30 ms acro

#future

Modulo required accuracy this may be good or bad. Cogitate a little while on the effects of multipath on GPS accuracy, especially when you only get the signal via a bounce path. (If you are interested

#future

Well, for most uses add about 3 or 4 ms to the time mark data read and average out a 7 ms peak to peak jitter and it should be modestly accurate maybe down to usual ntp accuracy. {^_^}

#future

Dunno - read the data on the site. That's all I know. Although I bought one for "old times sake" given that I know what the Phase 2B satellite looks like close up and its Delta launch pad (thanks to H

#future

And how much time does that read operation take? And is the time mark at the start of the first byte or at the end of the last byte. And when does the program performing the read get around to perform

#future

The performance counter has been available for a very long time. GetSystemTimePreciseAsFileTime() is an added function that means you do not have to invent your own. Remember that this only reads the

#future

time_t timeGetTime(); That has millisecond resolution - if running with mm timer set to 1 ms. Then there is the precision (100ns) timer with motherboard dependent actual resolution. I use timeGetTime(

#future

Then there is the brute force attempt to open each com port from 0 to 100. It's fugly. And it's historically not consistent from motherboard to motherboard and program to program. As I remember it the

I presume you mean +/- 1 ms. Your phrasing was a touch ambiguous. And that is only with the multimedia tick size setting to 1ms. (By now setting to 0.1 ms should be allowed but I suppose ms does not f

#future

Remember there are at least three or four totally unrelated different means of enumerating COM ports. That makes "correctly installed" a bit if a tough call. {o.o}

Oddly enough you might get shorter latency with the 96ksps. If the audio buffer size is the same for the two data rates it will fill up quicker at 96ksps. That is the ONLY reason I can see to use 96 k

This one looks intriguing, It has Windows driver. It has PPS - sort of, via USB. Waterproof GPS Receiver for Laptop, USB Interface, Raspberry Pi, 27 db Gain https://www.amazon.com/Waterproof-Receiver-

#future

You can do that using the PC version of Symmetricom's ntp client. If not that there is a full up ntp server/client for NTP out there on the web. One or both of those options should include the standar

#future

Brought to you by the department of redundancy department, division of needless repetition division. {o.o{

Just make sure the top checkmark on each side in the setup dialog, "use Ports class" is ticked. {^_-}

I understand that even with slippers hitting the family jewels is not a pleasant experience. {o.o}

0 Watts. At least it's not something I'd use at all. The sequencing is all wrong. Switch then apply power not the other way around. {o.o}

Really, once was enough. {+_+}