Network setup - Revision history

Jca: /* Home network connection */

2026-04-28T07:24:16Z

Home network connection

← Older revision		Revision as of 09:24, 28 April 2026
Line 50:		Line 50:

	sudo nmcli device wifi connect <SSID> password <password> ifname wlan0		sudo nmcli device wifi connect <SSID> password <password> ifname wlan0

	~~If you have no network contact, then use a local link (cable) or attach a screen and keyboard.~~

	==== As its own hotspot ====		==== As its own hotspot ====

Jca: /* As its own hotspot */

2026-04-28T07:23:40Z

As its own hotspot

← Older revision		Revision as of 09:23, 28 April 2026
Line 55:		Line 55:
	==== As its own hotspot ====		==== As its own hotspot ====

	See [[RICbot Hotspot \| hotspot]]		See [[RICbot Hotspot \| hotspot]].

	== Cable connection ==		== Cable connection ==

Jca: /* As its own hotspot */

2026-04-28T07:23:29Z

As its own hotspot

← Older revision		Revision as of 09:23, 28 April 2026
Line 55:		Line 55:
	==== As its own hotspot ====		==== As its own hotspot ====

	See [[~~Ricbot hotspot~~ \| hotspot]]		See [[RICbot Hotspot \| hotspot]]

	== Cable connection ==		== Cable connection ==

Jca: /* Network Manager */

2026-04-28T07:20:08Z

Network Manager

← Older revision		Revision as of 09:20, 28 April 2026
Line 18:		Line 18:
	nmcli connection		nmcli connection
	List available wifi access points		List available wifi access points
	nmcli ~~dev~~ wifi		nmcli device wifi list

	==== Connect to DTUdevice net ====		==== Connect to DTUdevice net ====

Jca: /* Home network connection */

2026-04-28T07:12:32Z

Home network connection

← Older revision		Revision as of 09:12, 28 April 2026
Line 52:		Line 52:

	If you have no network contact, then use a local link (cable) or attach a screen and keyboard.		If you have no network contact, then use a local link (cable) or attach a screen and keyboard.

			==== As its own hotspot ====

			See [[Ricbot hotspot \| hotspot]]

	== Cable connection ==		== Cable connection ==

Jca: /* NTP */

2026-04-20T12:34:22Z

NTP

← Older revision		Revision as of 14:34, 20 April 2026
Line 226:		Line 226:

	'''Depreciated'''. The Raspberry default time sync now works, also at DTU.		'''Depreciated'''. The Raspberry default time sync now works, also at DTU.
			=== PTP ===
	For PTP, see [[Ricbot PTP]].		For PTP, see [[Ricbot PTP]].

			=== NTP (depricated) ===
	Network Time Protocol is used to keep clocks in sync.		Network Time Protocol is used to keep clocks in sync.
	Raspberry Pi will start with the date and time of the last proper shutdown, and a few seconds after the network is up, it will sync the clock using NTP.		Raspberry Pi will start with the date and time of the last proper shutdown, and a few seconds after the network is up, it will sync the clock using NTP.

Jca: /* PTP */

2026-04-20T12:33:39Z

PTP

← Older revision		Revision as of 14:33, 20 April 2026
Line 222:		Line 222:

	The robot's name should be included in the list, but the network may take a while to detect it.		The robot's name should be included in the list, but the network may take a while to detect it.

	~~== PTP ==~~

	~~Precise Time Protocol (on Raspberry Pi 5)~~

	~~Assuming 2 Raspberry Pis are connected with an Ethernet cable, and both have an IP on eth0.~~

	~~==== Install ====~~

	~~Install on both master and slave:~~
	~~sudo apt install linuxptp~~

	~~Verify that there is support on 'eth0'.~~
	~~Should have hardware capabilities:~~

	~~$ ethtool -T eth0~~
	~~Time stamping parameters for eth0:~~
	~~Capabilities:~~
	~~hardware-transmit~~
	~~software-transmit~~
	~~hardware-receive~~
	~~software-receive~~
	~~software-system-clock~~
	~~hardware-raw-clock~~

	~~==== Test time master ====~~

	~~Start connection to eth0 hardware (as a process in the background)~~

	~~sudo phc2sys -s CLOCK_REALTIME -c eth0 -w &~~

	~~Start clock master service on eth0~~

	~~sudo ptp4l -i eth0 -m -2 -s~~

	~~It should be activated as a grand master soon.~~

	~~==== Test time client ====~~

	~~Run a PTP test slave (-s) with output to console (-m).~~

	~~sudo ptp4l -i eth0 -m -2 -s~~

	~~After a few minutes, this should yield a time offset on the order of 100 ns.~~

	~~Kill the phc2sys on the time server after the client test:~~
	~~sudo pkill phc2sys~~

	~~==== Install as a service on Master ====~~

	~~Most is copied from https://austinsnerdythings.com/2025/02/18/nanosecond-accurate-ptp-server-grandmaster-and-client-tutorial-for-raspberry-pi/.~~

	~~Create a service file for the connection to eth0:~~

	~~sudo nano /etc/systemd/system/phc2sys-grandmaster.service~~

	~~With:~~
	~~[Unit]~~
	~~Description=sync PHC with system clock (grandmaster)~~
	~~After=network-online.target~~
	~~Wants=network-online.target~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/sbin/phc2sys -s CLOCK_REALTIME -c eth0 -w~~
	~~Restart=always~~
	~~RestartSec=3~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~

	~~Create a service file for the ptp server:~~

	~~sudo nano /etc/systemd/system/ptp4l-grandmaster.service~~

	~~With:~~
	~~[Unit]~~
	~~Description=Precision Time Protocol (PTP) service (Grandmaster)~~
	~~After=network-online.target~~
	~~Wants=network-online.target~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/sbin/ptp4l -i eth0 -2~~
	~~Restart=always~~
	~~RestartSec=3~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~

	~~Enable and start these services~~

	~~sudo systemctl daemon-reload~~
	~~sudo systemctl enable phc2sys-grandmaster.service~~
	~~sudo systemctl enable ptp4l-grandmaster.service~~
	~~sudo systemctl start phc2sys-grandmaster.service~~
	~~sudo systemctl start ptp4l-grandmaster.service~~

	~~==== Install as a service on the client ====~~

	~~Make a new service file~~
	~~sudo nano /etc/systemd/system/ptp4l-client.service~~
	~~With:~~
	~~[Unit]~~
	~~Description=Precision Time Protocol (PTP) service (Client)~~
	~~After=network-online.target~~
	~~Wants=network-online.target~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/sbin/ptp4l -i eth0 -2 -m --summary_interval 3~~
	~~Restart=always~~
	~~RestartSec=3~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~

	~~Also, enable and start this service:~~

	~~sudo systemctl daemon-reload~~
	~~sudo systemctl enable ptp4l-client.service~~
	~~sudo systemctl start ptp4l-client.service~~

	~~Check the status of the client when all is in place~~
	~~sudo systemctl status ptp4l-client~~

	== NTP ==		== NTP ==

Jca: /* NTP */

2026-04-20T12:33:05Z

NTP

← Older revision		Revision as of 14:33, 20 April 2026
Line 351:		Line 351:

	'''Depreciated'''. The Raspberry default time sync now works, also at DTU.		'''Depreciated'''. The Raspberry default time sync now works, also at DTU.

			For PTP, see [[Ricbot PTP]].

	Network Time Protocol is used to keep clocks in sync.		Network Time Protocol is used to keep clocks in sync.

Jca: /* Install as a service on the client */

2026-04-19T11:57:19Z

Install as a service on the client

← Older revision		Revision as of 13:57, 19 April 2026
Line 338:		Line 338:
	[Install]		[Install]
	WantedBy=multi-user.target		WantedBy=multi-user.target

			Also, enable and start this service:

			sudo systemctl daemon-reload
			sudo systemctl enable ptp4l-client.service
			sudo systemctl start ptp4l-client.service

			Check the status of the client when all is in place
			sudo systemctl status ptp4l-client

	== NTP ==		== NTP ==

Jca: /* Install as a service on client */

2026-04-19T11:53:01Z

Install as a service on client

@@ Line 320: / Line 320: @@
   sudo systemctl start ptp4l-grandmaster.service
-==== Install as a service on client ====
+==== Install as a service on the client ====
 == NTP ==