Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Direwolf
- Messages
Search
|
PTT via CAT
Hi to all!!!
I have an FT-991, an FT-897 and FT-817. The FT-991 have the built-in serial defunct (only the audio section is working) and I use an RS232 adapter connected to the DB-9 (GPS/CAT) connector on the rear. The other ones uses the original SCU-17 interface, that provide 2 Serials and the 2 audio devices.
Is there a solution to use the CAT with Direwolf (for APRS or packet) instead the RTS? |
|
Re: ISS digipeater functional?
This morning when ISS flew with elevation of nearly 60¡ã I heard nothing from them. The last couple of weeksI heard on 144.800 FM voice and SSTV signals and also often on 144.825 packet radio transmissons, but was not in a position to decipher them due to the lack of working interface. But now I have such and no signals can be heard from the guys in the sky. Maybe they have a lot of work to accomplish (EVA etc.) and therefore only a limited time for playing ham radio.
But I will try to look out for signals from them when time permits. Best regards. Karl, DK7AL |
|
Re: DW 1.8D & CM108: no input reaction
David,
both version of ADEVICE work alternatively well in the same manner while they express the same values: # ADEVICE plughw:CARD=Device,DEV=0 # ADEVICE plughw:1,0 I have seen that there is a sound mixer for my Gnome GUI and I simpy tried 'qasmixer', with that I've got a clear picture and understanding of my sound installation. In contrast 'alsamixer' gave me only a limited picture of my installation. And 'pavucontrol' was entirely not in a position to show relations of HW and SW, so I dropped it after experimenting. Attached you will find the 'qsmixer' settings of my installation. Thanks again and best regards. Karl, DK7AL |
|
Re: ISS digipeater functional?
¿ªÔÆÌåÓýIt's about the same time span since I last logged packets, too.? The digi is turned off for all manner of ISS activities such as docking operation and numerous station tasks including spacewalks. I've known it to be missing for much longer time spans than 11 days. NASA used to publish daily work schedules which listed when ham gear was being turned off (and back on again) but I can't find those schedules with a quick look online.Someone else suggested the gear is off because there may not be a ham onboard. I'm unaware of that ever being the case, given that the APRS digi is licenced as a remote (unattended) station by both US and Russian authorities. At least that's my understanding, but I'm happy to learn if I'm wrong. Ray VK2TV On 24/4/25 04:45, Rusty Travis via
groups.io wrote:
Greetings, does anyone have insight into the current status of the ISS digipeater? indicates the "Service Module radio" as configured and functional, yet the "Station List" at shows no traffic for the past 11+ days, nor have I heard anything here. The Kenwood TK-762GH radio with CM108 is both Tx/Rx on 145.825 MHz. |
|
Re: ISS digipeater functional?
¿ªÔÆÌåÓýThis is an interesting question because the? digipeater could be
turned off. Also, if the ISS doesn't have anyone onboard that's
licensed that could be another issue.
On 4/23/25 14:45, Rusty Travis via
groups.io wrote:
Greetings, does anyone have insight into the current status of the ISS digipeater? indicates the "Service Module radio" as configured and functional, yet the "Station List" at shows no traffic for the past 11+ days, nor have I heard anything here. The Kenwood TK-762GH radio with CM108 is both Tx/Rx on 145.825 MHz. |
|
ISS digipeater functional?
¿ªÔÆÌåÓýGreetings, does anyone have insight into the current status of the ISS digipeater? indicates the "Service Module radio" as configured and functional, yet the "Station List" at shows no traffic for the past 11+ days, nor have I heard anything here. The Kenwood TK-762GH radio with CM108 is both Tx/Rx on 145.825 MHz.I thought direwolf 1.8D might be malfunctioning, but it works properly on 144.390 MHz. Can anyone verify ISS digipeater functionality, please? |
|
Re: DW 1.8D & CM108: no input reaction
¿ªÔÆÌåÓýGood to hear you got it working.? Just to clarify, what ADEVICE are you using in your direwolf.conf?? Also, any specific reason why you used qasmixer?? I had never heard of it before and had to look it up. --David KI6ZHD On 04/23/2025 12:16 AM, DK7AL wrote:
David, I've got it working this morning with some fine tuning the input level with the help of Qasmixer under my Gnome GUI. It was far too loud and had to be drastically reduced to get a response, after that I tuned the audio level in my CM108 interface and in the mixer accordingly, so that I have now a wider range in the mixer to optimize the incoming sound level. However, it was OK in principal in the HW secton, but had to be adjusted as briefly explained with helpful upcoming feedback from the system. Thank you for your efforts. Greetings. Karl, DK7AL |
|
Re: Direwolf cannot decodify APRS from AnyTone AT878UVII-Plus
#scu-17
#usb-codec
#ft-847
#direwolf
#linux
Hi Marc,
?
obviously I know the 6-pin DIN PKT connector is used for FM data but the DATA IN/OUT connected jack doesn't disturb although it isn't used in this case. I only quoted for additional information.
?
But the issue comes from AnyTone as next I tell:
?
Recently in a spanish AnyTone group several we users meet that we're suffering APRS-A issues like losing packets (until 60%) and not only Direwolf is unable to receive APRS-A packets from AT nor another digipeaters. Someone points out due to last firmwares (maybe from 3.01 to 3.06). Maybe in the next 3.07 release could be fixed.
?
Also I tried with another HT with OpenGD77 firmware and APRS-A TX capabilites and Direwolf can receive and decodify APRS-A frames succesfully.?
?
So I can say that my Yaesu FT-847 configuration is working fine.
?
When the new AT firmware release be published I'll try again.
?
Thanks. Regards.
|
|
Re: DW 1.8D & CM108: no input reaction
David,
I've got it working this morning with some fine tuning the input level with the help of Qasmixer under my Gnome GUI. It was far too loud and had to be drastically reduced to get a response, after that I tuned the audio level in my CM108 interface and in the mixer accordingly, so that I have now a wider range in the mixer to optimize the incoming sound level. However, it was OK in principal in the HW secton, but had to be adjusted as briefly explained with helpful upcoming feedback from the system. Thank you for your efforts. Greetings. Karl, DK7AL |
|
Re: DW 1.8D & CM108: no input reaction
David,
here are some short answers to your requests. a) Squelch: is wide open, the audio signal can be traced directly at pin #27 of CM108 with more than 100mVpp b) Output from 'uname -a' Linux kalli 5.15.0-136-generic #147~20.04.1-Ubuntu SMP Wed Mar 19 16:13:14 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux c) Output from 'aplay -l' **** Liste der Hardware-Ger?te (PLAYBACK) **** Karte 0: PCH [HDA Intel PCH], Ger?t 0: ALC887-VD Analog [ALC887-VD Analog] Sub-Ger?te: 0/1 Sub-Ger?t #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Ger?t 1: ALC887-VD Digital [ALC887-VD Digital] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 Karte 1: Device [USB PnP Sound Device], Ger?t 0: USB Audio [USB Audio] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 Karte 2: HDMI [HDA ATI HDMI], Ger?t 3: HDMI 0 [HDMI 0] Sub-Ger?te: 0/1 Sub-Ger?t #0: subdevice #0 Karte 2: HDMI [HDA ATI HDMI], Ger?t 7: HDMI 1 [HDMI 1] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 Karte 2: HDMI [HDA ATI HDMI], Ger?t 8: HDMI 2 [HDMI 2] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 Karte 2: HDMI [HDA ATI HDMI], Ger?t 9: HDMI 3 [HDMI 3] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 Karte 2: HDMI [HDA ATI HDMI], Ger?t 10: HDMI 4 [HDMI 4] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 Karte 2: HDMI [HDA ATI HDMI], Ger?t 11: HDMI 5 [HDMI 5] Sub-Ger?te: 1/1 Sub-Ger?t #0: subdevice #0 d) ADEVICE configurtion as 'default' does not work, but the following one works for transmission, but not for reception ADEVICE plughw:CARD=Device,DEV=0 (channel 0) e) How to proceed with 'pavucontrol' in connection with PDF document on page #63 is up to now unclear. Will be checked and reported in the next couple of minutes/hours. In any case - thanks for your swift response. Greetings. Karl, DK7AL |
|
APRS and Digipeting
#digipeter
#aprs
#direwolf
I set up a raspberry pi 3 with Direwolf. It's uses a Baofeng Uv-R5 and aprs cable and usb sound card. They all work and settings are correct for everything.
Everything seems to be working. I can see beacons the iGate sends out over the air. I can sms back and forth with it but it seems that my igate cannot send outgoing messages it receives from APRS-IS and digipeat them out into the air. Maybe I'm missing something? Below is a small portion of my log. I see a lot of [ig>tx] but nothing confirming packets were sent out. What more can I learn? ?
Thanks Fellas & Gals! [ig>tx] SMS>APOSMS,TCPIP*,qAC,WA7BF::K9JPT-9 ?:@8454182603 Jyv?skyl? jutting{2141
Was message addressee K9JPT-9 heard in the past 60 minutes, with 1 or fewer digipeater hops? Yes, K9JPT-9 last heard over radio 0 minutes ago, 0 digipeater hops. Was message source SMS heard in the past 1 minutes, with 0 or fewer digipeater hops? No, we have not heard SMS over the radio. ig_to_tx_allow? ch0 60605 "SMS>APOSMS::K9JPT-9 ?:@8454182603 Jyv?skyl? jutting{2141" ig_to_tx_allow? YES ig_to_tx_remember [2] = ch0 d0 1745271633 60605 "SMS>APOSMS::K9JPT-9 ?:@8454182603 Jyv?skyl? jutting{2141" [0L 2025-04-21 17:40:33] K9JPT-10>APDW16,WIDE1-1:}SMS>APOSMS,TCPIP,K9JPT-10*::K9JPT-9 ?:@8454182603 Jyv?skyl? jutting{2141 [ig>tx] KB1JGI>APBM1D,KB1JGI,DMR*,qAR,KB1JGI:@214036h4135.70N/07328.92WR159/000Fred
K9JPT-9 audio level = 25(7/8) ? [NONE] ? |||||||__
[0.3 2025-04-21 17:40:38] K9JPT-9>APK004,WIDE1-1,WIDE2-1::SMS ? ? ?:ack2141<0x0d> ACK message 2141 ?for "SMS", normal car (side view), Kenwood TH-D74 Rx IGate: Truncated information part at CR. rx_to_ig_allow? 36780 "K9JPT-9>APK004::SMS ? ? ?:ack2141" rx_to_ig_allow? YES, no dedupe checking [rx>ig] K9JPT-9>APK004,WIDE1-1,WIDE2-1,qAR,K9JPT-10::SMS ? ? ?:ack2141 [ig>tx] KM6FDI-9>APDR16,TCPIP*,qAC,T2GB:=4131.04N/07410.80Wu090/059/A=000334 Conference KM6FDI-14
[rx>ig] # [ig>tx] WB2ZII-13>APRS,WIDE2-2,qAR,W2MEB-10:!4119. ?N/07333. ?W#PHG7530 ?fill-in digipeater www.weca.org
[ig>tx] SMS>APOSMS,TCPIP*,qAC,WA7BF:!4024.51N/14943.02W$SMS Gateway (US, Canada, Australia & UK ONLY) - NA7Q
Special case, allow position from message sender SMS, 0 remaining. ig_to_tx_allow? ch0 25131 "SMS>APOSMS:!4024.51N/14943.02W$SMS Gateway (US, Canada, Australia & UK ONLY) - NA7Q" Tx IGate: Already transmitted maximum of 1 packets in 1 minute. [ig>tx] KM6FDI-9>APDR16,TCPIP*,qAC,T2GB:=4130.98N/07409.98Wu105/063/A=000295 Conference KM6FDI-14
[rx>ig] # [rx>ig] # [ig>tx] KM6FDI-9>APDR16,TCPIP*,qAC,T2GB:=4130.71N/07408.67Wu091/061/A=000332 Conference KM6FDI-14
[rx>ig] # [rx>ig] # |
|
Re: Direwolf Decode Help
¿ªÔÆÌåÓýThough somewhat off-topic, I wouldn't recommend to troubleshoot Direwolf input audio level issues with the very old Thomas Sailer soundmodem soft-TNC (not to be confused with the UZ7HO soundmodem for Windows).? Yes, the Linux soundmodem's "Spectrum Display" and maybe the GUI config were nice but everything else is *very* outperformed by Direwolf in all respects these days. --David KI6ZHD On 04/20/2025 04:18 PM, Marc Champagne
- W1MJC via groups.io wrote:
|
|
Re: DW 1.8D & CM108: no input reaction
¿ªÔÆÌåÓýOk, with seeing the trailing zero in "receive audio level CH0 0" means no audio is being routed to Direwolf.? In the beginning of this thread, you mentioned you're running Linux. ?? - Make sure that the squelch on your radio is wide open ?? - Which Distro and version? If your Linux distro doesn't have a GUI: ?? - Please send us the output of "aplay -l" to see what sound devices are recognized.? You currently have Direwolf configured as "plughw:CARD=Device,DEV=0? (channel 0)" but we need to confirm that's correct.? Once you get this corrected, you need to see some received audio level here.? Your goal should be to get an average report around 50 but you'll find a lot of variability here on remote stations.? Do your best and just leave it as Direwolf is very tolerant. If you're running a Linux distro with a GUI: ?? - You most likely have Pipewire or PulseAudio running.? That's fine but you need do a few more things: ????? 1. Configure the direwolf.conf ADEVICE line to use the device "default" ????? 2. Install the "pavucontrol" program and configure it per PDF page 63 .? You will need to change both the "playback" and "Record" tabs to route Direwolf to the correct sound device.? Setting the playback routing is typically easiest to use the Direwolf calibrate command line option to constantly transmit instead of waiting for a beacon to play. --David KI6ZHD On 04/21/2025 05:54 AM, DK7AL wrote:
John, thank you for this (-a 10) trick. The output is always: ADEVICE0: Sample rate approx. 44.1 k, 0 errors, receive audio level CH0 0 Best regards. Karl, DK7AL |
|
Re: Using Direwolf to emulate a host mode TNC
That is a great explanation Chris. Yes WA8DED and the better TF2.7b
still handles the AX.25 stack, but allows the application to select multiple connections at once via streams. You can still establish a connection as a human operator by "ESC I YUORCALL CR" (that defines your callsign). Then "ESC S 1 CR" That selects a stream other than the default UI stream. Then "ESC C W6TST" to connect. You then can move on to new streams and have several connections at once. This is holstmode behavior in a nutshell. It is straightforward to setup LinFBB BBS with a hostmode TNC. It avoids the Linux Kernel stack which has been an issue up until very recently. Having hostmode in direwolf would future proof a AX.25 stack for older software (that maybe still maintained but no new features) like FBB. Still the most killer packet terminal (by a stretch) is WinPack 6.80, but the author destroyed his sources before he passed away. Vista is the last OS it will run on. It works with a hostmode TNC. I run WinXP in VirtualBox to play with it. But it would be cool if direwolf had this built in stack TNC. I have TFKISS running in Linux now (only works in 32bit), and it provides this functionality as a separate program. It basically takes a KISS connection from something like Direwolf and provides a hostmode connection on the other side -- thus emulating a DED promed TNC. -Chris KQ6UP On Mon, Apr 21, 2025 at 7:24?AM WB2OSZ via groups.io <wb2osz@...> wrote:
-- Thanks, Chris Maness |
|
Re: Using Direwolf to emulate a host mode TNC
This thread was started a long time ago? but has some recent activity.
?
On Fri, Sep 16, 2016 at 03:46 PM, John Huggins wrote:
As I understand it, DireWolf doesn't perform any hostmode functions and perhaps never should.? If true, is there a program that can run in the Linux regime to perform just the host AX.25 management functions plus serve as go-between the DireWolf modem and the network port/BPQ32? The original TAPR TNC was designed for a human operator sitting at a? dumb terminal.??Text going to the TNC could be either a command to the TNC or text to be transmitted.
Text coming from the TNC could be a response to a command, monitored data, data received from connected station, or status such as the other station disconnected.?
?
Once people started writing applications, to talk to the TNC, it became very clear this was a very bad interface for computer application.? Everything was jumbled together in a single text stream rather than separating command, status, and different types of data.
?
One approach taken was KISS.? The TNC just shoveled packets back and forth without adding any intelligence.? The higher level processing was done in the computer.? For the connection oriented protocol to work well, it needs to know about:
- Channel status (i.e. data carrier detect from the modem & whether transmitter is on.)
- Length of the transmit packet queue.
?
Among other topics, I rambled on about why using KISS for connected mode packet is a really bad idea here: ?
?
The WA8DED Host Mode keeps the keeps the connection oriented protocol processing in the TNC, where it has information about channel and transmit queue status.? (Back then they referred to it as the AX.25 Link level but nowadays we would call it the Transport layer.)? A new interface was provided which separated the commands, status, and different types of data, making it more appropriate for use by a computer application.
?
direwolf implements the AX.25 connection oriented protocol.? As an extra bonus, it implements AX.25 version 2.2 (1998) while most others are still using the less efficient version 2.0 (1984).? This is accessible by the AGW protocol over TCP.? From the documentation, it looks like BPQ32 can talk to a TNC using AGW protocol.? You should be able to use:
?
[RADIO]---audio---[R-Pi:DireWolf/AGW]---TCP---[PC:Linux&BPQ32]
?
?
73,
John WB2OSZ
? |
|
Re: Direwolf Decode Help
It sounds like both the softmodem (direwolf) configuration and audio path are suspect at this point.
?
Maybe try the kernal soundmodem module instead of direwolf and see if it decodes packets?? ?If it does....maybe you're there (and fix the direwolf config or not).? ? If it doesn't, maybe look at the audio path some more?
?
Commands would be:
modprobe mkiss
soundmodem -c PTT -v 2
?
/etc/ax25/soundmodem.conf (i have this.? ?something similar...)
<modem> ?<configuration name="CAT"> ???<chaccess txdelay="150" slottime="100" ppersist="40" fulldup="0" txtail="10"/> ???<audio type="alsa" device="plughw:3,0" halfdup="1" capturechannelmode="Mono"/> ???<ptt file="/dev/ttyUSB0" hamlib_model="1001" hamlib_params=""/> ???<channel name="Channel 0"> ?????<mod mode="afsk" bps="1200" f0="1200" f1="2200" diffenc="1"/> ?????<demod mode="afsk" bps="1200" f0="1200" f1="2200" diffdec="1"/> ?????<pkt mode="MKISS" ifname="sm0" hwaddr="W1MJC-5" /> ???</channel> ?</configuration> ?<configuration name="PTT"> ???<chaccess txdelay="150" slottime="100" ppersist="40" fulldup="0" txtail="10"/> ???<audio type="alsa" device="plughw:3,0" halfdup="1" capturechannelmode="Mono"/> ???<ptt file="/dev/ttyUSB1" gpio="0" hamlib_model="" hamlib_params=""/> ???<channel name="Channel 0"> ?????<mod mode="afsk" bps="1200" f0="1200" f1="2200" diffenc="1"/> ?????<demod mode="afsk" bps="1200" f0="1200" f1="2200" diffdec="1"/> ?????<pkt mode="MKISS" ifname="sm0" hwaddr="W1MJC-5" /> ???</channel> ?</configuration> </modem> /etc/axports (i have this.? ?something similar.....)
sm0 ????W1MJC-5 ????????0 ??????128 ????4 ??????KPC-9612+ defaults sm1 ????W1MJC-6 ????????0 ??????128 ????4 ??????KPC-9612+ defaults ?
If getting a physical TNC is an option......that'd let you eliminate direwolf (or soundmodem) configuration problems as a factor.
?
? |
|
Re: Direwolf cannot decodify APRS from AnyTone AT878UVII-Plus
#scu-17
#usb-codec
#ft-847
#direwolf
#linux
I believe this is your problem. I? also use an FT-847 for packet....with audio to/from the 6-pin DIN PKT connector.....not the Data IN/OUT phono. ?
The DIN jack must be used for FM data.? ?The Data jack is for SSB modes (although the DIN jack works just fine for those too).? ? But the Data jack for FM data won't work (page 56/57 of the manual). |
|
Re: Using Direwolf to emulate a host mode TNC
I'm probably missing something here, but are you looking for 'kissattach' here ..... which reads from the the direwolf pty (if launched with -p) and creates the network interface you specified in axports?
?
?
?
On Fri, Sep 16, 2016 at 03:46 PM, John Huggins wrote:
As I understand it, DireWolf doesn't perform any hostmode functions and perhaps never should.? If true, is there a program that can run in the Linux regime to perform just the host AX.25 management functions plus serve as go-between the DireWolf modem and the network port/BPQ32? |
to navigate to use esc to dismiss