Differences

This shows you the differences between two versions of the page.

--- packet-bpq-node-building [2023/01/24 18:35] – m0lte
+++ packet-bpq-node-building [2023/01/25 11:59] – m0lte
@@ Line 5: / Line 5: @@
 So this page is an attempt to walk through what a node is and does, why you might want to build one (not everyone might), and how to do so.
-===== What and why =====
+==== What and why ====
 In a packet radio network, a node is a station which is often unattended, with one or more radios on different bands, generally forming a permanent part of the network, and generally offering some services to nearby stations which connect.
@@ Line 13: / Line 13: @@
 You might want to run a node if you want to contribute to extending the reach of a packet network, or if you are technically curious about packet network routing.
-In a traditional packet network, it's perfectly reasonable for many/most people not to want or need to set up a node. However, some OARC members are beginning to think about the design of more modern applications, utilising the underlying packet network, and to give the best experience it is likely that you would want to have an instance of that application running in the same location as the packet node. If we get to this point, then it's likely that more people will run node software than otherwise might be the case.
+In a traditional packet network, it's perfectly reasonable for many/most people not to want or need to set up a node. However, some OARC members are beginning to think about the design of more modern applications, utilising the underlying packet network, and to give the best experience it is likely that you would want to have an instance of that application running in the same location as the packet node. If we get to this point, then it's likely that more people will run node software than otherwise might be the case. So you might want to have a play for this reason.
-===== What a node isn't =====
+==== What a node isn't ====
 A node takes over your TNC - it isn't something you can just run in the background. If you turn your packet station into a node then everything you do will be done indirectly, via that node. Which works fine, you just need to be aware of it.
-A node isn't, as it stands, low-effort. There is a bit of a learning curve, and you'll need to be comfortable with getting your hands dirty. We believe there is room for improvement in this area.
+Building a node isn't, as it stands, low-effort. There is a bit of a learning curve, and you'll need to be comfortable with getting your hands dirty and troubleshooting. We believe there is room for improvement in this area.
+===== The build =====
+What you'll end up with by following this guide is a single port 1200 baud VHF BPQ node.
+While this guide targets a Raspberry Pi running Raspberry Pi OS, other platforms and Debian-based distros are likely to be similar.
+==== You will need ====
+  * A Raspberry Pi
+  * A [[packet-transceivers|suitable FM transceiver]]
+  * A KISS TNC with a Kantronics-style DB9 radio socket, e.g. NinoTNC
+  * An antenna, ideally roof mounted, with good quality coax back to the radio. Colinear antennas like the X-30 / X-50 are ideal for this.
+==== Alternatives ====
+You can swap out the NinoTNC for an instance of Dire Wolf with its KISS turned on, but that is beyond the scope of this guide.
 ===== NoV =====