Differences

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

--- packet-ninotnc-next-steps [2023/01/06 19:30] – m0ukf
+++ packet-ninotnc-next-steps [2023/04/10 17:14] (current) – [I want to run a node] m0lte
@@ Line 9: / Line 9: @@
 {{:kantronicstncwiring.png|}}
-The other end needs to be wired for your radio. This is specific to your radio. [[packet-transceiver-wiring|More here on that]].
+The other end needs to be wired for your radio. This is specific to your radio. [[packet:cables|More here on that]].
 The next thing you need to do is configure your NinoTNC. It has 2 groups of 4 switches, labelled SIGNALS and MODE.
@@ Line 49: / Line 49: @@
 [[https://www.cantab.net/users/john.wiseman/Downloads/Beta/piQtTermTCP|Linux ARM (Raspberry Pi)]]
-More detail on setting this up shortly, including how to QSO!
+=== QSO time ===
+To use QtTermTCP as a front-end for a KISS modem, such as NinoTNC, follow these steps:
+  * Start QtTermTCP
+  * Setup menu -> KISS setup
+  * Enable KISS interface: tick
+  * MYCALL: your callsign
+  * Select Device: something like ttyACM0 on Linux, COM3 on Windows
+  * Speed: as appropriate for your modem, 57600 for NinoTNC
+Leave the host and port blank, and the rest at defaults.
+== To make an outgoing connection: ==
+You can connect to any other station which is listening on frequency and accepting connections. This can be a full blown node right down to another individual station.
+  * Connection menu -> KISS connect
+  * Connection mode: Session
+  * Call to: the callsign of the station you want to connect to, e.g. GB7RDG
+  * Digis: as appropriate, or none if you're connecting directly.
+== To accept incoming connections from other stations: ==
+  * Have two stations with different callsigns
+  * On station 1, Listen menu -> Enable Listen (fill out CText with a welcome message if you like)
+  * On station 2, follow the instructions above ("To make an outgoing connection").
+Once connected, have a QSO using your keyboards! You can also exchange files using the YAPP menu.
+Remember on Linux to add your user to the `dialout` group to be able to access serial ports.
 ==== I want to run a node ====
@@ Line 57: / Line 87: @@
 This is quite an involved topic but one thing we want to do with this initiative is to demystify and simplify it.
-LinBPQ / BPQ32 is node software which is current and maintained//
+LinBPQ / BPQ32 is node software which is current and maintained
-  * [[packet-linbpq|here]] is a guide on getting it running on the Pi.
+* [[packet:linbpq_pi_installation|here]] is a guide on getting it running on the Pi.\\
-  * [[packet-linbpq-x86|here]] is a guide for Ubuntu/Linux Mint/Debian Computers
+* [[packet:linbpq_pc_installation|here]] is a guide for Ubuntu/Linux Mint/Debian Computers
 LinBPQ is a highly configurable and flexible piece of software - this makes it fairly complex. It is likely that for the national network we will settle on using LinBPQ, however there will be standards and simplification to help matters - maybe even scripts / a downloadable image. If you play with LinBPQ now, and you wish to join a national network project, expect to need to change your configuration to match.
+[An example config file is [[packet:linbpq-sample-config|here]] for reference if needed]
-LinBPQ is a highly configurable and flexible piece of software - this makes it fairly complex. It is likely that for the national network we will settle on using LinBPQ, however there will be standards and simplification to help matters - maybe even scripts / a downloadable image. If you play with LinBPQ now, and you wish to join a national network project, expect to need to change your configuration to match.