Raspberry Pi NTP Server - Revision history

Wikiadmin at 23:07, 20 October 2026

2026-10-20T23:07:23Z

← Older revision		Revision as of 01:07, 21 October 2026
Line 411:		Line 411:
	== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==		== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==
	{{#ev:youtube\|eqImO90rM4o}}		{{#ev:youtube\|eqImO90rM4o}}




	~~== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==~~

	This video guide walks through the step-by-step process of building a standalone Stratum-1 NTP server using a Raspberry Pi 1 Model B and a u-blox NEO-7M GPS receiver. Below is the technical breakdown and configuration timeline matching the embedded video guide.

	~~=== Video Timeline & Key Steps ===~~

	* '''00:00 - 01:30 \| Hardware Overview & Pinout'''
	~~:* External active GPS antenna (~28 dB gain) for stable satellite acquisition.~~
	~~:* u-blox NEO-7M module delivering both NMEA data and the pulse-per-second (PPS) hardware signal.~~
	~~:* Raspberry Pi 1 Model B (Chosen for its ultra-low power consumption, minimal electrical noise, and stable single-core environment).~~

	* '''01:30 - 03:10 \| OS Flashing via Raspberry Pi Imager'''
	~~:* Target OS: '''Raspberry Pi OS Lite (32-bit)'''.~~
	~~:* Customization Profile: Hostname set to <tt>ntp</tt>, Timezone set to <tt>Europe/Bucharest</tt>, SSH enabled, and user <tt>pi-ntp</tt> created.~~
	~~:* ''Note: The serial console is enabled by default during this process and will be manually disabled after boot.''~~

	* '''03:10 - 04:30 \| First Boot & System Update'''
	:* '''CRITICAL STEP:''' Keep the GPS module completely disconnected during the first boot. If wired to the UART pins prematurely, the active default serial login shell will interfere and may cause the Pi to fail to boot.
	~~:* Connect via Putty SSH and update the core system packaging.~~

	* '''04:30 - 06:17 \| UART & PPS Kernel Activation'''
	~~:# Disable the login shell by removing the console entry from: <tt>/boot/firmware/cmdline.txt</tt>~~
	~~:# Enable hardware UART in: <tt>/boot/firmware/config.txt</tt> using <tt>enable_uart=1</tt>~~
	~~:# Ensure the PPS driver loads automatically at boot by appending it to the system modules:~~
	~~:#: <tt>echo 'pps-gpio' >> /etc/modules</tt>~~
	~~:# Map the PPS overlay to the correct physical pin layout in <tt>config.txt</tt>:~~
	~~:#: <tt>dtoverlay=pps-gpio,gpiopin=18</tt>~~
	~~:# Safely power off the system to perform physical wiring.~~

	* '''06:17 - 07:48 \| Hardware Wiring Interface'''
	~~:* '''VCC''' (GPS Module) <--> '''Pin 2 or 4''' (Pi 5V Power)~~
	~~:* '''GND''' (GPS Module) <--> '''Pin 6 or 14''' (Pi Ground)~~
	~~:* '''TX''' (GPS Module) <--> '''Pin 10''' (Pi RXD0 / GPIO 15)~~
	~~:* '''RX''' (GPS Module) <--> '''Pin 8''' (Pi TXD0 / GPIO 14)~~
	~~:* '''PPS''' (GPS Module) <--> '''Pin 12''' (Pi GPIO 18)~~

	* '''07:48 - 10:51 \| Interface Diagnostics & gpsd Sync'''
	~~:* Verify raw NMEA sentence parsing over the serial line: <tt>cat /dev/serial0</tt>~~
	~~:* Install <tt>pps-tools</tt> and verify 1Hz pulse tracking: <tt>ppstest /dev/pps0</tt>~~
	~~:* Install and isolate <tt>gpsd</tt> configuration, forcing it to read both data streams instantly (<tt>-n</tt> flag) without waiting for external active clients.~~

	* '''10:51 - 15:28 \| Disciplining the System Clock with Chrony'''
	~~:* Isolate Chrony configuration from public pools to force total hardware clock reliance.~~
	~~:* Set the NMEA shared memory driver (<tt>refclock SHM 0</tt>) to provide the coarse absolute date context with a standard <tt>noselect</tt> monitor flag.~~
	~~:* Bind the precise PPS hardware device (<tt>refclock PPS /dev/pps0</tt>), locking it directly onto the GPS context, marked as <tt>prefer</tt>.~~
	~~:* Monitor system clock calibration live using: <tt>watch -n1 "chronyc sources; echo; chronyc tracking"</tt> until the server locks into Stratum-1 status.~~

	* '''15:28 - 17:03 \| LAN Server Provisioning'''
	~~:* Configure Chrony access control lists by exposing the local subnet: <tt>allow 192.168.1.0/24</tt>~~
	~~:* Confirm that the daemon successfully opened and bound UDP Port 123 using network sockets monitoring (<tt>netstat</tt>).~~

	* '''17:03 - 19:34 \| Network Client Integration (Ubuntu)'''
	~~:* Strip public time pools from client configuration files and point them directly onto the local Stratum-1 IP footprint (<tt>server 192.168.1.23 iburst</tt>).~~
	~~:* Use real-time terminal evaluation to track the node scaling smoothly down into a locked Stratum-2 time client.~~

	~~=== Production Benchmarks & Performance Conclusions ===~~
	* '''Jitter Stability:''' Maintained a steady performance envelope averaging between 0.4ms and 0.6ms, tracking tightly alongside expensive, hardened commercial timekeeping hardware (which averages around 0.2ms).
	* '''Throughput Capacity:''' The single-core legacy ARM architecture sustained an operational load profile of 15,000 to 18,000 active NTP requests per minute, approaching appliance-level performance limits at a fraction of the market cost.

Wikiadmin: /* Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) */

2026-10-20T23:06:35Z

Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS)

← Older revision		Revision as of 01:06, 21 October 2026
Line 411:		Line 411:
	== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==		== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==
	{{#ev:youtube\|eqImO90rM4o}}		{{#ev:youtube\|eqImO90rM4o}}




			== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==

			This video guide walks through the step-by-step process of building a standalone Stratum-1 NTP server using a Raspberry Pi 1 Model B and a u-blox NEO-7M GPS receiver. Below is the technical breakdown and configuration timeline matching the embedded video guide.

			=== Video Timeline & Key Steps ===

			* '''00:00 - 01:30 \| Hardware Overview & Pinout'''
			:* External active GPS antenna (~28 dB gain) for stable satellite acquisition.
			:* u-blox NEO-7M module delivering both NMEA data and the pulse-per-second (PPS) hardware signal.
			:* Raspberry Pi 1 Model B (Chosen for its ultra-low power consumption, minimal electrical noise, and stable single-core environment).

			* '''01:30 - 03:10 \| OS Flashing via Raspberry Pi Imager'''
			:* Target OS: '''Raspberry Pi OS Lite (32-bit)'''.
			:* Customization Profile: Hostname set to <tt>ntp</tt>, Timezone set to <tt>Europe/Bucharest</tt>, SSH enabled, and user <tt>pi-ntp</tt> created.
			:* ''Note: The serial console is enabled by default during this process and will be manually disabled after boot.''

			* '''03:10 - 04:30 \| First Boot & System Update'''
			:* '''CRITICAL STEP:''' Keep the GPS module completely disconnected during the first boot. If wired to the UART pins prematurely, the active default serial login shell will interfere and may cause the Pi to fail to boot.
			:* Connect via Putty SSH and update the core system packaging.

			* '''04:30 - 06:17 \| UART & PPS Kernel Activation'''
			:# Disable the login shell by removing the console entry from: <tt>/boot/firmware/cmdline.txt</tt>
			:# Enable hardware UART in: <tt>/boot/firmware/config.txt</tt> using <tt>enable_uart=1</tt>
			:# Ensure the PPS driver loads automatically at boot by appending it to the system modules:
			:#: <tt>echo 'pps-gpio' >> /etc/modules</tt>
			:# Map the PPS overlay to the correct physical pin layout in <tt>config.txt</tt>:
			:#: <tt>dtoverlay=pps-gpio,gpiopin=18</tt>
			:# Safely power off the system to perform physical wiring.

			* '''06:17 - 07:48 \| Hardware Wiring Interface'''
			:* '''VCC''' (GPS Module) <--> '''Pin 2 or 4''' (Pi 5V Power)
			:* '''GND''' (GPS Module) <--> '''Pin 6 or 14''' (Pi Ground)
			:* '''TX''' (GPS Module) <--> '''Pin 10''' (Pi RXD0 / GPIO 15)
			:* '''RX''' (GPS Module) <--> '''Pin 8''' (Pi TXD0 / GPIO 14)
			:* '''PPS''' (GPS Module) <--> '''Pin 12''' (Pi GPIO 18)

			* '''07:48 - 10:51 \| Interface Diagnostics & gpsd Sync'''
			:* Verify raw NMEA sentence parsing over the serial line: <tt>cat /dev/serial0</tt>
			:* Install <tt>pps-tools</tt> and verify 1Hz pulse tracking: <tt>ppstest /dev/pps0</tt>
			:* Install and isolate <tt>gpsd</tt> configuration, forcing it to read both data streams instantly (<tt>-n</tt> flag) without waiting for external active clients.

			* '''10:51 - 15:28 \| Disciplining the System Clock with Chrony'''
			:* Isolate Chrony configuration from public pools to force total hardware clock reliance.
			:* Set the NMEA shared memory driver (<tt>refclock SHM 0</tt>) to provide the coarse absolute date context with a standard <tt>noselect</tt> monitor flag.
			:* Bind the precise PPS hardware device (<tt>refclock PPS /dev/pps0</tt>), locking it directly onto the GPS context, marked as <tt>prefer</tt>.
			:* Monitor system clock calibration live using: <tt>watch -n1 "chronyc sources; echo; chronyc tracking"</tt> until the server locks into Stratum-1 status.

			* '''15:28 - 17:03 \| LAN Server Provisioning'''
			:* Configure Chrony access control lists by exposing the local subnet: <tt>allow 192.168.1.0/24</tt>
			:* Confirm that the daemon successfully opened and bound UDP Port 123 using network sockets monitoring (<tt>netstat</tt>).

			* '''17:03 - 19:34 \| Network Client Integration (Ubuntu)'''
			:* Strip public time pools from client configuration files and point them directly onto the local Stratum-1 IP footprint (<tt>server 192.168.1.23 iburst</tt>).
			:* Use real-time terminal evaluation to track the node scaling smoothly down into a locked Stratum-2 time client.

			=== Production Benchmarks & Performance Conclusions ===
			* '''Jitter Stability:''' Maintained a steady performance envelope averaging between 0.4ms and 0.6ms, tracking tightly alongside expensive, hardened commercial timekeeping hardware (which averages around 0.2ms).
			* '''Throughput Capacity:''' The single-core legacy ARM architecture sustained an operational load profile of 15,000 to 18,000 active NTP requests per minute, approaching appliance-level performance limits at a fraction of the market cost.

Wikiadmin: /* Test UART (NMEA) */

2026-10-20T23:01:28Z

Test UART (NMEA)

← Older revision		Revision as of 01:01, 21 October 2026
Line 78:		Line 78:
	</code>		</code>

	Acest rezultat confirma faptul ca Pi-ul primeste date ~~GPD~~ de la modul		Acest rezultat confirma faptul ca Pi-ul primeste date GPS de la modul
	Daca totul este configurat corect, ar trebui sa apara siruri NMEA. In cazul in care nu apare asemenator mai sus, verificati conexiunile RX/TX si setarile UART.		Daca totul este configurat corect, ar trebui sa apara siruri NMEA. In cazul in care nu apare asemenator mai sus, verificati conexiunile RX/TX si setarile UART.

Wikiadmin: /* Schema de conectare */

2026-10-20T23:00:22Z

Schema de conectare

← Older revision		Revision as of 01:00, 21 October 2026
Line 54:		Line 54:
	==== Schema de conectare ====		==== Schema de conectare ====

	[[File:GPIOtoGPS.jpg\|800px\|none\|~~Pagina Pringipala UrBackup~~]]		[[File:GPIOtoGPS.jpg\|800px\|none\|Schema conactare]]

	* Conectam pinul de 5V al Raspberry Pi la pinul de alimentare al modulului GPS.		* Conectam pinul de 5V al Raspberry Pi la pinul de alimentare al modulului GPS.

Wikiadmin at 21:16, 4 May 2026

2026-05-04T21:16:26Z

← Older revision		Revision as of 23:16, 4 May 2026
Line 1:		Line 1:
	~~{{#ev:youtube\|ANSb5mRzX_M}}~~

	== Configurarea Raspberry Pi ca server NTP folosint NEO-7M ==		== Configurarea Raspberry Pi ca server NTP folosint NEO-7M ==
	Un server NTP asigura sincronizarea corecta a orei pentru toate dispozitivele dintr-o retea, prevenind erori în loguri, autentificari sau servicii care depind de timp precis. Folosind un modul GPS cu PPS, un Raspberry Pi poate deveni o sursa Stratum‑1 foarte stabila și independenta de internet. Acest proiect prezinta configurarea unui astfel de server NTP simplu și fiabil pentru uz local.		Un server NTP asigura sincronizarea corecta a orei pentru toate dispozitivele dintr-o retea, prevenind erori în loguri, autentificari sau servicii care depind de timp precis. Folosind un modul GPS cu PPS, un Raspberry Pi poate deveni o sursa Stratum‑1 foarte stabila și independenta de internet. Acest proiect prezinta configurarea unui astfel de server NTP simplu și fiabil pentru uz local.
Line 410:		Line 408:
	Combinatia dintre Chrony si PPS bazat pe GNSS ofera o sursa de timp stabila si predictibila, potrivita pentru o gama larga de aplicatii.		Combinatia dintre Chrony si PPS bazat pe GNSS ofera o sursa de timp stabila si predictibila, potrivita pentru o gama larga de aplicatii.
	Cu imbunatatiri incrementale, aceasta platforma poate fi rafinata si mai mult si adaptata unor medii de sincronizare mai pretentioase.		Cu imbunatatiri incrementale, aceasta platforma poate fi rafinata si mai mult si adaptata unor medii de sincronizare mai pretentioase.

			== Building a GPS based Raspberry Pi NTP Server (NEO‑7M + PPS) ==
			{{#ev:youtube\|eqImO90rM4o}}

Wikiadmin: /* Configurarea Raspberry Pi ca server NTP folosint NEO-7M */

2026-05-04T21:09:01Z

Configurarea Raspberry Pi ca server NTP folosint NEO-7M

← Older revision		Revision as of 23:09, 4 May 2026
Line 1:		Line 1:
			{{#ev:youtube\|ANSb5mRzX_M}}

	== Configurarea Raspberry Pi ca server NTP folosint NEO-7M ==		== Configurarea Raspberry Pi ca server NTP folosint NEO-7M ==
	Un server NTP asigura sincronizarea corecta a orei pentru toate dispozitivele dintr-o retea, prevenind erori în loguri, autentificari sau servicii care depind de timp precis. Folosind un modul GPS cu PPS, un Raspberry Pi poate deveni o sursa Stratum‑1 foarte stabila și independenta de internet. Acest proiect prezinta configurarea unui astfel de server NTP simplu și fiabil pentru uz local.		Un server NTP asigura sincronizarea corecta a orei pentru toate dispozitivele dintr-o retea, prevenind erori în loguri, autentificari sau servicii care depind de timp precis. Folosind un modul GPS cu PPS, un Raspberry Pi poate deveni o sursa Stratum‑1 foarte stabila și independenta de internet. Acest proiect prezinta configurarea unui astfel de server NTP simplu și fiabil pentru uz local.

Wikiadmin: /* Testare gpsd */

2026-02-25T15:48:34Z

Testare gpsd

← Older revision		Revision as of 17:48, 25 February 2026
Line 158:		Line 158:
	mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqjmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj		mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqjmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
	</code>		</code>

			Din coloana situata in partea dreapta observam ca sistemul nostru se conecteaza la:
			* GP - GPS (Global Positioning System) este un sistem global de navigatie prin satelit dezvoltat de Statele Unite.
			* GA - Galileo este sistemul european de navigatie prin satelit (GNSS), dezvoltat de Uniunea Europeana.
			* SB - SBAS (Satellite-Based Augmentation System) este un sistem care imbunatateste precizia si fiabilitatea pozitionarii GNSS (GPS, Galileo etc.)
			Alte sisteme de GNSS care nu sunt prezente in conexiunea nostra ar pute fi:
			* GL - GLONASS este sistemul de navigatie prin satelit al Federatiei Ruse
			* BD - BeiDou este sistemul de navigatie prin satelit al Chinei

	=== Configurarea serverului NTP ===		=== Configurarea serverului NTP ===

Wikiadmin: /* Componente folosite */

2026-02-25T15:34:24Z

Componente folosite

← Older revision		Revision as of 17:34, 25 February 2026
Line 6:		Line 6:
	* Raspberry Pi 1 Model B - 180 RON (pret din 2012)		* Raspberry Pi 1 Model B - 180 RON (pret din 2012)
	* Modul GPS u-blox NEO-7M - 49,07 RON		* Modul GPS u-blox NEO-7M - 49,07 RON
	* Antena GPS ~~~28db~~ - 67 RON		* Antena GPS ~28 dB gain - 67 RON
	* Fire jumper female–female - 5,79 RON		* Fire jumper female–female - 5,79 RON
	* Card SD 16 GB - aprox 30 RON		* Card SD 16 GB - aprox 30 RON

Wikiadmin: /* Test UART (NMEA) */

2026-02-25T15:06:16Z

Test UART (NMEA)

← Older revision		Revision as of 17:06, 25 February 2026
Line 69:		Line 69:

	<code class="mw-code mw-highlight plainlinks" style="display:block"><!--		<code class="mw-code mw-highlight plainlinks" style="display:block"><!--
	--> cat /dev/serial0		--> <b># cat /dev/serial0</b>
	$GNRMC,140221.00,A,4423.43286,N,02605.77991,E,0.096,,250226,,,A,V*14		$GNRMC,140221.00,A,4423.43286,N,02605.77991,E,0.096,,250226,,,A,V*14
	$GNVTG,,T,,M,0.096,N,0.178,K,A*3C		$GNVTG,,T,,M,0.096,N,0.178,K,A*3C

Wikiadmin: /* Instalare unelte PPS si testare */

2026-02-25T15:06:02Z

Instalare unelte PPS si testare

← Older revision		Revision as of 17:06, 25 February 2026
Line 89:		Line 89:

	<code class="mw-code mw-highlight plainlinks" style="display:block"><!--		<code class="mw-code mw-highlight plainlinks" style="display:block"><!--
	--> <b>#ppstest /dev/pps0</b>		--> <b># ppstest /dev/pps0</b>
	trying PPS source "/dev/pps0"		trying PPS source "/dev/pps0"
	found PPS source "/dev/pps0"		found PPS source "/dev/pps0"