开云体育

Hello Danny, Direwolf v1.7A is a rather old version of the DEV branch as the current version is 1.7E: grep "Dire Wolf DEVELOPMENT" src/direwolf.c -- dw_printf ("Dire Wolf DEVELOPMENT

Hello Clinton, For the "original steps" you were following, where did you read those? Do you have a URL? Can you describe your setup? Since you 're showing two radios here (a Baofeng and a RTL

Hi, I finally figured the issue with the install (updated commands are helpful) but when running direwolf I get the following errors. My set up is a baofeng UV5R+, RTL-SDR receiver R820T2, raspberry

I have direwolf configured with AGWPORT 0 KISSPORT 8100 But when I start direwolf I get two KISS ports Disabled AGW network client port. Ready to accept KISS TCP client application 0 on port 8001

I was getting errors when I ran sudo make install and after, but I found the updated commands and was able to install but I get a bunch of errors when starting direwolf. Sent from Mail for

I was in the build directory. I finally found some updated commands and ran them and was able to finish the install but I’m getting a bunch of errors when I start direwolf. Sent from Mail for

Exactly what commands did you use?

Hei, In what directory you gave the command? sudo make install should be run in the build directory. I use thehe commands: cd ~ git clone -b dev https://www.github.com/wb2osz/direwolf cd

Hi, I followed the directions for installing direwolf on a raspberry pi and everything was working but when I get to the sudo make install command I get the following: make: *** No rule to make

Thanks much. It looks like it worked for the Libasound2. I'll continue with direwolf. 73, Larry? WB8LBZ El Paso, TX

The "elpa-magit" error is probably the result of trying to install "git-all" rather than just "git". There are some other issues with the out of date build instructions. Use the instructions

Hello Larry, I looked over that documentation and while it's nicely written, it's recommending some obsolete things like removing pulseaudio, I bet when you did that, it asked you to uninstall a lot

I am in the process of trying the install process described in the https://n1aae.com/raspberry-pi-aprs-direwolf-linux-igate-digipeater/ guide. This is a Raspberry Pi3 with the latest January 28th 2022

KISS protocol set TXDELAY = 30 (*10mS units = 300 mS), port 0 KISS protocol set Persistence = 63, port 0 KISS protocol set SlotTime = 12 (*10mS units = 120 mS), port 0 KISS protocol set TXtail = 3

As a quick follow up, what are your settings for slot time and persistence per the Direwolf User Guide section 9.2.13? You can learn how these two values are used to determine when the frequency

Yes, DCD is "0" before my TX every time so the TX INHIBIT function seems to be working.? It seems as though my issue is from DCD dropping mid-packet and then my station immediately jumps on the false

Hello Joshua, What was the state of DCD before your station asserted PTT? I assume it was "0". You should disable the APRS heuristics with say the following: FIX_BITS 0 AX25 This might be

It seems as though Direwolf is dropping the DCD occasionally on RX even though the packet gets decoded.? Here is an example: You can see that the carrier detect s

You are understanding me correctly.? I will turn on debugging and see what's going on.

If I'm understanding you correctly, you have a single channel setup on Direwolf as your 300bps TNC. Correct? If so, when Direwolf's base logic detects DCD on the signal, it should consider the