Differences

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

--- tutorial-packet-on-pi [2024/11/17 03:36] – [Audio - ALSA, not Pulse] kc2ihx
+++ tutorial-packet-on-pi [2025/01/12 18:56] (current) – kc2ihx
@@ Line 172: / Line 172: @@
 </code>
-When you're done, you should run ''sudo ldconfig ~/.local/bin/'' to register the shared libraries created by Hamlib.
+When you're done, or anytime after you install libraries via your package manager (e.g. ``apt install``) you should run ''sudo ldconfig ~/.local/bin/'' to register the shared libraries created by Hamlib. [[https://groups.io/g/KM4ACK-Pi/topic/hamlib_4_5_4_symbol_lookup/97067606|(source)]]
+===== QtTermTCP Desktop/Menu Icon =====
+Here are some suggestions for basic .desktop file entries for QtTermTCP. You’ll need to replace USER with your username. This will give you a nice shortcut in the applications menu.  This file to create this is located at ''~/.local/share/applications/qttermtcp.desktop''
+<code>
+[Desktop Entry]
+Name=QTTermTCP
+Path=/home/USER/.config/qttermtcp/
+Exec=QtTermTCP
+Icon=/home/USER/.local/share/icons/QtTermTCP.ico
+Terminal=false
+Type=Application
+</code>
 ====== Audio - ALSA, not Pulse ======
@@ Line 182: / Line 195: @@
 </code>
+Next we'll configure ALSA -- despite the jokes on the Internet, Linux audio isn't //that bad// for a simple case like ours.  That said, you’ll need to do some experimenting here but it shouldn’t be all that different from what we have below. You’ll need to know the sample rates supported by your device though. If you poke around in ''/proc/asound/'' you’ll find your card or you can run 'arecord -l' and 'aplay -l' to get a list of devices.
-====== rigctld (and udev rules) ======
+For example, run ''cat /proc/asound/card3/stream0'':
+<code>
+Burr-Brown from TI USB Audio CODEC at usb-0000:01:00.0-1.3.2, full speed : USB Audio
+Playback:
+  Status: Running
+    Interface = 1
+    Altset = 1
+    Packet Size = 192
+    Momentary freq = 48000 Hz (0x30.0000)
+  Interface 1
+    Altset 1
+    Format: S16_LE
+    Channels: 2
+    Endpoint: 0x02 (2 OUT) (ADAPTIVE)
+    Rates: 32000, 44100, 48000
+    Bits: 16
+    Channel map: FL FR
+</code>
+This is how you can set the default index for your USB audio card to force it to a consistent reboot safe value for the ALSA configuration. With only one USB audio device (the rig audio interface) this works well.
+Edit ''/etc/modprobe.d/alsa-base.conf'' to add:
+<code>
+options snd_usb_audio index=3
+</code>
+Edit your ''/etc/asound.conf'' file to add a hardware alias to this device.
+<code>
+pcm.scu {
+    type hw
+    card 3
+    device 0
+    rate 44100
+}
+</code>
+====== rigctld for CAT/CIV ======
+Configuring rigctld is a crucial step to getting the rest of this setup running smoothly. The exact commands may be a little different depending on your gear. What we need is ''rigctld'' running in the background to give us a CAT/CIV interface to play with.
+You’ll need to change:
+  * ''USER'' to your username
+  * ''YOUR_RIG'' You’ll need to find the number for your rig by running ''rigctld -l | less''
+  * ''CAT_DEVICE'': You’ll need to find your USB CAT/CIV device with ''ls /dev/ | grep tty''.  Likely it is ''/dev/ttyUSB0'' unless you have other USB serial devices plugged in.
+First we'll setup a ''systemd'' service for ''rigctld'' to make sure it comes up at boot, by creating the file ''/etc/systemd/system/rigctld.service'' with the following contents:
+<code>
+[Unit]
+Description=rigctld Start Script
+After=network.target
+[Service]
+Restart=always
+RestartSec=20
+StartLimitInterval=60
+StartLimitBurst=3
+User=USER
+Group=USER
+ExecStart=rigctld -m YOUR_RIG -r CAT_DEVICE
+SyslogIdentifier=rigctld-Debug
+[Install]
+WantedBy=multi-user.target
+</code>
+Then enable and start the service with:
+<code>
+sudo systemctl enable rigctld.service
+sudo systemctl start rigctld.service
+</code>
+If for whatever reason you need to make an edit to a systemd service entry you’ll need to reload systemd and start the service again.
+<code>
+sudo systemctl daemon-reload
+sudo systemctl restart rigctld.service
+</code>
+To check on the status of a service we use the ‘status’ command. At the bottom of the output we’ll get essentially a tail of ''stdout'' (the program's standard output). This is super handy for checking out issues.
+<code>
+sudo systemctl status rigctld.service
+</code>
+If we want to get really fancy we can get a running live log of the service using journalctl. The -u option gives a ‘tail -f’ like output. I use this so much I have a short alias for watching the output of my BBS services. I much prefer this to using screen because we get logging for troubleshooting and many of these daemons cannot take terminal input once run anyway.
+<code>
+journalctl -u rigctld.service
+</code>
+====== udev rules for your transceiver ======
+To make it reboot safe I would make a udev rule. Here is an example of mine. I use /dev/yaesucat as my CAT device in the above systemd entry as result of the entry below. The general idea is that you find a specific device identifier using the command below. This was a little tricky as the SCU-17 has two serial devices with the same hardware serial number so my goto identifier didn’t work in this case.
+Start by running ''udevadm info -q property -n /dev/ttyUSB0'', which will return information about the USB device:
+<code>
+DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/ttyUSB0/tty/ttyUSB0
+DEVNAME=/dev/ttyUSB0
+MAJOR=188
+MINOR=0
+SUBSYSTEM=tty
+USEC_INITIALIZED=9023171
+ID_BUS=pci
+ID_VENDOR_ID=0x1106
+ID_MODEL_ID=0x3483
+ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
+ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
+ID_PCI_INTERFACE_FROM_DATABASE=XHCI
+ID_VENDOR_FROM_DATABASE=VIA Technologies, Inc.
+ID_MODEL_FROM_DATABASE=VL805 USB 3.0 Host Controller
+ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3.1:1.0
+ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_3_1_1_0
+ID_USB_MODEL=CP2105_Dual_USB_to_UART_Bridge_Controller
+ID_USB_MODEL_ENC=CP2105\x20Dual\x20USB\x20to\x20UART\x20Bridge\x20Controller
+ID_USB_MODEL_ID=ea70
+ID_USB_SERIAL=Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_011F3FE4
+ID_USB_SERIAL_SHORT=011F3FE4
+ID_USB_VENDOR=Silicon_Labs
+ID_USB_VENDOR_ENC=Silicon\x20Labs
+ID_USB_VENDOR_ID=10c4
+ID_USB_REVISION=0100
+ID_USB_TYPE=generic
+ID_USB_INTERFACES=:ff0000:
+ID_USB_INTERFACE_NUM=00
+ID_USB_DRIVER=cp210x
+ID_MM_CANDIDATE=1
+DEVLINKS=/dev/yaesucat /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3.1:1.0-port0
+TAGS=:systemd:
+CURRENT_TAGS=:systemd:
+</code>
+From there we want to grab some unique information to help identify this device as our transceiver and create a ''udev'' rules file for the device that'll give it a meaningful and consistent name.
+Add some variation of the following to a file in ''/etc/udev/rules.d/'' such as this example called ''80-yaesu-scu17.rules'', using information about the device from ''udevinfo'' above:
+<code>
+ENV{MAJOR}!="?*", GOTO="yaesucat_rules_end"
+SUBSYSTEMS=="usb-serial", GOTO="yaesucat_usb_rules"
+GOTO="yaesucat_rules_end"
+LABEL="yaesucat_usb_rules"
+# YAESU SCU-17
+ENV{ID_USB_INTERFACE_NUM} == "00", SYMLINK+="yaesucat", MODE="660", GROUP="dialout"
+LABEL="yaesucat_rules_end"
+</code>
+After creating the file, run ''sudo udevadm control --reload'' to create a new device called ''/dev/yaesucat''.
+====== What's Next? ======
+After following this tutorial you should have a 'reboot safe' hardware configuration, making it easier to configure various amateur radio applications for use with FARPN.
+From here, you should configure QtTermTCP or another packet client and try connecting to a node!