Re:Chart – Completely Hackable Amateur Radio Telescope
by civilitty on Tuesday September 12, 2023 @11:37AM
(#37482883)
Theoretically yes but using GPS time of flight to synchronize sensor triggers to within tens of picoseconds is so far outside of "amateur" that you might as well incorporate and start replying to DoD RFPs.
When your math starts requiring relativistic physics, it's a lot easier and cheaper to just run some fiber.
Re:Chart – Completely Hackable Amateur Radio Telescope
by ooterness on Tuesday September 12, 2023 @11:57AM
(#37483230)
There's simpler options if all your equipment is in the same building, but yes, GPS-disciplined oscillators are a really great way to sync up clocks anywhere in the world to within a few nanoseconds. That said, it doesn't really help here because a) nanoseconds not picoseconds and b) the RTL-SDR doesn't have anywhere to plug it in.
Re:Chart – Completely Hackable Amateur Radio Telescope
by toomuchtodo on Tuesday September 12, 2023 @12:07PM
(#37483396)
Please forgive the silly question, but can the RTL-SDR receive the GPS signals software defined and process for timing?
Re:Chart – Completely Hackable Amateur Radio Telescope
by kawfey on Tuesday September 12, 2023 @12:29PM
(#37483735)
It is possible - https://www.rtl-sdr.com/rtl-sdr-tutorial-gps-decoding-plotti...
Re:Chart – Completely Hackable Amateur Radio Telescope
by civilitty on Tuesday September 12, 2023 @12:24PM
(#37483663)
No, it's not enough to know when samples from different SDRs were taken, they must all be taken within a very small interval (tens of picoseconds in OP's example). What the SDRs really need is an electrical signal called a "trigger" that tells them to read their sensors at that exact moment which is what GP meant by plugging them in. You can use a second GPS enable device to generate that trigger but synchronizing those triggers using time of flight is very hard.
Re:Chart – Completely Hackable Amateur Radio Telescope
by touisteur on Tuesday September 12, 2023 @05:47PM
(#37488960)
Maybe you can bruteforce time correlation by shifting every source slightly, trying a yuge number of shift combinations and seeing which combination gives the 'best' (most correlated) output on a known signal? I've done that for many out-of-sync systems, and since I've started using GPUs in the two Os I've become obsessed with brute force methods :-)
https://www.gps.gov/applications/timing/
https://ilrs.gsfc.nasa.gov/docs/timing/gpsrole.pdf