Radarcape:NTP - Revision history

Dl4mea at 17:15, 26 March 2025

2025-03-26T17:15:56Z

@@ Line 21: / Line 21: @@
 As it comes out of the box, Radarcape and Airsquitter can be used as Stratum 1 NTP source. Configure any client to use it as NTP server.
-==NTP client or server on Angstrom (deprecated)==
+===Local Time Synchronisation via NTP===
 In order to have correct time on Angstrom based Radarcapes, due to a hardware probelm in our cape board, a special kernel is required.
@@ Line 31: / Line 27: @@
 The Radarcape's hardware design will support true NTP using the GPS. Both, the Trimble serial data stream as well as the 1PPS, are available on the Beaglebone. However due to time constraints using those in order to create a Stratum 1 NTP server was not yet implemented.
-'''Important Note:''' Timestamping of the Mode-AC/Mode-S raw data frames is _not_ done using the system time which is described here. All received frames are directly time stamped in the FPGA without any interaction of the local CPU. However, the __date__ in Port 30003 messages is always the Linux system date. The __timestamp__ instead is a GPS timestamp when the config is set to GPS timestamps and system time when the Radarcape operates in legacy 12MHz timstamp mode.
+'''Important Note:''' Timestamping of the Mode-AC/Mode-S raw data frames is _not_ done using the system time which is described here. All received frames are directly time stamped in the FPGA without any interaction of the local CPU or operating system. However, the __date__ in Port 30003 messages is always the Linux system date. The __timestamp__ instead is a GPS timestamp when the config is set to GPS timestamps and system time when the Radarcape operates in legacy 12MHz timstamp mode.

Dl4mea: /* NTP client or server on Debian */

2025-03-26T17:14:09Z

NTP client or server on Debian

← Older revision		Revision as of 17:14, 26 March 2025
Line 6:		Line 6:
	\|}		\|}

	==NTP ~~client or server on Debian~~==		==NTP==

			===Basics===

			A Radarcape or Airsquitter in its regular operation comes with a built in GPS module, so nothing is easier than using that as a time source, too. Fallback options are NTP to given servers.

	===NTP client===		===NTP client===

	~~Debian uses systemd~~ NTP ~~client by default. To check the state you~~ can ~~type: systemctl status systemd~~-~~timesyncd~~.		The fallback NTP server for system time - but not MLAT timestamps - can be configured in Settings -> Network.


	===NTP stratum 1 server===		===NTP stratum 1 server===

	~~Instructions~~ and ~~files~~ to ~~set Radarcape~~ as a NTP ~~stratum 1~~ server ~~(PPS reference from GPS) is available at:~~		As it comes out of the box, Radarcape and Airsquitter can be used as Stratum 1 NTP source. Configure any client to use it as NTP server.

	~~https://github.com/Jetvision/radarcape-ntp-pps~~

	~~If you have before compiled and installed manually NTPD or Chrony it is recommended that you remove it before~~.

	==NTP client or server on Angstrom (deprecated)==		==NTP client or server on Angstrom (deprecated)==

Dl4mea: /* Links */

2024-11-08T20:42:34Z

Links

← Older revision		Revision as of 20:42, 8 November 2024
Line 66:		Line 66:

	Note: On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in journalctl.		Note: On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in journalctl.

	~~==Links==~~

	~~http://stackoverflow.com/questions/11219832/what-is-the-best-way-to-run-ntpdate-at-reboot-only-after-network-is-ready~~

imported>Nunojpg at 13:34, 5 August 2017

2017-08-05T13:34:26Z

← Older revision		Revision as of 13:34, 5 August 2017
Line 6:		Line 6:
	\|}		\|}

	==NTP ~~time synchronisation~~ on ~~Radarcapes with~~ Debian==		==NTP client or server on Debian==

	===NTP client===		===NTP client===
Line 20:		Line 20:
	If you have before compiled and installed manually NTPD or Chrony it is recommended that you remove it before.		If you have before compiled and installed manually NTPD or Chrony it is recommended that you remove it before.

	==Angstrom (deprecated)==		==NTP client or server on Angstrom (deprecated)==

	Configuring Angstrom as a NTP server is not recommend and not supported, as Debian provides much better compatibility and performance.		Configuring Angstrom as a NTP server is not recommend and not supported, as Debian provides much better compatibility and performance.

imported>Nunojpg at 13:26, 5 August 2017

2017-08-05T13:26:10Z

← Older revision		Revision as of 13:26, 5 August 2017
Line 6:		Line 6:
	\|}		\|}

	==NTP ~~Synchronisation~~ on Radarcapes with Debian==		==NTP time synchronisation on Radarcapes with Debian==

	===NTP ~~time as a~~ client===		===NTP client===

	NTP ~~as a~~ client ~~is standard for Debian~~. ~~There is nothing to do in special~~.		Debian uses systemd NTP client by default. To check the state you can type: systemctl status systemd-timesyncd.

	===NTP ~~as a~~ stratum 1 ~~device~~===		===NTP stratum 1 server===

	==NTP ~~Synchronisation on Radarcapes with Angstrom~~ (~~deprecated~~)==		Instructions and files to set Radarcape as a NTP stratum 1 server (PPS reference from GPS) is available at:

	~~As of state mid 2015, this~~ is deprecated. NTP ~~should be used with~~ Debian ~~only~~.		https://github.com/Jetvision/radarcape-ntp-pps

			If you have before compiled and installed manually NTPD or Chrony it is recommended that you remove it before.

			==Angstrom (deprecated)==

			Configuring Angstrom as a NTP server is not recommend and not supported, as Debian provides much better compatibility and performance.

	===Radarcape and Local Time Synchronisation via NTP===		===Radarcape and Local Time Synchronisation via NTP===

imported>Dl4mea: /* NTP Synchronisation on Radarcapes with Angstrom */

2015-08-16T10:33:39Z

NTP Synchronisation on Radarcapes with Angstrom

← Older revision		Revision as of 10:33, 16 August 2015
Line 14:		Line 14:
	===NTP as a stratum 1 device===		===NTP as a stratum 1 device===

	==NTP Synchronisation on Radarcapes with Angstrom==		==NTP Synchronisation on Radarcapes with Angstrom (deprecated)==

			As of state mid 2015, this is deprecated. NTP should be used with Debian only.

	===Radarcape and Local Time Synchronisation via NTP===		===Radarcape and Local Time Synchronisation via NTP===

			In order to have correct time on Angstrom based Radarcapes, due to a hardware probelm in our cape board, a special kernel is required.

	The Radarcape's hardware design will support true NTP using the GPS. Both, the Trimble serial data stream as well as the 1PPS, are available on the Beaglebone. However due to time constraints using those in order to create a Stratum 1 NTP server was not yet implemented.		The Radarcape's hardware design will support true NTP using the GPS. Both, the Trimble serial data stream as well as the 1PPS, are available on the Beaglebone. However due to time constraints using those in order to create a Stratum 1 NTP server was not yet implemented.

imported>Dl4mea: /* NTP time as a client */

2015-08-15T20:07:33Z

NTP time as a client

← Older revision		Revision as of 20:07, 15 August 2015
Line 9:		Line 9:

	===NTP time as a client===		===NTP time as a client===

			NTP as a client is standard for Debian. There is nothing to do in special.

	===NTP as a stratum 1 device===		===NTP as a stratum 1 device===

imported>Dl4mea at 19:41, 15 August 2015

2015-08-15T19:41:59Z

← Older revision		Revision as of 19:41, 15 August 2015
Line 6:		Line 6:
	\|}		\|}

	==Radarcape and Local Time Synchronisation via NTP==		==NTP Synchronisation on Radarcapes with Debian==

			===NTP time as a client===

			===NTP as a stratum 1 device===

			==NTP Synchronisation on Radarcapes with Angstrom==

			===Radarcape and Local Time Synchronisation via NTP===

	The Radarcape's hardware design will support true NTP using the GPS. Both, the Trimble serial data stream as well as the 1PPS, are available on the Beaglebone. However due to time constraints using those in order to create a Stratum 1 NTP server was not yet implemented.		The Radarcape's hardware design will support true NTP using the GPS. Both, the Trimble serial data stream as well as the 1PPS, are available on the Beaglebone. However due to time constraints using those in order to create a Stratum 1 NTP server was not yet implemented.
Line 46:		Line 54:

	Note: On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in journalctl.		Note: On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in journalctl.

	~~==Open Issues==~~

	* How to inquire more information about the NTP status

	==Links==		==Links==

	http://stackoverflow.com/questions/11219832/what-is-the-best-way-to-run-ntpdate-at-reboot-only-after-network-is-ready		http://stackoverflow.com/questions/11219832/what-is-the-best-way-to-run-ntpdate-at-reboot-only-after-network-is-ready

imported>Beastadmin at 19:24, 25 March 2015

2015-03-25T19:24:52Z

← Older revision		Revision as of 19:24, 25 March 2015
Line 3:		Line 3:
	{\|		{\|
	\|[[File:Expert.png\|For Experts]]		\|[[File:Expert.png\|For Experts]]
	\|''~~The tasks described in~~ this ~~manual require advanced skills in Unix/Linux.~~''		\|''Required Linux/Unix skills to execute this task: Advanced''
	\|}		\|}

Line 45:		Line 45:
	Nov 09 13:48:15 rc12 connmand[122]: ntp: time slew +85.321813 s		Nov 09 13:48:15 rc12 connmand[122]: ntp: time slew +85.321813 s

	~~===Problems===~~		Note: On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in journalctl.
	On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in ~~the~~ journalctl.
			==Open Issues==

	~~==To do==~~
	* How to inquire more information about the NTP status		* How to inquire more information about the NTP status

imported>Dl4mea: /* To do */

2013-11-23T11:27:58Z

To do

← Older revision		Revision as of 11:27, 23 November 2013
Line 44:		Line 44:
	Nov 09 13:49:41 rc12 connmand[122]: connmand[122]: ntp: time slew +85.321813 s		Nov 09 13:49:41 rc12 connmand[122]: connmand[122]: ntp: time slew +85.321813 s
	Nov 09 13:48:15 rc12 connmand[122]: ntp: time slew +85.321813 s		Nov 09 13:48:15 rc12 connmand[122]: ntp: time slew +85.321813 s

			===Problems===
			On a few devices I saw that after some days the time sync via NTP is suddenly lost. NTP update messages disappear in the journalctl.

	==To do==		==To do==
	* How to inquire more information about the NTP status		* How to inquire more information about the NTP status

			==Links==

			http://stackoverflow.com/questions/11219832/what-is-the-best-way-to-run-ntpdate-at-reboot-only-after-network-is-ready