开云体育

I know this is a busy group so thank you for reading this. It's been quite some time since I've played with packet radio so I've probably overlooked something obvious. When I last used my Yaesu radio ADEVICE plughw:1,0 (in the direwolf config file) worked perfectly. Now I want to use SDRconnect instead, just to receive. arecord -l **** List of CAPTURE Hardware Devices **** card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0 and device 0 look like the correct device (ADEVICE plughw:0,0) but direwolf returns: Reading config file /home/phil/direwolf.conf Audio device for both receive and transmit: plughw:0,0 (channel 0) Could not open audio device plughw:0,0 for input Device or resource busy This is what the audio mixer reports under the playback tab: ALSA plugin [SDRconnect]: ALSA Playback on What setting should I be using to have direwolf listen to the output (the speaker) from SDRconnect? -- Regards, Phil

I am at my witts end. I have been trying to use my Nooelec SDR with direwolf and direwolf does not "see" it and place it in the list. I have teied all releases from 1.5 to 1.7 to see if there is a difference.

Hi, I think I just successfully built and installed Direwolf on my Mac, following the instructions in the user guide. According to the guide, to run direwolf, I just need to run /usr/local/bin/direwolf from my home directory. I do that but nothing seems to start running since direwolf does not seem to exist in /usr/local/bin. I do see dw-start.sh in my home directory but running that, I get the following Direwolf in GUI mode start up DISPLAY=:0 Did not find an X terminal emulator. Reverting to CLI mode ----------------------- Direwolf in CLI mode start up No Sockets found in /var/folders/t9/g9sttp414nl_hx76sr642l000000gn/T/.screen. I'm stuck now. Any help and tips would be appreciated. Thank you, Sepehr N6IRN

Kind of asking John WB2OSZ What please is the significance of? // Originally 40. Version 1.2, try 10 for lower latency. #define ONE_BUF_TIME 10 in audio.c (also in the portaudio and windows audio code) Reason I ask is that I have used pulseaudio under direwolf for years that has seen on average 1 in 10 TX packets audio buffer underruns. Changing this from 10 to 40 (Along with some other buffering and CPU speed changes) seems to have resolved them. Yes I am aware that pulseaudio is not good with direwolf, but I am stuck with it. With these changes I am not having any TX>RX delay problems that stop decoding of the next 1200AFSK packet. Cheers Bob VK2YQA

I have spent quite a while trying to figure out why I cant get direwolf to connect to any AX.25 nodes. It starts up fine and sees APRS traffic but if I try to send by packet in Winlink or connect to a BBS the connection never gets established. The radio is an Icom 9700 and I am connecting via USB using COM5 and RTS. The OS is windows 11. I am using the built USB audio codecs. The Kiss interface is started and I can connect to it (port 8001 on 127.0.0.1) but when I try to connect to a node I get a few transmissions with a "connecting to VA7QBE-10" and then a few seconds later "disconnect reported". Here is what the interface log shows Ready to accept KISS TCP client application 1 on port 8001 ... KISS protocol set Persistence = 160, chan 0 KISS protocol set SlotTime = 30 (*10mS units = 300 mS), chan 0 KISS protocol set TXDELAY = 40 (*10mS units = 400 mS), chan 0 KISS protocol set FullDuplex = 0, chan 0 [0L] VE7JFZ>VA7QBE-10:(SABM cmd, p=1) [0L] VE7JFZ>VA7QBE-10:(SABM cmd, p=1) [0L] VE7JFZ>VA7QBE-10:(SABM cmd, p=1) [0L] VE7JFZ>VA7QBE-10:(SABM cmd, p=1) [0L] VE7JFZ>VA7QBE-10:(SABM cmd, p=1) KISS client application 0 on TCP port 8001 has gone away. It doesnt matter which winlink server I pick it is always the same. As a note I can get WSJTZ to use the radio no problem with same com port settings.

I am working on bringing up an APRS bot and I am having some troubles. Originally I was running Direwolf 1.6 and was having problems getting packets from the APRS-IS connection to be seen by the KISS client. This evening I compiled Direwolf 1.7 and used the ICHANNEL statement. Now I am getting packets from the APRS-IS connection routed over the KISS connection. That is the good news. The bad news is that the packets are being received as third party packets and I can not find any references to how packets should be sent over the KISS connection so that the reply packet gets routed back over the KISS connection. So on the APRS-IS feed, I am seeing the packet come across as WT0F-4>APDR16,TCPIP*,qAC,T2PRT::APRSFL :Test{14 Then on the KISS client, I am seeing the packet come across as X*>X*:}WT0F-4>APDR16,TCPIP*,qAC,T2PRT::APRSFL :Test{14 The response that the client sends back (ACK) is (or close it is as I did not have it handy) APRSFL>APZIOR,WIDE1-1::WT0F-4 :ACK{14 This packet goes out the RF interface instead of the APRS-IS connection. So the question is do I need to prepend the packet with X*>X*:} or X>X:} ? Is there any good documentation on how to properly handle third party packets? Thanks. -- Gerard Hickey / WT?F IRLP:3067/Echolink:529661 hickey@... DMR: 3102272 425-395-4554 Allstar: 531920 MeshPhone: 386-8611

I saw in several previous posts that an issue arises when Direwolf v 1.7 is tried on the latest Bookworm Update. I haven't seen any recent posts, and didn't find an definitive "fix", so I thought I'd give updating Bookwork on a test platform (previously working with 1.7 & Bookworm). Sure enough it failed. Error writing "27" to /sys/class/gpio/export, errno=22 Invalid argument What is the best correction? Is it simply to download the latest Dev version? I'm not in any rush, so I thought I'd wait for somewhat stable solutions. Arnold, KQ6DI

Good evening all. When setting the parameters in the direwolf.conf file for PBeacon, specifically the PHG, is the antenna gain specified in dBi or dBd? Thanks and 73 Tim KB2MFS

The info about smartbeaconing on 9.11.5 - p121 http://www.hamhud.net/hh2/smartbeacon.html http://info.aprs.net/index.php?title=SmartBeaconing The first goes somewhere unrelated The second is deadlink. Cheers Bob VK2YQA

Have been going through the docs on this and now decoding quite weak/noisy signals, quite interesting. Want to make sure I have covered everything else that "may not be documented". Most of the 14105 chatter here is marginal. Using latest 1.8. I haven't found an understandable explanation on the term "slicers" yet. I am using the older format; MODEM 300 1600:1800 B- 5@30 /1 ie what are the merits of using (say) B+ or even A+ instead. I see 9 "modems" on the log display with that (eg ___||||__). Has there been new modem development since 1.7? Might be nice to see a list of current modems (and summary) available. FX25 and "FIX_BITS 1 AX25" also works well. Seeing quite a few recoveries. Am TXing 16. Am wondering how important audio input level setting (and even sampling division rate) is in regard to quantisation errors and dynamic range. If so is there a debug option that shows the occupied bit width, or is this what "audio level" actually logs? Cheers Bob VK2YQA

I have an ICOM 9700 connected with a USB cable. I setup direwolf per the instructions for CM108. I tried to test my configuration with direwolf -x a and got the following message. ** Reading config file direwolf.conf Available audio input devices for receive (*=selected): * 0: Microphone (USB Audio CODEC ) (channel 0) 1: Microphone Array (Realtek(R) Au Available audio output devices for transmit (*=selected): * 0: Speakers (USB Audio CODEC ) (channel 0) 1: Speakers (Realtek(R) Audio) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate. Using \\?\hid#vid_08bb&pid_2901&mi_03#9&10faddb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control. Write failed to \\?\hid#vid_08bb&pid_2901&mi_03#9&10faddb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} ERROR: PTT for channel 0 has failed. See User Guide for troubleshooting tips. Sending alternating mark/space calibration tones (1200/2200Hz) on channel 0. Press control-C to terminate. Write failed to \\?\hid#vid_08bb&pid_2901&mi_03#9&10faddb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} ERROR: *** The output from CM108 is as follows *** D:\Radio\direwolf-1.7.0-9807304_i686>cm108 D:\Radio\direwolf-1.7.0-9807304_i686>cm108 VID PID Product HID [ptt] --- --- ------- --------- 046d c05a USB Optical Mouse \\?\hid#vid_046d&pid_c05a#7&125ea53a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} deed feed Acer Airplane Mode Controller \\?\hid#10251229#3&9d5d338&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col01#4&22d87139&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col02#4&22d87139&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col03#4&22d87139&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col04#4&22d87139&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 08bb 2901 USB Audio CODEC \\?\hid#vid_08bb&pid_2901&mi_03#9&10faddb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} ** = Can use Audio Adapter GPIO for PTT. VID PID Product HID [ptt] --- --- ------- --------- 046d c05a USB Optical Mouse \\?\hid#vid_046d&pid_c05a#7&125ea53a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} deed feed Acer Airplane Mode Controller \\?\hid#10251229#3&9d5d338&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col01#4&22d87139&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col02#4&22d87139&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col03#4&22d87139&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 06cb cd41 HIDI2C Device \\?\hid#syna7db5&col04#4&22d87139&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 08bb 2901 USB Audio CODEC \\?\hid#vid_08bb&pid_2901&mi_03#9&10faddb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} ** = Can use Audio Adapter GPIO for PTT. ** If I run direwolf without the -x a options I get no error messages.

I have had a great experience with direwolf for the most part so far, and I understand this is open source software maintained by volunteers so I am not complaining. Having said that I have had some issues with "connected mode" ax25 operations. For example, I can reach stations, but said stations will not connect and/or stay connected. this is unfortunately preventing me from using winlink via PAT and using paracon to connect to PBBS nodes/servers. pat and paracon use the direwolf agwpe server so I also attempted to use the built in ax25 stack and that worked but only a couple times out of many connection tries to PBBS servers/nodes APRS and "non-connected" messaging is working wonderfully however and for that I am of course very grateful. So am I the only one who has had these issues recently? Also, I know troubleshooting is much easier with more info, so here is my setup: Arch linux kernel version: ```6.12.4-arch1-1``` Dire Wolf version 1.7 ptt/input soundcard: digirig mobile pipewire-pulse is my audio "server" I'm using pavucontrol to monitor input audio levels Once again, it is decoding on aprs and some messages from the PBBS servers, but not maintaining Connections. Also, attached is my direwolf config: # direwolf.conf of KK7WXH Thank you all for your help, KK7WXH!

I'm having an issue with getting data to send with Direwolf 1.7 on a Raspberry Pi with Bookworm. It can receive fine and PTT activates when a message should be sent but it's only the carrier and no data. All of the volume settings are correct but the speaker volume is forced to zero, I don't know if this is supposed to be happening because I couldn't find anything about it in the documentation but I could have missed it. Any help would be greatly appreciated. I am also quite new to all of this so feel free to explain as much as possible. Thank you, Grayson

I'd like to configure direwolf to digi repeat like a packet repeater interfaced to a transceiver tuned to a packet frequency. Can direwolf be configured to do this? If so, please point me in the that direction. 73, VE3ECI Greg

Starting over fixed it. I don't know what I missed the first time, but it is running perfectly now. I should have tried that a couple days ago... Arnold, KQ6DI On 12/09/2024 3:33 PM PST ARNOLD HARDING <kq6di@...> wrote: I have a Pi 3A, 3B, 3B+ all running Bookworm and Direwolf 1.8, and all work fine. It's only this attempt at another 3B giving me issues, so something odd happened. I think my best option is to re-format the SD Card, and start over at the point of loading the OS. It seems like a better option than fighting what might be missing... Arnold, KQ6DI _

I have Direwolf working in a Pi 3B, and I am unable to have the sound devices volumes get properly restored after a reboot. It receives fine, and transmits fine, and I can adjust volumes easily using alsamixer, but on the next power-up, all of the volumes need to get re-adjusted again. I can use sudo alsactl store 1 (or no channel, or 2 or 3) and the next power-up the sound devices are messed up yet again. I'm using a usual CM108 sound card, so nothing unusual. It should be easy, but I haven't seen the clue as to what yet. Thanks. Arnold, KQ6DI

I think I lost an instruction... How do I compile Direwolf version 1.8 - for Bookworm? I think I lost the proper step for git checkout dev ? I've done this before and it wasn't difficult, but now ??? I lost some step. Thanks, Arnold, KQ6DI