Building a 4 Port Packet Controller - Revision history

Opadmin at 19:48, 25 October 2022

2022-10-25T19:48:17Z

← Older revision		Revision as of 15:48, 25 October 2022
Line 1:		Line 1:
	This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 B+ or similar hardware. Please note that due to a ~~hardware design limitation, the Raspberry Pi 4B+ and it's variants is~~ [https://github.com/raspberrypi/linux/issues/3962 unable to drive more than one soundcard at a time]. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with [https://dd-wrt.com/ DD-WRT firmware], bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.		This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 B+ or similar hardware. Please note that due to a [https://github.com/raspberrypi/linux/issues/3962 hardware design limitation], the Raspberry Pi 4B+ and it's variants is unable to drive more than one soundcard at a time. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with [https://dd-wrt.com/ DD-WRT firmware], bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.

	[[File:4PPC_Schematic.jpg\|320px]]		[[File:4PPC_Schematic.jpg\|320px]]

Opadmin at 19:41, 25 October 2022

2022-10-25T19:41:47Z

← Older revision		Revision as of 15:41, 25 October 2022
Line 1:		Line 1:
	This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 B+ or similar hardware. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with [https://dd-wrt.com/ DD-WRT firmware], bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.		This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 B+ or similar hardware. Please note that due to a hardware design limitation, the Raspberry Pi 4B+ and it's variants is [https://github.com/raspberrypi/linux/issues/3962 unable to drive more than one soundcard at a time]. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with [https://dd-wrt.com/ DD-WRT firmware], bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.

	[[File:4PPC_Schematic.jpg\|320px]]		[[File:4PPC_Schematic.jpg\|320px]]

Opadmin at 02:17, 24 June 2021

2021-06-24T02:17:24Z

← Older revision		Revision as of 22:17, 23 June 2021
Line 835:		Line 835:
	With all of this completed, the controller needs some configuration to become operational. At a minimum, /home/pi/bpq/bpq32.cfg must be edited to an appropriate callsign. It is suggested to update ALIASes to reflect the system location and/or role. Each of the ports should be updated to reflect appropriate information, a frequency and baudrate is suggested. The Telnet port allows remote access to the node, pay careful attention to the USER= lines which contain usernames and passwords for access.		With all of this completed, the controller needs some configuration to become operational. At a minimum, /home/pi/bpq/bpq32.cfg must be edited to an appropriate callsign. It is suggested to update ALIASes to reflect the system location and/or role. Each of the ports should be updated to reflect appropriate information, a frequency and baudrate is suggested. The Telnet port allows remote access to the node, pay careful attention to the USER= lines which contain usernames and passwords for access.

	More configuration information ~~will~~ be ~~included~~ in the [[4 Port Controller Administration Guide]]		More configuration information can be found in the [[4 Port Controller Administration Guide]]

Opadmin at 22:37, 23 June 2021

2021-06-23T22:37:25Z

← Older revision		Revision as of 18:37, 23 June 2021
Line 806:		Line 806:
	ro		ro

	In some cases, the "ro" command will report ~~that a file~~ is busy and a remount read only is not possible. Generally this is due to a service opening a file read write, a reboot will always correct this condition.		In some cases, the "ro" command will report "mount: /: mount point is busy." and a remount read only is not possible. Generally this is due to a service opening a file read write, a reboot will always correct this condition.

	---		---

Opadmin at 02:18, 23 June 2021

2021-06-23T02:18:22Z

← Older revision		Revision as of 22:18, 22 June 2021
Line 763:		Line 763:
	Once downloaded, consider pulling it into a preferred text editor and review each step. Afterwards, make the script executable and run it.		Once downloaded, consider pulling it into a preferred text editor and review each step. Afterwards, make the script executable and run it.

	chmod +x controller_setup.sh		chmod +x controller_setup.sh<br>
	sudo ./controller_setup.sh		sudo ./controller_setup.sh<br>

	The script will print a basic summary of each step, after each step completes, it will prompt to "Press any key" to continue. This is intended to allow capturing of error messages along the way or review of items changed. If something goes wrong, pressing CTRL+C will exit out of the script.		The script will print a basic summary of each step, after each step completes, it will prompt to "Press any key" to continue. This is intended to allow capturing of error messages along the way or review of items changed. If something goes wrong, pressing CTRL+C will exit out of the script.

Opadmin at 00:55, 23 June 2021

2021-06-23T00:55:42Z

← Older revision		Revision as of 20:55, 22 June 2021
Line 778:		Line 778:
	This script will		This script will

	1) Remove packages which do not permit running from a read only filesystem		1) Remove packages which do not permit running from a read only filesystem<br>
	2) Install busybox-syslogd and remove rsyslogd		2) Install busybox-syslogd and remove rsyslogd<br>
	3) Update cmdline.txt to boot read only		3) Update cmdline.txt to boot read only<br>
	4) Create symbolic links for specific paths and files, allowing them to run from tmpfs		4) Create symbolic links for specific paths and files, allowing them to run from tmpfs<br>
	5) Moves random-seed to tmpfs and update systemd unit to suite		5) Moves random-seed to tmpfs and update systemd unit to suite<br>
	6) Updates /etc/fstab to mount /boot and / read only		6) Updates /etc/fstab to mount /boot and / read only<br>
	7) Adds several tmpfs entries to /etc/fstab to allow read write to system RAM		7) Adds several tmpfs entries to /etc/fstab to allow read write to system RAM<br>
	8) Appends lines to /etc/rc.local to update /etc/resolv.conf and restore alsactl levels		8) Appends lines to /etc/rc.local to update /etc/resolv.conf and restore alsactl levels<br>

	This too should be reviewed prior to being run. Once logged into the Raspberry Pi 3 the script can be downloaded with		This too should be reviewed prior to being run. Once logged into the Raspberry Pi 3 the script can be downloaded with
Line 793:		Line 793:
	Once downloaded, consider pulling it into a preferred text editor and review each step. Afterwards, make the script executable and run it.		Once downloaded, consider pulling it into a preferred text editor and review each step. Afterwards, make the script executable and run it.

	chmod +x controller_setup.sh		chmod +x controller_setup.sh<br>
	sudo ./controller_setup.sh		sudo ./controller_setup.sh<br>

	The script will print a basic summary of each step, after each step completes, it will prompt to "Press any key" to continue. This is intended to allow capturing of error messages along the way or review of items changed. If something goes wrong, pressing CTRL+C will exit out of the script.		The script will print a basic summary of each step, after each step completes, it will prompt to "Press any key" to continue. This is intended to allow capturing of error messages along the way or review of items changed. If something goes wrong, pressing CTRL+C will exit out of the script.
Line 806:		Line 806:
	ro		ro

	In some cases, the "ro" command will report that a file is busy and a remount read only is not possible. Generally this is due to a service ~~restart~~, a reboot will always correct this condition.		In some cases, the "ro" command will report that a file is busy and a remount read only is not possible. Generally this is due to a service opening a file read write, a reboot will always correct this condition.

	---		---
Line 816:		Line 816:
	This script will		This script will

	1) Create a running folder of /home/pi/bpq		1) Create a running folder of /home/pi/bpq<br>
	2) Download the most recent version of pilinbpq from G8BPQ's website		2) Download the most recent version of pilinbpq from G8BPQ's website<br>
	3) Download the accompanying HTMLpages and unzip them		3) Download the accompanying HTMLpages and unzip them<br>
	4) Create a startup script that allows updating of pilinbpq on restart		4) Create a startup script that allows updating of pilinbpq on restart<br>
	5) Create, enable and start a systemd unit to handle the start, stop and restart of BPQ		5) Create, enable and start a systemd unit to handle the start, stop and restart of BPQ<br>

	This too should be reviewed prior to being run. Once logged into the Raspberry Pi 3 the script can be downloaded with		This too should be reviewed prior to being run. Once logged into the Raspberry Pi 3 the script can be downloaded with
Line 828:		Line 828:
	Once downloaded, consider pulling it into a preferred text editor and review each step. Afterwards, make the script executable and run it.		Once downloaded, consider pulling it into a preferred text editor and review each step. Afterwards, make the script executable and run it.

	chmod +x bpq32_setup.sh		chmod +x bpq32_setup.sh<br>
	sudo ./bpq32_setup.sh		sudo ./bpq32_setup.sh<br>

	----		----

			With all of this completed, the controller needs some configuration to become operational. At a minimum, /home/pi/bpq/bpq32.cfg must be edited to an appropriate callsign. It is suggested to update ALIASes to reflect the system location and/or role. Each of the ports should be updated to reflect appropriate information, a frequency and baudrate is suggested. The Telnet port allows remote access to the node, pay careful attention to the USER= lines which contain usernames and passwords for access.

			More configuration information will be included in the [[4 Port Controller Administration Guide]]

Opadmin at 00:48, 23 June 2021

2021-06-23T00:48:14Z

← Older revision		Revision as of 20:48, 22 June 2021
Line 5:		Line 5:
	'''Before starting this build'''		'''Before starting this build'''

	1) It is assumed there is a working Raspberry Pi 3 B+ with Raspian/Raspberry Pi OS 10 installed. This will probably work for Raspbian 9 and hopefully 11		1) It is assumed there is a working Raspberry Pi 3 B+ with Raspian/Raspberry Pi OS 10 installed. This will probably work for Raspbian 9 and hopefully 11<br>
	2) Remote access via SSH has been setup. Once this build is complete, the Raspberry Pi 3 B+ will run headless		2) Remote access via SSH has been setup. Once this build is complete, the Raspberry Pi 3 B+ will run headless<br>
	3) The onboard soundcard has been disabled. This is accomplished by editing /boot/config.txt and adding the line		3) The onboard soundcard has been disabled. This is accomplished by editing /boot/config.txt and adding the line<br>

	dtparam=audio=off		dtparam=audio=off
Line 13:		Line 13:
	Then reboot		Then reboot

	4) While the software setup is believed to be safe, please be sure that all important data is backed up in case something goes wrong		4) While the software setup is believed to be safe, please be sure that all important data is backed up in case something goes wrong.<br>
	5) All software setup will happen after the hardware build is complete.		5) All software setup will happen after the hardware build is complete.<br>

	----		----
Line 831:		Line 831:
	sudo ./bpq32_setup.sh		sudo ./bpq32_setup.sh

	---		----

Opadmin at 00:47, 23 June 2021

2021-06-23T00:47:25Z

Show changes

Opadmin at 22:26, 19 June 2021

2021-06-19T22:26:59Z

← Older revision		Revision as of 18:26, 19 June 2021
Line 1:		Line 1:
	This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 or similar hardware. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with DD-WRT firmware, bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.		This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 or similar hardware. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with [https://dd-wrt.com/ DD-WRT firmware], bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.

	[[File:4PPC_Schematic.jpg\|320px]]		[[File:4PPC_Schematic.jpg\|320px]]

Opadmin at 22:24, 19 June 2021

2021-06-19T22:24:34Z

← Older revision		Revision as of 18:24, 19 June 2021
Line 1:		Line 1:
	~~This documentation is still in progress. Please reference [https://ohiopacket.org/files/docs/Controller_Build.pdf Controller Build] for construction details.~~		This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 or similar hardware. This design allows any combination of software TNC ([https://github.com/wb2osz/direwolf Direwolf] or G8BPQ's [https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html QtSoundModem]) or G8BPQ's C port of [https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html ARDOP] modem for HF. This means the controller can have any combination of up to 4 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including [https://www.outpostpm.org/index.php Outpost PPM], [https://winlink.org/WinlinkExpress Winlink Express], [https://www.cantab.net/users/john.wiseman/Documents/index.html BPQ32], [https://ohiopacket.org/xrpi/ XRouter] and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with DD-WRT firmware, bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.

	~~----~~


	This page serves to be a guide for those wishing to build a 4 port packet controller on a Raspberry Pi 3 or similar hardware. This design allows any combination of software TNC (Direwolf or G8BPQ's QtSoundModem) or G8BPQ's C port of ARDOP modem for HF. This means the controller can have any combination of 300/1200/2400/4800/9600 baud packet and/or ARDOP modems running simultaneously. When coupled with G8BPQ's excellent packet switch, this allows for a low cost controller to house a multiport packet system or to act as a "network TNC" for other software, including Outpost PPM, Winlink Express, BPQ32 ~~on Windows~~ and others which support the AGWPE and/or KISS over TCP protocols. It uses the very popular Linksys WRT54G or BEFSR41 router as an enclosure as well as acts as a 3 or 4 port 10/100 megabit network switch to allow expansion of controllers and/or addition of other network devices. When coupled with a WRT54G, this can also include providing a wireless access point or if flashed with DD-WRT firmware, bridging to a wireless access point (Wireless client). This should cost under $100 USD to build, most of the part values are not critical.

	[[File:4PPC_Schematic.jpg\|320px]]		[[File:4PPC_Schematic.jpg\|320px]]
Line 721:		Line 716:
	Congratulations, the controller build is now ready for testing!		Congratulations, the controller build is now ready for testing!

	~~For~~ PTT ~~setup~~:<br>		If you have an existing Raspberry Pi 3 node running Direwolf, QtSoundModem, ARDOPC, you can configure each. The soundcard numbers may need to be found experimentally, the PTT GPIO numbers are as follows:<br>

	Port 1 uses GPIO 21<br>		Port 1 uses GPIO 21<br>
	Port 2 uses GPIO 20<br>		Port 2 uses GPIO 20<br>
Line 727:		Line 723:
	Port 4 uses GPIO 12<br>		Port 4 uses GPIO 12<br>

	~~Software setup~~ guide ~~is pending~~		If you are starting with a fresh system, a guide for building a 4 port node using Direwolf will be created in the near future.