Jnos and QtSoundModem

Today I was playing with Jnos, on my main system I have BPQ32 running with Direwolf and QtSoundModem. BPQ32 uses the Kiss port on Direwolf and the AGW port on QtSoundModem. Now I know that Jnos can easily handle the AGW interface/driver, so I linked Jnos with the AGW poort of Direwolf. attach agwpe agw 44.137.31.70 8000 ifconfig agw description “AGW – 1200 baud port” ax25 hport agw on trace agw 0111 Direwolf is running on 144.850Mhz 1k2 and 430.950Mhz 9k6 Now I thought it would be nice to hook Jnos to QtSoundModem as well. But BPQ32 already uses the AGW port of QtSoundModem. Now I had read that Maiko VE4KLM had written a Kiss over tcp/ip for Winrpr. Who doesn’t dare don’t win. Here we go. QtSoundmodem is running on 14.102Mhz 300Baud with 1100Hz on the left channel and 2000Hz on the right channel. Autoexec.nos attach winrpr qt0 44.137.31.76 8105 attach kiss qt0 1 qt1 # ifconfig qt0 description “Kiss tcp/ip port 14.102Mhz 1100Hz” ifconfig qt1 description “Kiss tcp/ip port 14.102Mhz 2200Hz” trace qt0 0x211 qt0.log 1000 trace qt1 0x211 qt1.log 1000 # ax25 hport qt0 on ax25 hport qt1 on The winrpr is the kiss over tcp/ip driver Read more

Direwolf Vs QtSoundModem (part 2)

Rx Only Okay, that was a bit of a disappointment. I ran the test at 14.1022Mhz on 300 Baud. I think the conditions were very bad in those 24 hours. For the test I use Kissutil. https://www.mankier.com/1/kissutil kissutil  can be used interactively for troubleshooting a KISS TNC. It is usable with direwolf and other generic KISS TNCs connected to a serial port. It can also be used as an application interface where each side places files in a directory for the other to process. First I wrote two start files for the test. Direwolf.sh #!/bin/bash cd /home/niels/testbed/ ./kiss-direwolf -p 8009 -o /home/niels/testbed/rec-direwolf Qtsm.sh #!/bin/bash cd /home/niels/testbed/ ./kiss-qtsm -p 8105 -o /home/niels/testbed/rec-qtsm The test ran for 24 hours, which is 86400 seconds. timeout -s 9 86400 ./qtsm.sh After 24 hours I can start counting the received frames. As you can see this is very disappointing. Now I understand that the focus of QtSoundModem is more in the HF area. With a difference of 4 frames, the difference between Direwolf and QtSoundModem is minimal. In fact, too few frames were received in the 24 hours to make a good comparison. Is my opinion. The next test we will try on 144.800Mhz the local Read more

Direwolf Vs QtSoundModem (part 1)

This is about RX and not TX. This has caused some headaches. I want to use one trx and one antenna for this test. (Icom 7300 and a Hyendfed)Now the problem is that Direwolf and QtSoundModem both use the sound card. Now you can’t both use the same sound card at the same time. So we will have to use two virtual sound cards and route the audio to these sound cards.  For this I use “pactl” with this I can manipulate the PulseAudio server. pactl load-module module-virtual-sink sink_name=direwolf And pactl load-module module-virtual-sink sink_name=qtsoundmodem Actually we are making a virtual audio card for Direwolf and QtSoundModem. Now we need to route the Audio from the input to the virtual audio card. This is possible with PavuControl. Setup Direwolf ADEVICE pulse ACHANNELS 1 CHANNEL 0 MYCALL N0CALL MODEM 300 1000 1200 AGWPORT 8008 KISSPORT 8009 Uhmmmmm port 8001.  I don’t understand that yet, in the config it really is port 8009. Setup QtSoundModem   Now I haven’t fully read up on PulseAudio and pactl and the virtual cable/cards. Perhaps my wording and references are not quite correct. Now I have the opportunity to test…..

Bpq32 with QtSoundModem and Hamlib

Yesterday I added 2 HF ports to my Bpq32 Node / BBS. I have chosen to use QtSoundModem and Hamlib. QtSoundModem is a Linux port or Soundmodem from UZ7HO. I use Hamlib/rigctld to take control of the Tranceiver. QtSoundmodem and Hamlib run on a different Raspberry than the BBS and Node. After some testing I found out that I need Hamlib version 3.3 to control the icom 7300. The versions 4.0 and 4.1 do not work for me. Apparently the icom 7300 is not being initialized. Can’t actually find out why this is. With the command “rigctld -l” you get a list of which tranceivers are supported. So I need number 373 for the Icom 7300. /usr/local/bin/rigctld -m 373 -r /dev/ttyUSB0 -s 19200 -T 44.137.31.76 -t 4532 & In the QtSoundModem.ini I have in the [Init] section. HamLibHost=44.137.31.76 HamLibPort=4532 PTT=HAMLIB PTTBAUD=19200 PTTMode=17 Now the bpq32.cfg PORT PORTNUM=4 ID=14.1022 +1100Hz DRIVER=UZ7HO CHANNEL=A PACLEN=80 CONFIG ADDR 44.137.31.76 8101 ; AGW port of QtSoundModem BEACONAFTERSESSION MAXSESSIONS=5 ENDPORT PORT PORTNUM=5 ID=14.1022 +2000Hz DRIVER=UZ7HO CHANNEL=B PACLEN=80 CONFIG ADDR 44.137.31.76 8101 ; AGW port of QtSoundModem BEACONAFTERSESSION MAXSESSIONS=5 ENDPORT With Hamlib it is also possible to control the TRX from Bpq32. I immediately added a Robust Read more

Linux Port of UZ7HO’s Soundmodem

Very good news, John G8BPQ has ported Soundmodem from UZ7HO to Linux. Mail from John G8BPQ. Andy UZ7HO has allowed me to port his Soundmodem to C so that it can be run run Linux systems. See https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html This is pre-Beta software. It has been tested by several people but is likely to still have bugs. 73, John G8BPQ

BPQ32 Example Soundmodem port

Example for a UZ7HO soundmodem port PORT ID=UZ7HO DRIVER=UZ7HO CHANNEL=A QUALITY=0 MAXFRAME=4 FULLDUP=0 FRACK=8000 RESPTIME=3000 RETRIES=10 PACLEN=128 TXDELAY=200 SLOTTIME=100 PERSIST=64 KISSOPTIONS=ACKMODE CONFIG ADDR 127.0.0.1 8100 PATH C:\RMS Express\soundmodem.exe MAXSESSIONS=4 ENDPORT  

New Soundmodem version is available UZ7HO

New Soundmodem version is available: http://uz7.ho.ua/packetradio.htm SoundModem v1.00b changes: – Added “DW QPSK 2400bd” and “DW 8PSK 4800bd” Direwolf compatible modes. The carrier frequency must be “1800Hz” (for a full compatibility with Direwolf). http://uz7.ho.ua/modem_beta/CHANGELOG.txt http://uz7.ho.ua/modem_beta/user_guide_v045b_EN.pdf Get the version V1.00b http://uz7.ho.ua/modem_beta/soundmodem100.zip

Direwolf Soundmodem

Direwolf source Direwolf example config ############################################################# # # # Configuration file for Dire Wolf # # # # Linux version # # # ############################################################# # card number reported by “arecord -l” command. ADEVICE plughw:0,1 ACHANNELS 1 ############################################################# # # # CHANNEL 0 PROPERTIES # # # ############################################################# CHANNEL 0 MYCALL PI1LAP-8 MODEM 1200 1200:2200 E+ PTT /dev/ttyUSB0 DTR TXDELAY 20 TXTAIL 10 KISSPORT 8001 FIX_BITS 1 PBEACON delay=1 every=30 overlay=S symbol=”digi” lat=51^33.52N long=003^48.15E power=4 height=15 gain=6 comment=”PI1LAP-10 RX\TX iGate Kortgene,ZLD JO11VN” via=WIDE1-1,WIDE2-1 DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #FILTER 0 1 t/wn IGSERVER aprs.pa4tw.nl:14580 IGLOGIN PI1LAP 20391 PBEACON sendto=IG delay=0:30 every=30:00 symbol=”igate” overlay=T lat=51^33.52N long=003^48.15E #PBEACON sendto=IG delay=0:30 every=60:00 symbol=”igate” overlay=T lat=42^37.14N long=071^20.83W IGTXVIA 0 WIDE1-1 WIDE2-1 IGFILTER m/250 FILTER IG 0 t/m # Finally, we don’t want to flood the radio channel. # The IGate function will limit the number of packets transmitted # during 1 minute and 5 minute intervals. If a limit would # be exceeded, the packet is dropped and message is displayed in red. IGTXLIMIT 6 10

RASPBERRY PI4 TRIFECTA TNC-BANK IMAGE COMPANION DOCUMENTATION

In memory of Red PE1RRR, We’ll keep the packets flying. Thanks my friend. Credits PE1RRR. DOWNLOAD WARNING: Cooling The use of this image is at own risk. Active (fan) or large area heatsink cooling is required to keep the RPI from overheating. For example, a heat sink case such as this one is sufficient if there is adequate airflow around the unit. While the image does not by default overclock your RPI4, it is necessary to put the RPI into Performance Mode, which will make it run hotter. Overclocking is highly recommended but is a manual step you must take full responsibility for. Before You Start Network is handled by DHCP. The SSH system is not running by default and this must be manually activated to generate host keys for the system using the raspi-config tool. Having the SSH system enabled will let you log in from a remote system (using PuTTY for example) on your own network, making it a lot easier to transfer copy & paste instructions from this document. You will still need a display, a keyboard and a mouse connected for initial setup. This document is not perfect, it is a work in progress. The image is the first of its kind so it isn’t perfect Read more

Winlink Gateway HB9AK

As Winlink Gateway i`m using HB9AK from Switzerland on dail 7.050Mhz. HB9AUR (Martin) is the Operator (SysOp) of HB9AK. I have test the system of Martin with Winmor, Ardop, Robust 300/600. I have a old AEA DSP2232 modem that can make Pactor 1, but i have some issues to get things going. HB9AK is a big boy with many possibilities. Here a small list. Technical details of HB9AK (JN36PV, 650 m asl): QRGs (dial frequency): 3’613.0, 7’050.0, 10’144.4(NB), 14’108.9, 18’114.4, 21’113.5 (NB: narrow band only). Use USB for all QRGs. Center frequency is 1.5 kHz higher than dial frequency. TRX1 (40m): KENWOOD TS-590S, dipole(N/S); Modes WINMOR, PACTOR(1-4), Robust Packet Radio, ARDOP, VARA TRX2 (30m): KENWOOD TS-590SG, dipole(N/S); Modes WINMOR(500), PACTOR(1-2), ARDOP TRX3 (20m): KENWOOD TS-590SG, dipole(N/S) or LogPer; Modes WINMOR, PACTOR(1-4), Robust Packet Radio, ARDOP, VARA TRX4 (80m/17m/15m): KENWOOD TS-590S, 80m dipole, 17/15m fan dipole; Modes WINMOR, PACTOR(1-4), Robust Packet Radio, ARDOP, VARA Technical details of HB9AK-1 (JN47LI, 1130 m asl): TRX5 (10m): ICOM IC-706, vertical dipole; Modes WINMOR, PACTOR(1-4), Robust Packet, ARDOP, VARA TRX6 (2m): MOTOROLA GM340, X-50; Mode Packet Radio AFSK 1200 Bd, BPSK 1200 Bd, BPSK 2400 Bd, QPSK 2400 bps, QPSK 3600 bps Technical details of Read more