¿ªÔÆÌåÓý

Date   
Direwolf audio device issue with FT-847 and SCU-17 6 #linux #scu-17 #ft-847 #sound #usb-codec
Hello all, first of all thanks for accept me in the group. I'm introducing into direwolf and I'm configuring my ~/direwolf.conf file to testing it. My transceiver is a Yaesu FT-847 connected to SCU-17 interface. I can work in HF modes succesfully but with direwolf I'm having trouble with the audio device. Next my configurations: $ arecord -l **** List of CAPTURE Hardware Devices **** card 0: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ cat ~/direwolf.conf ADEVICE plughw:0,0 CHANNEL 0 MYCALL N0CALL MODEM 1200 PTT /dev/ttyUSB1 RTS AGWPORT 8000 KISSPORT 8001 IGTXLIMIT 6 10 # Parameters for VHF FX25TX 1 RETRY 5 FRACK 3 MAXFRAME 7 EMAXFRAME 14 PACLEN 128 DWAIT 0 TXDELAY 25 TXTAIL 15 MAXV22 2 FULLDUP OFF --- I have a HT next to me to test the 847 signals and both tuned in the same frequency. I'm testing with "direwolf -x a" command and it happens: - With "ADEVICE plughw:0,0": the 847 does PTT fine, I can see the transceiver alternating TX but the HT doesn't receive anything - With "ADEVICE plughw:2,0": the 847 does PTT fine, I can see the transceiver alternating TX, I can hear the sound through the computer speakers and the HT is receiving the signal. I can't understand this strange behaviour ... Any help will be appreciated. Thanks.
Started by V¨ªctor J. S¨¢nchez @ · Most recent @
Airband-Direwolf-APRS configuration 3
As requested. I've been running RTLSDR_Airband from the day I found out about it. I was trying to write code for a multi-channel FM receiver and it was proving quite difficult, and I dropped the effort once I found out about it. It uses a very efficient algorithm mix and filter multiple frequencies to baseband RF, where AM and FM demodulation can be applied. FM demodulation is very efficient as well. On my Raspberry Pi I'm running 10 channels at present, with 4 recording audio from repeater outputs, 4 recording baseband RF from repeater inputs, and 2 FM audio channels piped into Direwolf. This consumes about 10% of one of the 4 processor cores on a Raspberry Pi 4. It is supposed to work on a Raspberry Pi 2 and Pi 3, using the on-board GPU to accelerate computation, but I've never tried it. It is also quite reliable, and I've had it running over a month at a time on the Pi. The reason I was doing this was to hunt a repeater jammer in the area, and APRS was an afterthought. The jammer is now gone but new ones come from time to time so I record 4 repeaters 24 hours/day. The audio recordings are used for evidence, and the IQ recordings for analysis, especially experimentally with transmitter profiling. Experience using Direwolf made it obvious it would be a good fit - and it almost was. I now have about 40 GB of recordings. I also encouraged some fellow club members to run similar setups and devised a method by which they could upload their recordings to my system, making them all available for review or analysis. It still has some rough edges but basically works. The most difficult thing is managing security. I called the system Dragnet, which if you look at the files you'll see this as the user account for the programs. The biggest issue I had, which I was dealing with today, was that Airband emits 32-bit floating point samples and Direwolf wants 8 bit unsigned or 16 bit signed integers. There are programs that would do the conversion but they are rather complex, so I decided to write one for the purpose to act as an intermediary between Airband and Direwolf. Initially I tried reading from Airband using an Internet socket, and writing to a socket for Direwolf to read but I ran into difficulties and just wrote the output to stdout and piped it into Direwolf. That worked well for APRS traffic on 144.390 and a couple of weeks ago I added the ISS APRS RS0ISS as a second channel. Yesterday I checked the logs and found that I was receiving the ISS about once per day with several transmissions during the pass and was pleased. I started thinking that because I had two instances of Direwolf I would have 2 igate connections and thought that wasteful, so I decided to pursue the socket to socket sample format conversion again. This time I used Microsoft Copilot which sped things up a lot. The last thing I asked Copilot to do was add GPL V3 terms and conditions to make the code open source. After much back and forth I now have a version which will forward samples to another socket or to stdin based on the command line options. I wrote simple system services for airband, the two instances of the format converter (Terrestrial and ISS APRS) and one instance of Direwolf. It's all running nicely as I write. The main components are Configuration files for airband and Direwolf Systemctl .service files for the 4 system services. The sample converter code, which I called f32_i16.c due to lack of imagination (maybe I should call it AirWolf) I'm happy to share all of it and will post some stuff in the replies. Use at your own risk of course.
Started by Chris VE3NRT @ · Most recent @
f32_i16.c 2
Compilation is: gcc f32_i16.c -o f32_i16 -lm You can find the code at https://github.com/SullivanChrisJ/AirWolf.git I run it as a system service with the following .service file (installed in /etc/systemd/system, with $ sudo systemctl enable --now f32_i16_1.service. One of these is needed for each of the channels. Service file would be something like. It could probably be improved. [Unit] Description=Sample conversion for Direwolf Instance #1 Wants=network.target After=network.target [Service] Type=simple ExecStart=/bin/sh -c '/usr/local/bin/f32_i16 7355 7455' WorkingDirectory=/home/dragnet Restart=no User=dragnet [Install] WantedBy=multi-user.target Sample for airband.service [Unit] Description=SDR AM/NFM demodulator Documentation=https://github.com/charlie-foxtrot/RTLSDR-Airband/wiki Wants=network.target After=network.target # Dependencies: # RTLSDR-Airband binary is assumed to be in /usr/local/bin # The configuration file is assumed to be in /usr/local/etc/rtl_airband.conf [Service] Type=simple ExecStart=/usr/local/bin/rtl_airband -Fe -c /usr/local/etc/rtl_airband.conf WorkingDirectory=/mnt/sftp/ve3nrt # Bumping the dongle sometimes causes a read failure which will cause the program # to exit. Tell it to restart, with a small delay in case of presistent failure. Restart=always RestartSec=60 User=ve3nrt [Install] WantedBy=multi-user.target Sample for aprs.service (direwolf). You will need to create the airband directory in /var/log with permissions the program can access, or put the file somewhere else. [Unit] Description=AX.25 APRS Packet Monitor on port 7455 & 7456 Wants=network.target After=network.target [Service] Type=simple ExecStart=/bin/sh -c '/usr/local/bin/direwolf -t 0 -c /usr/local/etc/aprs.conf >> /var/log/airband/aprs.log' WorkingDirectory=/home/dragnet Restart=no User=dragnet [Install] WantedBy=multi-user.target
Started by Chris VE3NRT @ · Most recent @
Sample rate ignored when using UDP audio input? 3
I've been using RTLSDR_Airband with Direwolf for APRS for some time now. Originally I tried converting the socket output from Airband from f32 to i16 and sending the output to another socket for Direwolf to read, but couldn't get it to work. I abandoned that idea and sent the converted output to stdout instead and it worked perfectly. Recently though, I added the ISS to my receive list in Airband, and that worked nicely as well, and I pick it up every day or so. I I though it would be nice to use 1 Direwolf instance to handle both APRS sources, so I have resumed work on socket output from the conversion program and socket input to Direwolf. I now have it to the point where the Direwolf opens the socket successfully and says it is listening. The problem is no decodes. However, if I listen to the socket with netcat and pipe the output to Direwolf stdin, it works. This uses 7358 as the output port from the converter. When I run Direwolf like this: direwolf -a 10 -r 16000 -n 1 -b 16 -B1200 -t 0 UDP:7358 I get. Dire Wolf version 1.7 Includes optional support for: hamlib cm108-ptt dns-sd Reading config file /home/dragnet/direwolf.conf Audio input device for receive: UDP:7358 (channel 0) Audio out device for transmit: default (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 16000 sample rate, DTMF decoder enabled. Note: PTT not configured for channel 0. (Ignore this if using VOX.) Disabled AGW network client port. DNS-SD: Avahi: Announcing KISS TCP on port 0 as 'Dire Wolf on airband' DNS-SD: Avahi: Service name collision, renaming service to 'Dire Wolf on airband #2' DNS-SD: Avahi: Announcing KISS TCP on port 0 as 'Dire Wolf on airband #2' DNS-SD: Avahi: Service 'Dire Wolf on airband #2' successfully registered. ADEVICE0: Sample rate approx. 8.0 k, 0 errors, receive audio level CH0 34 Note the last line. It doesn't matter which sample rate I choose, it always says 8.0k, and doesn't decode. I have also tried 1.8A & 1.8D, which are no different. This is what I get when I use netcat as an intermediary. netcat -u -l -p 7358 | direwolf -r 16000 -a 10 -n 1 -b 16 -B1200 -t 0 - Dire Wolf version 1.7 Includes optional support for: hamlib cm108-ptt dns-sd Reading config file /home/dragnet/direwolf.conf Audio input device for receive: stdin (channel 0) Audio out device for transmit: default (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 16000 sample rate, DTMF decoder enabled. Note: PTT not configured for channel 0. (Ignore this if using VOX.) Disabled AGW network client port. DNS-SD: Avahi: Announcing KISS TCP on port 0 as 'Dire Wolf on airband' DNS-SD: Avahi: Service name collision, renaming service to 'Dire Wolf on airband #2' DNS-SD: Avahi: Announcing KISS TCP on port 0 as 'Dire Wolf on airband #2' DNS-SD: Avahi: Service 'Dire Wolf on airband #2' successfully registered. Digipeater VA3BAL-4 audio level = 35(10/8) |||||_|__ [0.2] VE3GIF-2>APDW17,VA3BAL-4*,DISCVR:}VA3VWX-13>APRS,TCPIP,VE3GIF-2*:@091753z4337.37N/07929.87W_288/008g015t033r000p000P000h76b10204.DsVP Weather Report, WEATHER Station (blue) Use of "APRS" in the destination field is obsolete. You can help to improve the quality of APRS signals. Tell the sender (VA3VWX-13) to use the proper product identifier from https://github.com/aprsorg/aprs-deviceid N 43 37.3700, W 079 29.8700 wind 9.2 mph, direction 288, gust 15, temperature 33, rain 0.00 in last hour, rain 0.00 in last 24 hours, rain 0.00 since midnight, humidity 76, barometer 30.14, ".DsVP" Opening log file "2025-02-09.log". Digipeater VA3BAL-4 audio level = 35(10/8) _|||||___ [0.3] VE3GIF>APK102,VA3BAL-4*,DISCVR:=4345.72N/07911.10W_234/011g t031r000p000P h82b10195KDvs<0x0d> Weather Report, WEATHER Station (blue), Kenwood D710 N 43 45.7200, W 079 11.1000 wind 12.7 mph, direction 234, temperature 31, rain 0.00 in last hour, rain 0.00 in last 24 hours, humidity 82, barometer 30.11, "KDvs" ADEVICE0: Sample rate approx. 16.0 k, 0 errors, receive audio level CH0 52 That is, not only does it report the correct sample rate, it decodes just fine. Any ideas? Or is it time for a bug report? 73, Chris
Started by Chris VE3NRT @ · Most recent @
What other things can I monitor with Dire Wolf. RTL-FM and Linux? 3
I have an RTL-SDR receiver I use for monitoring ACARS, and APRS. I am interested in monitoring just for fun other signals on the uhf/vhf bands. I have an OMNI X scanner antenna up pretty high so I get decent reception. I live close to a large metropolitan area. There is an industrial area where there are ships and barges. APRS is kind of boring, but ACARS is interesting. I have used in the past my dongle with DSD plus and SDR Trunk for monitoring the state communication system. DSD Plus is too unwieldy to use. But I like SDR Trunk. Anyway what other entities are possible to configure to listen to? i use MX Linux.
Started by w1av @ · Most recent @
JSON Output from Direwolf 5
Does anyone know if it is possible to add a JSON Post output to Direwolf. In addition to saving the GPS data to a logfile I would like to also send the data to a website. The preferred delivery to the website is JSON POST. Jakob
Started by Jakobn108 @ · Most recent @
Add -dgt to dw-start.sh 2
Hello again to the group! I start Direwolf via cron with dw-start.sh. I¡¯d like to add -dgt to the startup command. My question is, which line (number) do I add -dgt to? Thanks in advance for any replies. Doug AE9DM
Started by [email protected] @ · Most recent @
ISOTIME in Logfile
Where is ISOTIME derived from in the Direwolf logfile? Is this time info received from APRS messages or is it a timestamp added to the log derived from the local time on the PC running Direwolf?
Started by Jakobn108 @
I need help! 21
Hello! New to the group, thanks for allowing me to post. I've been running APRS/Dire Wolf mobile tracker successfully since 2020 with the same physical setup. My SD became corrupt and like a dummy, never made a backup. I'm trying to get it running again with Dire Wolf 1.8 Development D and having a couple issues: GPS doesn't move within Dire Wolf (stuck at 4041.76N/08928.70) but moves with GPSMON Not getting digipeated I believe the issues are related but can't find the common denominator. Dire Wolf launches without error using -dgt I've attached the script that I'm using to create my new installation for reference. ANY assistance would be greatly appreciated. 73 - AE9DM, Doug
Started by [email protected] @ · Most recent @
Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500) 18
Hello, I get the the error "Timeout waiting for input from audio device 0. Terminating after audio input failure." immediately upon transmitting a connection request to a pbbs. The FTM-500 locks up in transmit, and I need to disconnect the digirig cable from the laptop and restart Direwolf/Paracon to recover. Yes, it looks like RFI, but this hardware combination works fine with VaraFM and Soundmodem. I've also added additional ferrite beads to the digirig cable. I've noticed that I don't get the same error (and transmit lockup) when I set the audio output device to a different soundcard, while keeping the audio input on the digirig lite. I am able to transmit on the digirig lite without lockup. Direwolf also works fine while just listening on 144.39. The audio levels look good and most packets are decoded. Any help will be appreciated! Thanks, Eric KG7ASX Direwolf config follows: ADEVICE 1 2 CHANNEL 0 MYCALL KG7ASX MODEM 1200 PTT CM108 AGWPORT 8000 KISSPORT 8001 IGTXLIMIT 6 10 RETRY 5 FRACK 4 MAXFRAME 7 EMAXFRAME 63 PACLEN 128 DWAIT 64 TXDELAY 30 TXTAIL 15 Startup Text: PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> .\direwolf.exe Dire Wolf version 1.7 Includes optional support for: cm108-ptt Reading config file direwolf.conf Available audio input devices for receive (*=selected): 0: FTdx-10 Input (USB AUDIO CODEC * 1: Digirig Lite Input (2- USB Audi (channel 0) 2: Microphone Array (Intel? Smart Available audio output devices for transmit (*=selected): 0: FTdx-10 Output (USB AUDIO CODE 1: Speaker (Realtek(R) Audio) * 2: Digirig Lite Output (2- USB Aud (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate. Using \\?\hid#vid_0d8c&pid_0012&mi_03#7&38439e45&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 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 ...
Started by KG7ASX @ · Most recent @
Unable to connect to IGate server 7
Hi, I am trying to set up an IGat. Everything seems to be working. Packets are being decoded. The connection to the gate servers is the only thing that isn't working. Connect to IGate server noam.aprs2.net (192.104.234.219) failed. It's been running for a couple of hours now and has tried half a dozen IP addresses so far. I've got a good internet connection and can ping those servers. One thing that I am not too sure about is the APRS-IS password. Should I get a password for my call sign or should my call sign be appended with the SSID? Aside from the password, everything else seems fine in the config file. Any help or tips would be appreciated. Sepehr N6IRN
Started by Sepehr - N6IRN @ · Most recent @
Problems trying configure my location for iGate.. 7
Morning from a cold, wet and windy Scotland.... I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on aprs.fi properly... I've tried Lat/ Long and UTM. My Pbeacon statement is: PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=42^55.94539 long=071^3.39273E via=WIDE1-1,WIDE2-1 This locates me in Eastern Europe near Tapaz..... My lat/long is 55.945526, -3.392573 What am I doing wrong?? (what do the 42^ and 071^ mean/do???) Bob
Started by Bob @ · Most recent @
Unable to get Direwolf to connect to IC-7300 15
I have been running my IC-7300 with a VARA modem and Winlink on HF for some time. I would like to be able to operate HF packet using Direwolf and the VARA modem. I downloaded installed, and modified the direwolf.conf file. I have attached my direwolf.conf. When I run the command direwolf -x a direwolf executes and says ready for KISS connection. However, I do get this message Line 268 is commented out # OBEACON - for an object report (usually some other entity) Also, the IC-7300 does not transmit after issuing the direwolf -x a command I would appreciate assistance on properly configuring the station for HF Packet. Bob, KN4HH
Started by Bob Watson @ · Most recent @
APRS messaging query 4
Looking to understand some obscure things about APRS messaging. In Understanding-APRS-Packets.pdf on John's aprsspec github site. (Tnx John!) RF to RF on same channel, well understood. Also understood is that the delivery will be retried until timed out, an ack is received or send cancelled. RF to RF via an IGate says can be done, but how does one know the recipients current RF location? Is it just automatic when WIDE hops are used? Also could the recipients closest RF TX site be explicitly defined in the digi path? The WHOIS server example is a bit confusing, but in essence appears to be a robot data response. My main question though is how does one poll for a message "being held not deliverable" in IS? (Mainly I think in VK as Inet>RF messaging seems disabled) I use Xastir to only display/list the RF channel and usually leave the Internet Server interface down, but now wonder if up and the filter parameter t/m/VK* will work? (I have TX disabled on this interface too.) I know too there is a facility to send messages from the CLI, but is there a method to pull down "held" messages? Tnxs Bob VK2YQA
Started by Bob Cameron @ · Most recent @
Containerized (Docker) APRS tracker with DireWolf 12
Hi all, I've been building an APRS tracker for Raspberry Pi and other small SBCs, and (mainly because I've been doing this for a whole bunch of ADSB/ACARS/AIS-related software as well), I have created a containerized version of this. The Docker container includes GPSD (to capture GPS data from a USB-based GPS dongle), Chrony (to set the system time based on the GPS data), and (of course) DireWolf configured as a tracker. The advantage of Docker is that it creates a (sort-of) VM environment that is easy to configure, deploy, and maintain/update. My idea was to automate the configuration as much as possible. For "normal" deployments: the container figures out the soundcard config you can (in most cases) set the TX and RX audio levels with an environment parameter as simple %full-scale. This takes away the need to do much sleuthing with `alsamixer` and the like. it detects which USB2Serial port the GPS is using it monitors the serial port as I found that my GPS randomly disconnects and reconnects to a different /dev/ttyACMx port it abstracts several of the necessary APRS tracker parameters into the `docker-compose.yml` config file I've set it up so all data is written to a minimal set of directories that can easily be mapped to `tmpfs` (RAM), so we can lock down the rest of the OS to protect the SD card when the SBC goes down because the car power goes away. I've tested it (a bit) on Raspi3B+, Raspi4B, LePotato, and OrangePi boards, using Raspberry Pi OS (32 and 64 bits), DietPi (arm64), and "pure" minimalist Debian (on the LePotato board). They all work more or less the same. So far so good and the basics work fine. There are a few things I still want to tackle: I need to figure out what is causing these random disconnects/reconnects of the GPS. Maybe it's just because it's a cheap dongle? My soundcard dongle will only work in RX sampling rate of 48k. The only way I get DireWolf to decode is by adding `-r 48000` to the command line. I have not been able to figure out how to lower the sampling rate of the audio device Right now, only an `armhf`, `arm64`, and `amd64` image is available. Specifically, there's no `armel` image which makes the container incompatible with some of the older/lower-end Raspi's. This has nothing to do with DireWolf, it's related to something else that I simply haven't prioritized to solve (specifically, I use S6 version 3 which doesn't work by default on `armel` or `i386`) I need to pay some attention to my hardware. The Baofeng UV-5R I'm using with APRS-K2 cable and Vox for PTT control is obviously nowhere close to ideal Need to "harden" the OS so it's safe with hard power-downs If you are interested, feel free to take a look here: https://github.com/sdr-enthusiasts/docker-aprs-tracker 73, Ramon KX1T
Started by Ramon Kolb @ · Most recent @
wrong topic - but I guess this is where the experts live 11
I have 2 sites - my home and my bunker. I own both buildings and they are about 10 miles apart and in 2m contact. The bunker is NOT residential it is commercial. I would like to run packet radio from both sites. Right now there are only 2 other packet sites in the area, and I can reach them from both locations. I know I cant use the same "-1 -2 -3 postfixes from both sites. I have had both sites talking with different "nodenames". Having two sites (and access to both sites at the same time) would allow me to better understand and experiment with packet routing setups - as well as to try out different pieces of kit (inc direwolf!) from home. Are there any opinions about the "best" way to do this - or the pitfalls and what I have to be careful with?? Iain MM7IRM
Started by iainmaoileoin @ · Most recent @
Receive only with SDRconnect and direwolf 15
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
Started by phillor@... @ · Most recent @
Not Detecting SDR 3
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.
Started by Josh MacDonald @ · Most recent @
New Setup issues 39
Hello, I am currently trying to get our ic-9100 radios connected via direwolf and a rigblaster plug and play to our ubuntu computers. I have successfully gotten the config files set up and have successfully transmitted (using run code 'direwolf -x a') through one ic-9100 (lets call this radio A) and successfully hear the transmission through the other radio (radio B). However, the radio B is also connected with a second rigblaster to computer B, which while running with run code 'direwolf' shows no received information. I have also tried to tune both radio set ups to 144.39 which I was told was a national APRS frequency and that I should be able to receive packets from it. While tuned, I can hear the transmissions, but again, neither setup of direwolf is showing any kind of received information. I am not sure if the issue lies in the config file or if it has something to do with our aux jack set-up... The rigblaster has an input and output aux jack, while our computers have a combo input/output jack. I believe we are using a splitter that should solve that issue and allow both to be plugged in, but- maybe I'm wrong? Any advice or ideas would be appreciated. Here are the lines that are uncommented in our config file: ADEVICE plughw:1,0 CHANNEL 0 MYCALL <This is set up with our call sign, left out here> MODEM 1200 PTT /dev/ttyUSB0 RTS DTR AGWPORT 8000 KISSPORT 8001 IGTXLIMIT 6 10 FX25TX 1 PERSIST 63 SLOTTIME 12 RETRY 5 FRACK 5 MAXFRAME 4 PACLEN 128 DWAIT 0 TXDELAY 50 TXTAIL 40 We mainly followed the setup instructions from https://themodernham.com/ultimate-direwolf-tnc-installation-guide-for-windows-and-linux/#get-linux-com
Started by cdres @ · Most recent @
Unable to start up direwolf on mac
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
Started by Sepehr - N6IRN @
Current Image
Image Name
Sat 8:39am