Earlier quoted context omitted.
But does that really require an absolute time reference?
In these cases mostly not, they require low jitter references and a good counter. An example that does - I work for IceCube, a big neutrino detector at the South Pole. The detector is essentially a time of flight system that detects emitted light as it propagates through the ice when a neutrino interaction happens. We need good time distribution in the system so we can marry up hits from the 5000 odd sensors in the i…
Open-sourcing a more precise time appliance
151–160 of 188 posts
Re: Open-sourcing a more precise time appliance
#152I don't see ESP8266 mentioned here: Overview: https://hackaday.com/2021/07/25/portable-gps-time-server-pow... Developer story: https://www.linkedin.com/pulse/iot-maker-tale-stratum-1-time... Repo: https://github.com/Montecri/GPSTimeServer A simpler version from the comments: https://enginemonitor.blogspot.com/2020/09/gps-module.html?m...
Why bother getting a nanosecond-level accurate time signal if you're going to feed it to an ESP8266 to distribute over Wi-Fi (or, in other words, reducing your accuracy to ~10 milliseconds or so)?
Re: Open-sourcing a more precise time appliance
#153Earlier quoted context omitted.
I believe they usually get it from the network.
That was my impression as well but now I’m puzzled about why. Since most smartphones have GPS builtin why not get time from GPS?
Re: Open-sourcing a more precise time appliance
#154Of course they come out with this now, after I've got a few antennas up on the roof, half a dozen GPS-disciplined OCXOs providing 10 MHz and PPS signals throughout the house, which are being fed into SolarFlare PTP NICs, and sync'd throughout the network using PTP.
Apparently my workstations' offsets (RMS) are currently 17 and 21 nanoseconds, though, so I suppose there's still room for improvement.
Re: Open-sourcing a more precise time appliance
#155I cannot find any source files for the FPGA code in the repository (no .v .vhd .vhdl files and I can't see anything by looking around manually). The FPGA directory [1] contains some binaries and some documents relating to commercial code from a Swiss firm [2]. I've seen plenty of projects described as open source when the firmware is open source and the hardware is closed but this is the first time I've seen one wher…
It's a particular module for the Xilinx Artix 7 XC7A100T, made by a Shanghai-based integrator. As an individual user, you could buy these on Aliexpress, from eBay resellers, or from Amazon resellers. Facebook presumably has an arrangement with the contract manufacturer that's not going to be possible for an individual developer ordering ones and twos to replicate. However, to modify the HDL, you'd need a $3,000 licen…
Re: Open-sourcing a more precise time appliance
#156I cannot find any source files for the FPGA code in the repository (no .v .vhd .vhdl files and I can't see anything by looking around manually). The FPGA directory [1] contains some binaries and some documents relating to commercial code from a Swiss firm [2]. I've seen plenty of projects described as open source when the firmware is open source and the hardware is closed but this is the first time I've seen one wher…
It's a particular module for the Xilinx Artix 7 XC7A100T, made by a Shanghai-based integrator. As an individual user, you could buy these on Aliexpress, from eBay resellers, or from Amazon resellers. Facebook presumably has an arrangement with the contract manufacturer that's not going to be possible for an individual developer ordering ones and twos to replicate. However, to modify the HDL, you'd need a $3,000 licen…
I think the XC7A100T is supported by the free (and limited) edition of Vivado [1]. Of course, the confusion about what you can and can't do with the HDL is in itself a barrier to open source and hobby work. This is true even when the work is theoretically possible and everyone has the best of intentions.
[1] https://www.xilinx.com/products/design-tools/vivado/vivado-m...
Re: Open-sourcing a more precise time appliance
#157Earlier quoted context omitted.
Curious, why did telephony require such accurate clocks?
It's not about accuracy (nobody really cares if the whole network is running fast or slow compared to some other clock) so much as synchrony (the whole network needs to be running from the same clock). Asynchronous networks can't guarantee latency or jitter performance, and they require buffers. Synchronous networks (remember, this is voice-grade stuff) can deliver bits out at the same rate as bits in, anywhere in th…
Re: Open-sourcing a more precise time appliance
#158Earlier quoted context omitted.
Valve did something similar for the Vive tracker dev kit. There was a time before the standalone tracker was available https://www.vive.com/us/accessory/vive-tracker/ where if you wanted a tracker that wasn't a full controller you had to build it yourself. This involved a paid workshop in Seattle to get access to the dev kit and learn their tooling. Hardware was open source, but firmware was closed. If you wanted fir…
The Valve situation sounds like they attempted to open source after the fact, which doesn’t work with large hardware projects. The only way to really open source a hardware project of this magnitude is to set open source as a constraint from the start. If you don’t, you inevitably end up with someone licensing some code somewhere from a vendor that can’t be open sourced. It gets integrated deeply enough that the proj…
Re: Open-sourcing a more precise time appliance
#159Earlier quoted context omitted.
To improve the performance of their distributed systems by imposing stronger assumptions than full asynchronicity on their environment, I expect. (See also Google’s Spanner.)
Of course we go inspired by the Google Spanner project and what they have published over a decade ago. Hats off to the Google Spanner team
Re: Open-sourcing a more precise time appliance
#160Growing up in Boulder, THE atomic clock (NIST) was touted as a modern marvel (circa early 90’s childhood), it’s incredible to think that similar performance is now available on a pci-e card! Any relation to DARPA’s “making progress” announcement in August 2018 [1]?