| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| qttermtcp-node [2026/02/23 16:01] – n3vem | qttermtcp-node [2026/02/28 19:20] (current) – formatting w1cdn |
|---|
| ====== Using QTtermTCP With Your Node - Quick Start ====== | ====== Using QtTermTCP With Your Node - Quick Start ====== |
| |
| The goal of this article is to give you just enough info to start using QTtermTCP to interact with your node (and others!). For a full guide of QTtermTCP, refer to the [[https://www.cantab.net/users/john.wiseman/Documents/QtTermTCP.html|author's information]]. | The goal of this article is to give you just enough info to start using QtTermTCP to interact with your node (and others!). For a full guide of QtTermTCP, refer to the [[https://www.cantab.net/users/john.wiseman/Documents/QtTermTCP.html|author's information]]. |
| |
| If you followed the FARPN getting started tutorials, you should be able to find a shortcut to QTTermTCP in the applications menu on your Raspberry Pi or whatever other device you installed your packet station software onto. | If you followed the FARPN [[software-configuration-tutorials|getting started tutorials]], you should be able to find a shortcut to QtTermTCP in the applications menu on your Raspberry Pi or whatever other device you installed your packet station software onto. |
| |
| {{:qttermtcp.png?400|}} | {{:qttermtcp.png?400|}} |
| {{:qttermtcpnewhost.png?400|}} | {{:qttermtcpnewhost.png?400|}} |
| |
| You'll be connecting to your own node locally, not via RF, so in the dialog box that pops up, you'll want to enter the appropriate info. Some of this will come from the user information that you put in the telnet section of your ~/.config/linbpq/bpq32.cfg file, so you may want to open that file for reference. | You'll be connecting to your own node locally, not via RF, so in the dialog box that pops up, you'll want to enter the appropriate info. Some of this will come from the user information that you put in the telnet section of your ''~/.config/linbpq/bpq32.cfg'' file, so you may want to open that file for reference. |
| |
| **Host Name**: 127.0.0.1 | **Host Name**: 127.0.0.1 |
| |
| |
| You should have a line that looks something like this, in your Telnet section. The first "call" is your username (it doesn't actually have to be your callsign.) That's the value you enter in the "User:" field of QTtermTCP. | You should have a line that looks something like this, in your Telnet section. The first "call" is your username (it doesn't actually have to be your callsign.) That's the value you enter in the "User:" field of QtTermTCP. |
| |
| the "password" should be your password (you did change that right?!) and that is what you enter in the "Password:" field of QTTermTCP | The "password" should be your password (you did change that right?!) and that is what you enter in the "Password:" field of QtTermTCP. |
| <code> | <code> |
| USER=call,password,CALL,NODE,SYSOP | USER=call,password,CALL,NODE,SYSOP |
| {{:qttermtcphostvalues.png?400|}} | {{:qttermtcphostvalues.png?400|}} |
| |
| Click Save when done! | Click ''Save'' when done! |
| |
| |
| Back at the main screen, click connect, and choose the connection you just created. You should be rewarded with a prompt for you node in the bottom half of the window, and in the top you should start seeing some packet activity scrolling by. The volume of activity in the top will depend on band, mode and conditions, since this is what your station is receiving! Things in red are what your station sends, so if you set up beacons in your config file, or elsewhere, you'll see those periodically get sent. | Back at the main screen, click connect, and choose the connection you just created. You should be rewarded with a prompt for your node in the bottom half of the window, and in the top you should start seeing some packet activity scrolling by. The volume of activity in the top will depend on band, mode and conditions, since this is what your station is receiving! Things in red are what your station sends, so if you set up beacons in your config file, or elsewhere, you'll see those periodically get sent. |
| |
| {{:qttermtcpconnected.png?400|}} | {{:qttermtcpconnected.png?400|}} |
| ? | ? |
| </code> | </code> |
| as this will generate a list of applications/commands you can run. If you used our guides, that will likely look similar to this: | as this will generate a list of applications/commands you can run on your own node. If you used our guides, that will likely look similar to this: |
| <code> | <code> |
| ? | ? |
| </code> | </code> |
| |
| play around with the options and see what happens! | Enter one of those commands to start that application. Play around with the applications and see what happens! |
| A nice cheat sheet of commands for you as the SYSOP is [[https://ham.packet-radio.net/packet/bpq32/bpq32-guide/bpq-user-and-sysop-commands.pdf|available here]], thanks to PY2BIL | |
| | A nice cheat sheet of commands for you as the SYSOP is [[https://ham.packet-radio.net/packet/bpq32/bpq32-guide/bpq-user-and-sysop-commands.pdf|available here]], thanks to PY2BIL. |
| |
| For additional "things to do" now that you have this up and running, check out our "[[now-what|Now What?]]" section. | For additional "things to do" now that you have this up and running, check out our "[[now-what|Now What?]]" section. |
| |
