💾 Archived View for alaskalinuxuser.ddns.net › 2021-11-27.gmi captured on 2024-09-29 at 00:18:47. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
">
* 024w, https://alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/
photo_2021-09-17_06-02-36-1-300x169.jpg 300w, https://
alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-09-17_06-
02-36-1-768x431.jpg 768w, https://alaskalinuxuser3.ddns.net/wp-content/
uploads/2021/09/photo_2021-09-17_06-02-36-1.jpg 1280w" sizes="(max-
width: 1024px) 100vw, 1024px" />
024w, https://alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-
09-17_06-02-39-300x169.jpg 300w, https://alaskalinuxuser3.ddns.net/wp-content/
uploads/2021/09/photo_2021-09-17_06-02-39-768x431.jpg 768w, https://
alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-09-17_06-02-
39.jpg 1280w" sizes="(max-width: 1024px) 100vw, 1024px" />
024w, https://alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-
09-17_06-02-47-300x169.jpg 300w, https://alaskalinuxuser3.ddns.net/wp-content/
uploads/2021/09/photo_2021-09-17_06-02-47-768x431.jpg 768w, https://
alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-09-17_06-02-
47.jpg 1280w" sizes="(max-width: 1024px) 100vw, 1024px" />
024w, https://alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-
09-17_06-02-42-300x169.jpg 300w, https://alaskalinuxuser3.ddns.net/wp-content/
uploads/2021/09/photo_2021-09-17_06-02-42-768x431.jpg 768w, https://
alaskalinuxuser3.ddns.net/wp-content/uploads/2021/09/photo_2021-09-17_06-02-
42.jpg 1280w" sizes="(max-width: 1024px) 100vw, 1024px" />
Last post I talked about trying to use PAT, and it wasn’t working very well for
me. I had set up PAT and Ardop, but I kept getting errors and couldn’t start
trying to connect. Essentially, since Ardop couldn’t talk to the radio, it
assumed it wasn’t on and couldn’t proceed. But I had a little bit more time
this week and finally got it ironed out. Perhaps you are here because you too
have a radio without computer controls so you have to manually set your
transmit and receive bands, etc.
Eventually, I got it to work by using ardopc, flrig, rigctl, and pat together.
I took a lot of information from this post:
https://rockfloat.com/ham/pat_linux.html
But had to edit it for a non-cat, manually controlled radio. Essentially, I had
two choices, use a “dummy” radio with hamlib, or have hamlib get input from
flrig. I tried both, but went with flrig in the end, as it was much easier to
adjust with a gui.
So, I’ll show you my setup and maybe it can help you if you are doing the same
sort of thing. First I ran $ pat configure and edited it like so:
{\n "mycall": "KL4TH",\n "secure_login_password": "<EDITED>",\n
"auxiliary_addresses": [],\n "locator": "BP64du",\n "service_codes":
[\n "PUBLIC"\n ],\n "http_addr": "localhost:8080",\n "motd": [\n
"Open source Winlink client - getpat.io"\n ],\n "connect_aliases": {\n
"telnet": "telnet://{mycall}:CMSTelnet@cms.winlink.org:8772/wl2k"\n },\n
"listen": [],\n "hamlib_rigs": {"myrig": {"address": "localhost:
4532", "network": "tcp"}},\n "ax25": {\n "port": "wl2k",\n
"beacon": {\n "every": 3600,\n "message": "Winlink P2P",\n
"destination": "IDENT"\n },\n "rig": ""\n },\n "serial-tnc":
{\n "path": "/dev/ttyUSB0",\n "baudrate": 9600,\n "type":
"Kenwood"\n },\n "winmor": {\n "addr": "localhost:8500",\n
"inbound_bandwidth": 1600,\n "drive_level": 0,\n "rig": "",\n
"ptt_ctrl": false\n },\n "ardop": {\n "addr": "localhost:8515",\n
"arq_bandwidth": {\n "Forced": false,\n "Max": 500\n },\n
"rig": "myrig",\n "ptt_ctrl": false,\n "beacon_interval": 0,\n
"cwid_enabled": true\n },\n "pactor": {\n "path": "/dev/
ttyUSB0",\n "baudrate": 57600,\n "rig": "",\n
"custom_init_script": ""\n },\n "telnet": {\n "listen_addr": ":
8774",\n "password": ""\n },\n "gpsd": {\n "enable_http":
false,\n "use_server_time": false,\n "addr": "localhost:2947"\n
},\n "schedule": {},\n "version_reporting_disabled": false,\n
"forms_path": "/home/alaskalinuxuser/.wl2k/Standard_Forms"\n}\n
I don’t actually have a serial TNC, nor did I use GPSD, Pacto, Telnet, Winmor,
or the like. I just left those per the defaults. I did edit the “ardop”
section, and the hamlibs section to be “myrig”. I then used:
$ aplay -l
To list my sound cards and got the information for ardop to use. After
downloading Ardopc from their website, I put it to work with this command:
$ ardopc_64 8515 plughw:1,0 plughw:1,0\n\nInput peaks = -10833, 11449\n Command
Trace TO Host INPUTPEAKS -10833 11449\nInput peaks = -10274, 9467\n Command
Trace TO Host INPUTPEAKS -10274 9467\nInput peaks = -11784, 11576\n Command
Trace TO Host INPUTPEAKS -11784 11576\nInput peaks = -12445, 11873\n Command
Trace TO Host INPUTPEAKS -12445 11873\nInput peaks = -10387, 10518\n Command
Trace TO Host INPUTPEAKS -10387 10518\nInput peaks = -11437, 10818\n Command
Trace TO Host INPUTPEAKS -11437 10818\nInput peaks = -10291, 11485\n Command
Trace TO Host INPUTPEAKS -10291 11485\nInput peaks = -10508, 10822\n Command
Trace TO Host INPUTPEAKS -10508 10822\nInput peaks = -10555, 10137\n Command
Trace TO Host INPUTPEAKS -10555 10137
In the above, ardopc_64 is the 64 bit version of ardop, the 8515 is the port to
use on the local machine, and the plughw:1,0 is for my sound card (output then
input I believe, but I may have that backwards). The trailing input peaks are
what it was hearing from the radio, which was on.
Now I started flrig from the Ubuntu menu. It has a pretty nice gui and you can
just click on the numbers to change them up or down. It of course can’t
actually talk to my radio, but ardop doesn’t know that. This is the critical
part, because whatever I set flrig to, that is what rigctl, ardop, and pat are
going to think the real radio is tuned to.
With flrig running, I then started rigctl like so:
$ rigctl -m 4 -s 4800\n\nRig command: f\nFrequency: 14091000\n\nRig command:
f\nFrequency: 7102000\n\nRig command: f\nFrequency: 7102000\n\nRig command:
f\nFrequency: 7102000\n\nRig command:
The -m 4 means the fourth option in it’s numbered radio options, which happens
to be flrig input. The -s option is the baud rate speed. The commands I was
running after that were the “f” command, to get the currently set frequency.
You can see that in flrig, I was set to 14.091, then I changed to 7.102
instead, and rigctl was tracking my changes, which is a good sign.
With all of this set up, I finally was able to start pat with this command:
alaskalinuxuser@alaskalinuxuser-HP-2000-Notebook-PC:~$ pat --listen "ardop"
http\n2021/09/16 16:49:18 Unable to get frequency from rig myrig: dial tcp
127.0.0.1:4532: connect: connection refused.\n2021/09/16 16:49:18 Listening for
incoming traffic on ardop...\n2021/09/16 16:49:18 Starting HTTP service
(localhost:8080)...\n2021/09/16 16:49:18 ARDOP TNC (ARDOP TNC_1.0.4.1-BPQ)
initialized
Note the “connection refused” bit. I don’t actually have a rig that can be
controlled from the computer, so it says that it can’t connect. This is okay if
you are using an old radio like mine. You can also see that ardop was set up
and initialized, which is also a good sign.
Now I used the web gui of pat like normal. I simply chose to connect, then
chose ardop, then chose the RMS listing to get the list of known radio servers
and chose one from the list. In this example, I chose VY1WLK at 14.091 MHz.
When I did that I then adjusted my physical radio to that frequency, and
adjusted flrig to match. Now there was no error in pat about setting rig
control manually, since it believed that it had been done automatically, even
though I did actually do it manually.
Next I hit connect and this is what I got in the terminal/log:
2021/09/16 16:50:18 Connecting to VY1WLK (ardop)...
And my computer sent out the right “sounds” and that caused the signalink to
key the radio to transmit! If you can see the screenshots, you can also see
that I tried KL7EDK, and since it was in use, after hitting connect, it gave me
a log that it was “waiting for clear channel…” so it knows well enough to
listen before it speaks.
I have found though that connecting to these radio servers is rather
challenging, often taking numerous tries and with some stations being
impossible to connect to. But, to God be the glory, the setup finally works!
Linux – keep it simple.