Dire Wolf Software TNC

Re: Direwolf won't send APRS messages

richvantrease@... (Richard Vantrease) — Wed, 16 Apr 2025 07:02:03 -0700

I had these exact errors, someone suggested RFI.聽 Put a ferrite bead on the USB cable, and problem solved.聽

Re: Multiple Radio Culprit

stevene1@... (Steven) — Tue, 15 Apr 2025 12:46:09 -0700

It failed to transmit on either transceiver.聽 Here's my original conf file excerpt:

聽

#############################################################
# 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 145.825MHZ 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽#
#############################################################聽
ADEVICE1 plughw:4,0
ACHANNELS 1
MODEM 1200
#############################################################
# 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 #
# 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 CHANNELS 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 #
# 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽#
#############################################################聽
# 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 144.39 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 #
#############################################################
CHANNEL 0
MYCALL N7GEE-10
PTT /dev/ttyUSB0 RTS -DTR
#############################################################
# 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 145.825 聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 #
#############################################################
CHANNEL 2
MYCALL N7GEE-10
PTT /dev/ttyUSB1 RTS -DTR
##############################################################

聽

I tried swapping the USB cables also.聽 Since one soundcard cable is configured differently than the other (one CIV and the other not) I rather imagine its responsible for the CM108 failure.

Re: Direwolf won't send APRS messages

direwolf-groupsio@... (David Ranch) — Tue, 15 Apr 2025 08:16:41 -0700

To prove that this is an RFI issue, tune your radio to frequency you know where it will *refuse* to transmit.聽 Once QSYed, start up Direwolf and try tranmitting a packet.聽 See if the PTT indicator lights up and the errors from Direwolf and the OS go away.

--David
KI6ZHD

On 04/14/2025 09:48 PM, KQ4UDA via groups.io wrote:

Re: Direwolf won't send APRS messages

hope.aaron.c@... (KQ4UDA) — Tue, 15 Apr 2025 06:55:38 -0700

I'm having the same issue.

Hardware :聽 I'm using an sbitx v3 (pi 4b) > unpowered usba hub > usba to usbc adapter > digirig lite > baofeng.聽 The hardware is colocated, though the hf side of my sbitx is not powered up.聽 Of note, the digirig lite did work without issue being closely colocated with my old phone and worked great.聽 Yes I have ferrite beads involved.聽 Power supply is through the radio side of the sbitx via the gpio pins.聽 I have it plugged into a substantial battery pack rated for 12 amps of draw by the wiring.

Settings : KISS over tcp : localhost, 8001 (confirmed),聽

聽

Behavior :

Dire Wolf version 1.7
Includes optional support for: 聽hamlib cm108-ptt dns-sd

Reading config file /home/pi/.direwolf.conf
Audio device for both receive and transmit: plughw:3,0 聽(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using /dev/hidraw2 GPIO 3 for channel 0 PTT control.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on sbitx'
DNS-SD: Avahi: Service 'Dire Wolf on sbitx' successfully registered.

Attached to KISS TCP client application 0 on port 8001 ...

Ready to accept KISS TCP client application 1 on port 8001 ...
KISS protocol set hardware "TNC:", chan 0

"聽

聽

It does receive and decode very well.聽 Though I get persistent finicky complaints about the volume despite feathering the radio / mixer.

Everything is working fine until transmission time.聽 The radio is activated via ptt for a blip, then it turns off and off we go into errors as above.

Aaron
KQ4UDA

Re: Help with setup

dk7al@... (DK7AL) — Tue, 15 Apr 2025 02:46:02 -0700

Yes Sir,

that's what I did during my experiments and investigations. In the meantime I've managed to get my system running in good order. Thank you for your request.

Greetings.

Karl, DK7AL

Am 13.04.25 um 02:37 schrieb uspt via groups.io:

Re: Winlink Error

uspt@... — Mon, 14 Apr 2025 19:16:10 -0700

there are a few Digirig models; lite & mobile

and sub models as well; read carefully to make sure it features are correct for the application.聽

聽

if you want CAT control for your radio聽

make sure the cable is the correct one for the intended radio.聽

i really the compact size.

got two of them, one for HT and another for mobile station.聽

Re: Help with setup

uspt@... — Mon, 14 Apr 2025 19:15:55 -0700

have you run :
aplay -l
&
a record -l
to see what devices are on your ports ?

Re: Best Method to Link Over Network?

direwolf-groupsio@... (David Ranch) — Mon, 14 Apr 2025 07:56:24 -0700

AGW will do this very well.聽 On the Raspberry Pi with the radio (rpi#1), run Direwolf with AGW enabled.聽 Then on the other Raspberry Pi (rpi#2), setup your APRS application to use AGW and put in the IP address of Rpi#1 and it should just work.聽 If your APRS application doesn't support APRS, try doing something similar but with TCP-KISS instead.

--David
KI6ZHD

On 04/12/2025 11:06 PM, nick.k6nlc via groups.io wrote:

Re: Best Method to Link Over Network?

bob3bob3@... (Bob Cameron) — Sun, 13 Apr 2025 12:52:58 -0700

Is it worth doing at the basic private network level? ie make the non internet connected network route through the connected one? Lots of options here from straight routing and gateways to masquerade. Might be some security concerns of course. iptables as a firewall and only route the APRS packets can also be done.

Apart from routing are there any other uses for a direwolf instance on the non radio hardware network?

Cheers Bob VK2YQA

On 13/4/25 16:06, nick.k6nlc via groups.io wrote:

Best Method to Link Over Network?

nick.k6nlc@... — Sun, 13 Apr 2025 10:37:49 -0700

I want to link two separate PCs (or raspberry pi's) running on two separate routed networks similar to a KISS client/server configuration. Both networks have access to each other but only one has a radio resource and internet connection; I would like to send APRS data from one network without resources to the network that does.聽 Is there a method for achieving this?聽 The ICHANNEL feature looks like it would be able to do this but direwolf does not act as a KISS client.聽 I have a work around that uses another program to receive data via KISS and pass it to the internet via APRS-IS.聽 I would like to use direwolf, if possible, to keep the installations lightweight.

Re: Help with setup

bob3bob3@... (Bob Cameron) — Sat, 12 Apr 2025 20:19:23 -0700

Hi Karl

You have a pulseaudio installation. In many (but not all) of the basic Linux distributions the user cannot access the ALSA device directly, instead pulseaudio does that. This explains why on your first post that you had a resource busy error. The device list query allows a limited read only access of sorts.

It also explains why it worked when you removed the audio device spec from the DIrewolf config file. This causes the default聽 sound car device under pulseaudio to be used. In most distros you would use "pavucontrol" to set which device is used by which application, and the per application volume controls,

If the Linux box is dedicated for single app radio/sound card use then it is probably worth removing pulseaudio entirely. Giving your login user membership to the audio group may also work with pulseaudio left in place, but there may be random device locks if pulseaudio is left running. It is best to kill with "pulseaudio --kill" then checking the daemon has not respawned to test that direwolf is working okay. There are so many possible permutations how pulseaudio can be setup that I can only generalise.

If pulseaudio is being used by direwolf you may run into (random load dependent) latency and PTT/audio window issues during transmit (RX works fine). The general recommendation is not to run it, although I have personally worked through the problems and use it here.

Hope this info helps

Cheers Bob VK2YQA

https://aprs.fi/#!call=a%2FVK2YQA-12&timerange=43200&tail=43200

On 13/4/25 01:58, DK7AL wrote:

Re: GMSK

wb2osz@... (WB2OSZ) — Sat, 12 Apr 2025 12:37:38 -0700

(1)聽聽 Is the satellite transmitting AX.25?

(2)聽聽 Why do you have "ACHANNELS 2?"聽聽聽 That is for stereo input

(3)聽聽 Why do you have "MODEM 1200"聽 when you want to receive 9600?

(4)聽 How are you getting the audio from the radio into the computer?聽 Speaker audio does not have the required audio bandwidth.聽 You need to use the 9600 pin on the DATA2 socket.

聽

From the instruction manual, page 167, it looks like you need to enable聽 9600 bps mode.

57. 9600bps Mode (Default: OFF)
Turn the [DATA2] socket鈥檚 9600 bps data transmission
ON or OFF.
鈥� OFF : For only the regular audio (or slow data) trans-
mission.
鈥� ON : For 9600 bps data transmission.

聽

If you are still having trouble send me an audio recording from the 9600 pin.

聽

73,

John WB2OSZ

聽

GMSK

cassandra.dresler@... (cdres) — Sat, 12 Apr 2025 11:48:50 -0700

Hello all,

For background- here is the last topic I had on this project, which goes over my setup.
/g/direwolf/topic/108025301#msg9801
Basically, 2 computer ground stations set up with direwolf/rigctl for our cubesat. I have been working on the satellite transceiver for awhile, so it's been a minute since I have been on here, but I am currently trying to get the groundstation direwolf to decode a beacon message of 'test' from the transceiver. It is a trxvu, with a 9600 BPS, GMSK, and is running on i2c commands.

I can successfully begin the beacon from the TRXVU, being able to audibly here the packet on our ICOM-9100, but direwolf running on the ground station, being run in variations of [direwolf, direwolf -p, or direwolf -B 9600 -r 48000] all return no packet decoding.

the current config file is set up as such:
all commented, other than the following:
ACHANNELS 2
CHANNEL 0
MYCALL W5GB
MODEM 1200 === I have also tried to change this to 9600 and still no response
PTT RIG 2 localhost:4532
CHANNEL 1
MYCALL W5GB-1
MODEM 1200=== I have also tried to change this to 9600 and still no response
AGWPORT 8000
KISSPORT 8001
IGTXLIMIT 6 10
TXDELAY 30
TXTAIL 10

Any ideas?

Re: Help with setup

dk7al@... (DK7AL) — Sat, 12 Apr 2025 08:58:37 -0700

After a heavy tinkering session with the CM108 USB sound card this morning I managed to separate the bindungs of the USB sound card modem from the sound system of my Linux box. Now I can operate this item secure with the indication of "ADEVICE plughw:2,0" in the config file even after a reboot of my Linux box. If the LED D1 is permanently lid, which is a good indication that the chip is not in connection of the Linux system, further system calls will no longer appear via the USB sound card. After starting SW direwolf from CLI, D1 flashes on regular intervals and indicates it is in action by SW.

Now I am also impressed that the PTT (Pin 13) and COS (Pin 48) work both with the help of the CM108 chip. Time to bring these items in a plastic/metal box for a more durable handling in the next time.

Thank you all.

Greetings.
Karl, DK7AL

Re: Help with setup

dk7al@... (DK7AL) — Sat, 12 Apr 2025 08:17:53 -0700

Good morning folks,

I have a Linux box and the problem, that "ADEVICE plughw:1,0" in the config file does not work without complaining that a resource or device is busy. But commenting out this statement works, i.e. I can hear packet sound on the headphones. I am not sure if PTT cm108 works - because it is not yet checked.

Here are some details of my situation:

$ cm108
VID PID Product Sound ADEVICE ADEVICE HID [ptt]
--- --- ------- ----- ------- ------- ---------
** 0d8c 013c USB PnP Sound Device /dev/snd/pcmC1D0c plughw:1,0 plughw:Device,0 /dev/hidraw0
** 0d8c 013c USB PnP Sound Device /dev/snd/pcmC1D0p plughw:1,0 plughw:Device,0 /dev/hidraw0
** 0d8c 013c USB PnP Sound Device /dev/snd/controlC1 /dev/hidraw0

$ lsof /dev/snd/pcmC1D0c
pulseaudi 14545 username mem CHR 116,3 678 /dev/snd/pcmC1D0c
pulseaudi 14545 username 36u CHR 116,3 0t0 678 /dev/snd/pcmC1D0c

$ ps axv | grep 14545
14545 ? S<sl 0:05 186 40 2422663 21372 0.2 /usr/bin/pulseaudio --daemonize=no --log-target=journal

I am currently a bit confused where I probably find the second process of the resource/device for isolating it, so that the plughw statement can be issued. It is up to now unclear why I see two lines after the lsof statement in my case and what actions could follow on.

I would appreciate any helpful ideas on this matter.

Greetings.
Karl, DK7AL

Re: Winlink Error

karlanmitchell@... (Karlan Mitchell) — Fri, 11 Apr 2025 15:09:40 -0700

Okay, appreciate it.聽 Suspected it could be an issue because I did notice a delay and hang time on radio.聽 Was just throwing me off because I could clearly see messages coming through before winlink disconnected KISS.

聽

Got a digirig on the way now.

Re: Winlink Error

wb2osz@... (WB2OSZ) — Fri, 11 Apr 2025 12:32:11 -0700

The direwolf Radio Interface Guide 聽 https://github.com/wb2osz/direwolf-doc/blob/main/Radio-Interface-Guide.pdf聽 section 7.4 explains why you don't want to use VOX built in to the radio.聽

You need to use a different interface which provides the push-to-talk control to the radio.

聽

73,

John WB2OSZ

Winlink Error

karlanmitchell@... (Karlan Mitchell) — Fri, 11 Apr 2025 12:26:34 -0700

聽

Hey, I've spent a few hours looking for a solution to this,聽 Sound card is setup correctly, packets are being sent via VOX (uv-5r), stations are replying.聽 However it seems winlink is disconnecting without acknowledging the RX packets.聽聽

聽

Any ideas?聽 Is this most likely a winlink or direwolf setting?聽 Exactly the same behavior with "soundmodem.exe" program.

Surely I'm missing one simple setting somewhere.

聽

Thank you!

聽

-Karlan

AI5TS

Re: Multiple Radio Culprit

stevene1@... (Steven) — Thu, 10 Apr 2025 21:25:54 -0700

Thanks John.聽 I'm looking into that.

Re: Multiple Radio Culprit

stevene1@... (Steven) — Thu, 10 Apr 2025 21:25:25 -0700

No the sound cards don't have unique identifiers anywhere I can find.聽 I'm using a RPI4b.

Thanks for the advice.

聽