Differences

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

--- packet:qttermtcp [2023/11/15 11:39] – explain and configure "TALK" command in QtTermTCP and bpq32 m0odz
+++ packet:qttermtcp [2025/06/02 21:21] (current) – m0lte
@@ Line 1: / Line 1: @@
 ====== QtTermTCP ======
+Official Website: https://www.cantab.net/users/john.wiseman/Documents/QtTermTCP.html
 QtTermTCP is a software package created by John G8BPQ that acts as a "terminal" for interacting with packet radio stations. It can connect to directly to a BPQ node using FBB over IP, or the more recent beta version supports KISS, both with a directly connected serial TNC or over TCP to something like Dire Wolf.
@@ Line 27: / Line 29: @@
 If you have a Debian-like OS, such as Ubuntu, Raspberry Pi OS, or indeed Debian itself, please consider using the repository here: https://github.com/Online-Amateur-Radio-Club-M0OUK/oarc-packages - instead of following the manual installation steps below.
+==== MacOS Download ====
+Download [[https://www.dropbox.com/scl/fo/5x7y3hlkfgtvjx35g5dnm/AHhwU7hPuDG_5xU3MFbt9rI?rlkey=se06u2h1354lle6kk1omu41p1&dl=1|QTTermTCP.app]] (version 0.0.0.77)
+==== MacOS with Brew ====
+If you use MacOs with the [[https://brew.sh/|Brew Package Manager]] a tap has been set up that will compile the QtTermTCP binary from source including dependencies:
+<code>
+brew install tomwardill/oarc-qttermtcp-tap/oarc-qttermtcp
+QtTermTCP
+</code>
+This installs the QtTermTCP app as if it was a CLI app, so it must be started from the terminal.
+==== Ubuntu 22.04 - standard installation ====
+In almost every case, you are better off installing by following this guide than building it yourself: https://guide.foxk.it/clients/qtttcp/
 ==== Ubuntu 22.04 - manual installation ====
@@ Line 67: / Line 87: @@
 You should now be able to launch QtTermTCP from the "Applications" menu
+==== Raspbian Desktop - standard installation ====
+In almost every case, you are better off installing by following this guide than building it yourself: https://guide.foxk.it/clients/qtttcp/
 ==== Raspbian Desktop - manual installation ====
@@ Line 75: / Line 99: @@
 <code>
 # First let's install the support packages.
-sudo apt-get install -y qt5-qmake qtbase5-dev libqt5serialport5-dev git
+sudo apt-get install -y qt5-qmake qtbase5-dev libqt5serialport5-dev qtmultimedia5-dev git
 # Move to the user's home folder and create a source folder.
@@ Line 198: / Line 222: @@
 Open QTTermTCP. Assuming everything is setup correctly you should see "AGW Connected" in the bottom status bar.
 To attempt to Connect, in the top bar select ''%%Connect%%'' > ''%%AGW Connect%%'' and enter the call sign of the station you wish to connect to. Digis can usually be left empty if you're in direct range of the node you're connecting to. You'll also have to select the radio port. For a single modem connection this will be the first in the list.
@@ Line 208: / Line 231: @@
 ==== LISTEN ====
-QtTermTCP has a very nice feature that ties directly with the TALK command.  When set up correctly if a remote user types "TALK" and your node handles it a tab will open on your QtTermTCP app and you can communicate directly with that user.
+QtTermTCP has a very nice feature that ties directly with the TALK command.\\
+When set up correctly if a remote user types "TALK" and your node handles it a tab will open on your QtTermTCP app and you can communicate directly with that user.\\
+For this configuration example (it is actually mine), I have the TNC connected to one machine running linBPQ and my main machine running QtTermTCP.\\
+\\
+I need to know my main machine's IP address (not the internet IP address, my internal network IP address).\\
+''//192.168.1.175//''\\
+I also need a port number on my main machine to listen on.  I will use\\
+''//8015//''\\
+In QtTermTCP, click on the ''Listen'' menu. A new window will open as below:\\
+{{:packet:m0odz_qttermtcp_listen.png?400|}}\\
+Check the box ''[X] Enable Listen''\\
+Fill in the port number (''//8015//'' in my example)\\
+Fill in the CText box with the information the end user will see when they use the "TALK" command\\
+Click the OK button.\\
+If you notice a mistake later you can Click on the "Listen" menu item again to change it.\\
+\\
+On the node itself you need to add the TALK command to bpq32.cfg.  Below I show mine.\\
+''APPLICATION //4//,TALK,att //2// //192.168.1.175// //8015//,//GB7ODZ-5//,//ODZTLK//,        ; TALK Application''\\
+Step by step:\\
+''APPLICATION //4//''\\
+This is the application number, you can have between 1 and 32.  Ensure the number is unique (you can't have 2 application 4 lines).\\
+''TALK''\\
+This is the command the end user types to activate the command\\
+''att //2// //192.168.1.175// //8015//''\\
+Attach to port ''//8015//'' on IP address ''//192.168.1.175//'' using BPQ port ''//2//'' (this is my node's telnet port, ''PORTNUM //2//'').\\
+''//GB7ODZ-5//''\\
+This is a direct connection to the TALK command.  The end user could type ''C //GB7ODZ-5//'' and it would be as if they connected to my node as normal and then typed the "TALK" command\\
+''//ODZTLK//''\\
+This is the alias of ''//GB7ODZ-5//'' and can be used in the same manner (''C //ODZTLK//'')\\
+\\
+Save the config file and restart bpq32.\\
+\\
+One thing I do in QtTermTCP is to enable tabbed windows which means I can have multiple connections in one app.\\
+Click on the ''Setup'' menu and then ''Tabbed''.\\
+Also, tick ''[X] Beep on inbound connections''.  This will make a noise when the end user connects to ''TALK''.\\
+When the end user connects to ''TALK'', a tab at the bottom will show the remote user's callsign.\\
+If you change the "Tabbed" option then restart QtTermTCP.\\
+\\
+{{:packet:m0odz_qttermtcp_setup_tabbed_window.png?400|}}\\
+\\
-For this configuration example (it is actually mine), I have the TNC connected to one machine running linBPQ and my main machine running QtTermTCP.
+===== Building from source =====
-I need to know my main machine's IP address (not the internet IP address, my internal network IP address).
-.168.1.175
-I also need a port number on my main machine to listen on.  I will use
-In QtTermTCP, cick on the Listen menu. A new window will open as below:
-{{:packet:m0odz_qttermtcp_listen.png?400|}}
-Check the box "[X] Enable Listen
-Fill in the port number (8015 in my example)
-Fill in the CText box with the information the end user will see when they use the "TALK" command
-Click the OK button.
-If you notice a mistake later you can Click on the "Listen" menu item again to change it.
-On the node itself you need to add the TALK command to bpq32.cfg.  Below I show mine.
+This is not necessary for most use cases, just for reference.
-APPLICATION 4,TALK,att 2 192.168.1.175 8015,GB7ODZ-5,ODZTLK,        ; TALK Application
-Step by step:
-APPLICATION 4
-This is the application number, you can have between 1 and 32.  Ensure the number is unique (you can't have 2 application 4 lines).
-TALK
-This is the command the end user types to activate the command
-att 2 192.168.1.175 8015
-Attach to port 8015 on IP address 192.168.1.175 using BPQ port 2 (this is my node's telnet port).
-GB7ODZ-5
-This is a direct connection to the TALK command.  The end user could type "C GB7ODZ-5" and it would be as if they connected to my node as normal and then typed the "TALK" command
-ODZTLK
-This is the alias of "GB7ODZ-5" and can be used in the same manner ("C ODZTLK")
-Save the config file and restart bpq32.
+==== On Windows ====
-One thing I do in QtTermTCP is to enable tabbed windows which means I can have multiple connections in one app:
+As of 0.0.0.79 commit a5e1b1389cbd9b3718b9ae41277f90633154cf47 from <nowiki>git://vps1.g8bpq.net/QtTermTCP</nowiki>
-{{:packet:m0odz_qttermtcp_setup_tabbed_window.png?400|}}
-Ensure you tick [X] Beep on inbound connections.  This will make a noise when the end user connects to TALK.
+With VS2022 on Windows 11
-When the end user connects to TALK, a tab at the bottom will show the remote callsign.
+Requires:
+  * C++ desktop development workload installed in VS Installer
+  * [[https://download.microsoft.com/download/5/C/3/5C3770A3-12B4-4DB4-BAE7-99C624EB32AD/windowssdk/winsdksetup.exe|Windows SDK 10.0.17763.0]] (VS will tell you if the version needed is now different)
+  * [[https://aka.ms/vs/15/release/vs_buildtools.exe|VS 2017 Build Tools]]
+  * Qt Visual Studio Tools extension (Extension Manager)
+  * [[https://download.qt.io/archive/qt/5.14/5.14.2/qt-opensource-windows-x86-5.14.2.exe|Qt 5.14.2]] (check version in QtInstall element in QtTermTCP.vcxproj) - you just need the msvc2017 bits
+Notes:
+  * Remove the hard coded path from the .sln file
+  * In the Qt VS Tools extension, add a Qt installation named "5.14.2" pointed at C:\Qt\Qt5.14.2\5.14.2\msvc2017\bin - this is referenced from the project file
+  * Run C:\Qt\Qt5.14.2\5.14.2\msvc2017\bin>windeployqt.exe C:\git\vps1.g8bpq.net\QtTermTCP\Win32\Debug
+==== On Debian-ish Linux (including WSL) ====
+Tested on Ubuntu 24.04
+<code>
+sudo apt install -y qt5-qmake qtbase5-dev libqt5serialport5-dev qtmultimedia5-dev
+mkdir build && cd build
+qmake ..
+make -j4
+</code>