Transmit using direwolf with multiple channels

13 views
Skip to first unread message

Matt

unread,
Aug 25, 2024, 6:18:26 PM8/25/24
to qthapp-users
I added a second audio device/radio/channel to the direwolf config that I use for APRS. Now I get the message below in direwolf when attempting to beacon from QTH.app, and the beacon is not successfully sent.

I am using different KISS ports for different direwolf channels, so channel 0 is port 8001 and channel 2 is port 8003. Both channels are set up as mono audio devices, which is why the numbering is that way (see Dire Wolf User Guide).

Has this behavior been observed before?

Thanks,
Matt W1CDN

<<< Data frame from KISS client application, channel 0, total length = 77
000: 00 82 a0 a2 a8 90 62 e0 ae 62 86 88 9c 40 64 ae ......b..b...@d.
010: 92 88 8a 64 40 63 03 f0 40 32 32 30 36 35 39 68 ...d@c..@220659h
020: 34 37 35 36 2e 34 38 4e 2f 30 39 37 30 31 2e 36 4756.48N/09701.6
030: 31 57 2d 4c 65 61 76 65 20 61 20 6d 65 73 73 61 1W-Leave a messa
040: 67 65 20 74 6f 20 73 61 79 20 68 69 21 ge to say hi!
[ig] W1CDN-1>APDW17:!4756.49NI09701.62W#PHG5000Digipeater and two-way iGate
[0L 17:07:04] W1CDN-1>APDW17,WIDE1-1:!4756.49NI09701.62W#PHG5000Digipeater and two-way iGate
Invalid transmit channel 1 from KISS client app.

Are you using AX.25 for Linux? It might be trying to use a modified
version of KISS which uses the channel field differently than the
original KISS protocol specification. The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1
Reply all
Reply to author
Forward
0 new messages