packet-ninotnc-next-steps
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| packet-ninotnc-next-steps [2023/01/06 19:31] – [I want to run a node] m0ukf | packet-ninotnc-next-steps [2023/04/10 17:14] (current) – [I want to run a node] m0lte | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| {{: | {{: | ||
| - | 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. | 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:// | [[https:// | ||
| - | More detail | + | === 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 | ||
| + | * 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 | ||
| + | |||
| + | * 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, | ||
| + | |||
| + | == 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 ==== | ==== I want to run a node ==== | ||
| Line 59: | Line 89: | ||
| 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: |
| - | * [[packet-linbpq-x86|here]] is a guide for Ubuntu/ | + | * [[packet: |
| 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. | 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 | + | |
packet-ninotnc-next-steps.1673033489.txt.gz · Last modified: by m0ukf
