3.1 KiB
3.1 KiB
Version 3:
To Figure Out
- Details on the NEO-F10T/breakout
- Battery
- GPIO Pinouts
- Voltages
- GPIO pin pitch
- Antenna connector type
- Best GPS Antenna+Cable for it
- PPS Settings
- UART Speed settings
- Any pulse out (32kHz maybe?)
- Pulsar Clock
- all daaat shit lmao
Hardware
-
Raspberry Pi 5 16GB
- Raspberry OS Lite
-
NVME hat for NVME boot (? IF NOT INTERFERE WITH GPIO SHIT)
- NVME SSD (? IF NOT INTERFERE WITH GPIO SHIT)
-
Custom Hat
-
-
RTC x2
- CR1220 x2 (Battery)
-
Gen 10 Timekeeping Specific GPS Module - NEO-F10T
-
- Make sure battery TYPE and APPLICATION is figured out
- May have to solder in holder or something
- Make sure GPIO pins are FUCKING 2.54mm AND 3.3v OR 5v
- use goldddd ones~
- Make sure antenna connector is gonna work
- GPS cable
- GPS antenna
- Make sure battery TYPE and APPLICATION is figured out
-
-
-
Operation Flow
Both RTCs loaded time over I2C, both inputting 32kHz signal via GPIO
Dual RTC time, GPS time, system time, GPS PPS, dual 32kHz signals, pulsar readings:
- tested off each other
- deltas per pulse (errors) (add to Grafana)
- averages per pulse (add to Grafana)
- stored in histograms, constantly updating (add to Grafana)
- dial in desired confidence interval over time (add to Grafana)
- divisor/multiplier for 32kHz pulses to make them ONE BEAT constantly updated (displayed in Grafana)
- one 32kHz oscillator (the most reliable) will be dubbed the "master universal beat pulse", made into pulse by divisor/multiplier based on previous calculations
- and will serve as source of truth for UBT web display
- sanity tested against network sources
-
Test both RTC times against GPS time
-
Test system time against GPS time
-
Test system time against network time
-
Sanity Checks
- Time reported vs time actual (net)
- Cable/system delay calculated vs delay measured
- Readability check
- Repeatability check
- Accuracy check
- Precision check
Maybe
-
Play with PPS (dial faster?)
-
Play with UART speed (dial faster?)