开云体育

Lately, when I try to download and compile the latest dev version of DireWolf, I get a lot of compile-time errors. Not being a programmer, I don’t understand what it all means and the compiled version of direwolf fails to run. I’ve included the output of my compile attempt below and would appreciate if anybody can tell me what I need to do/install to correct the errors. Thanks, -Jeffrey Komori, KH6JUZ $ uname -a Linux KH6JUZ 6.6.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.47-1+rpt1 (2024-09-02) aarch64 GNU/Linux $ git clone https://www.github.com/wb2osz/direwolf Cloning into 'direwolf'... warning: redirecting to https://github.com/wb2osz/direwolf.git/ remote: Enumerating objects: 4052, done. remote: Counting objects: 100% (1583/1583), done. remote: Compressing objects: 100% (415/415), done. remote: Total 4052 (delta 1297), reused 1301 (delta 1156), pack-reused 2469 (from 1) Receiving objects: 100% (4052/4052), 139.53 MiB | 4.22 MiB/s, done. Resolving deltas: 100% (2858/2858), done. $ cd direwolf $ git checkout dev branch 'dev' set up to track 'origin/dev'. Switched to a new branch 'dev' $ vi src/direwolf.h $ mkdir build $ cd build $ cmake .. -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Git: /usr/bin/git (found version "2.39.5") -- Dire Wolf Version: 1.8.0-0734e46 -- Build type set to: Release CMake system: Linux -- Target architecture: ARM64 -- Use NEON SIMD instructions -- Looking for strlcpy -- Looking for strlcpy - not found -- Looking for strlcat -- Looking for strlcat - not found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE -- Checking for module 'libgps' -- Found libgps, version 3.22 -- Found GPSD: /usr/lib/aarch64-linux-gnu/libgps.so -- Checking for module 'hamlib' -- Package 'hamlib', required by 'virtual:world', not found -- Could NOT find hamlib (missing: HAMLIB_LIBRARY HAMLIB_INCLUDE_DIR) -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") -- Found gpiod: /usr/lib/aarch64-linux-gnu/libgpiod.so -- Found ALSA: /usr/lib/aarch64-linux-gnu/libasound.so (found version "1.2.8") -- Checking for module 'libudev' -- Found libudev, version 252 -- Found udev: /usr/lib/aarch64-linux-gnu/libudev.so -- Found Avahi: TRUE -- Configuring done -- Generating done -- Build files have been written to: /home/aprs/direwolf/build $ make -j4 [ 1%] Building C object external/misc/CMakeFiles/misc.dir/strlcpy.c.o [ 1%] Building C object external/geotranz/CMakeFiles/geotranz.dir/mgrs.c.o [ 1%] Building C object external/misc/CMakeFiles/misc.dir/strlcat.c.o [ 2%] Building C object external/geotranz/CMakeFiles/geotranz.dir/error_string.c.o [ 2%] Building C object external/geotranz/CMakeFiles/geotranz.dir/polarst.c.o [ 2%] Linking C static library libmisc.a [ 3%] Building C object external/geotranz/CMakeFiles/geotranz.dir/tranmerc.c.o [ 3%] Built target misc [ 3%] Building C object src/CMakeFiles/decode_aprs.dir/decode_aprs.c.o [ 4%] Building C object src/CMakeFiles/text2tt.dir/tt_text.c.o [ 4%] Building C object external/geotranz/CMakeFiles/geotranz.dir/ups.c.o [ 5%] Building C object external/geotranz/CMakeFiles/geotranz.dir/usng.c.o [ 5%] Building C object external/geotranz/CMakeFiles/geotranz.dir/utm.c.o [ 6%] Building C object src/CMakeFiles/decode_aprs.dir/deviceid.c.o [ 7%] Linking C static library libgeotranz.a [ 7%] Building C object src/CMakeFiles/decode_aprs.dir/ais.c.o [ 7%] Linking C executable text2tt [ 7%] Built target geotranz [ 7%] Building C object src/CMakeFiles/tt2text.dir/tt_text.c.o [ 7%] Built target text2tt [ 8%] Building C object src/CMakeFiles/ll2utm.dir/ll2utm.c.o [ 8%] B

Since I just spent an hour messing with systemd files to get a direwolf.service working I wanted to post an operational one that may help some people. $ cat /etc/systemd/system/direwolf.service [Unit] Description=direwolf After=network.target [Service] Type=forking Restart=always RestartSec=90 StartLimitInterval=400 StartLimitBurst=3 User=<USERNAME> Group=<USERNAME> ExecStart=/usr/bin/screen -S dw -d -m /usr/local/bin/direwolf SyslogIdentifier=Direwolf [Install] WantedBy=multi-user.target this assumes you built from source and have screen installed. check file destinations. after systemctl enable/start just run "screen -r dw"

I want to set my 897D frequency when starting direwolf inside the direwolf conf .... Possible? Maybe even to FM Mike

Working on a project and I have looked though the documentation as well as searched this group and have not come up with anything. When Direwolf uses speech for a beacon does it / can it transmit a 100 hz tone along with the speech for voice alerting radios? Or would I need to have another program output the tone when it is speaking? Thanks in advance! Jon KB3OSP

I'm testing a local (non upstream) APRS-IS server and was advised to switch all my client connections to port 10152. How do I configure/change that in Direwolf? I am using 1.8D. Thanks Doug

I'm decoding 14.105 MHz LSB with Direwolf. Most packets have format errors. I guess that it's because they are not APRS. For example: KD2YCK-1 audio level = 59(11/11) __|||____ [0.3] KD2YCK-1>MAIL:Mail For:KD2YCK N1UGK NC8Q N2MH ERROR!!! Unknown APRS Data Type Indicator "M", UNKNOWN vendor/model KD0YTE-7 audio level = 39(30/12) _||||||__ [0.3] KD0YTE-7>ID:KD0YTE - Kirksville MO. EN30qf BPQ Packet Node <0x0d> ERROR!!! Unknown APRS Data Type Indicator "K" Use of "ID" in the destination field is obsolete. You can help to improve the quality of APRS signals. Tell the sender (KD0YTE-7) to use the proper product identifier from https://github.com/aprsorg/aprs-deviceid Can Direwolf parse non APRS packets? Larry, N7RTS

I'm running direwolf this way on Debian: net105.conf: ============== ACHANNELS 1 CHANNEL 0 MODEM 300 1600:1800 7@30 /4 D command line: ============== direwolf -c ./net105.conf -t 0 -n 1 -b 16 -B 300:1600:1800 -r 48000 -X /4 udp:7355 Are these options optimal for HF 300 baud? I prefer to use command line options as much as possible instead of .conf file settings. I'd also like to get rid of any redundancies or default items in the .conf file. I am decoding a lot of packets on 14.105 MHz LSB but want to make sure the options are optimized. thanks, Larry

I am trying to get IS-traffic to be sent via a networked-kiss interface. packets retrieved from IS being digipeated to the network-kiss interface (in my case channel 6) produce the following output: [ig>tx] OE6MMF-1>APLG01,TCPIP*,qAC,T2CSNGRAD:=4711.45NL01545.85E&LoRa iGATE [6.is] X>X:}OE6MMF-1>APLG01,TCPIP*,qAC,T2CSNGRAD:=4711.45NL01545.85E&LoRa iGATE expected behaviour: [ig>tx] OE6MMF-1>APLG01,TCPIP*,qAC,T2CSNGRAD:=4711.45NL01545.85E&LoRa iGATE [6.is] OE6PLD-2>APDW18:}OE6MMF-1>APLG01,TCPIP*,qAC,T2CSNGRAD:=4711.45NL01545.85E&LoRa iGATE can anybody confirm this behaviour or has NCHANNEL running correctly? regadrs peter, OE6PLD

Per chance, have you ever heard a position report from the digipeater itself, about the digipeater itself? There is a concept in APRS called vicinity plotting, where the location of a station that hasn't yet reported its own position is estimated from the position of the stations first relayed by that digipeater (for digipeaters) or the position of the first relaying digipeater (for originating stations). In fact, in my area, there are several "stealth" digipeaters that never send position beacons, but only meet their government-mandated identification requirements by inserting their callsign-SSID into the digipeat path (UITRACE), so vicinity plotting is the only way to locate the digipeaters (other than true RF direction-finding or asking the digipeater owner). Just out of curiosity, what program or website are you using to see the digipeater's location? Presumably, it's one that supports vicinity plotting. Andrew, KA2DDO author of YAAC (which does support vicinity plotting)

Greetings, I'm wondering why the ISS PBEACON always indicates ~0.0 lat/lon. Is GPS disabled due to rf electrical or security concerns? From direwolf 1.8D: ... 0,1724595363,2024-08-25T14:16:03Z,RS0ISS,RS0ISS,16(2/2),0,',RS0ISS,IS,0.005500,0.166667,0.0,,,,,,Kenwood TM-D710,Special,,ARISS-International Space Station ... RS0ISS audio level = 16(2/2) ___||____ [0.3 07:16:03 25Aug2024] RS0ISS>0P0PS3,APRSAT:'v&<0x1c>l <0x1c>SI]ARISS-International Space Station=<0x0d> MIC-E, Satellite/Pacsat w/overlay I, Kenwood TM-D710, Special N 00 00.3300, E 000 10.0000, 0 km/h (0 MPH) ARISS-International Space Station ... Thank you.

I don't remember where I read about it, but there was somewhere a mention of software that was nulling out the { on message identifiers on gated packets. There is a discussion on the QTHapp google mailing list that includes the following example: > Here's a few of the raw packets from APRS.fi: > > 2024-08-19 10:30:21 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1*,WIDE2-2,qAR,KC1QHG::kr1st :Good morning > friend!{01} > 2024-08-19 10:30:22 EDT: > KC1SRI>APQTH1,K1FFK-1,EKONCT*,WIDE2-1,qAO,WA1VIN::kr1st :Good morning > friend!<0x00>01} [Invalid message packet] > 2024-08-19 10:34:15 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1*,WIDE2-2,qAR,KC1QHG::kr1st :Good morning > friend!{01} > 2024-08-19 10:34:17 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1,EKONCT*,WIDE2,qAO,WA1VIN::kr1st :Good > morning friend!<0x00>01} [Invalid message packet] > 2024-08-19 10:36:35 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1*,WIDE2-2,qAR,KC1QHG::KR1ST :Good morning > friend!{01} > 2024-08-19 10:36:37 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1,EKONCT*,WIDE2,qAO,WA1VIN::KR1ST :Good > morning friend!<0x00>01} [Invalid message packet] > 2024-08-19 10:49:11 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1*,WIDE2-2,qAR,KC1QHG::KR1ST :Good morning > friend!{01} > 2024-08-19 10:49:14 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1,EKONCT*,WIDE2,qAO,WA1VIN::KR1ST :Good > morning friend!<0x00>01} [Invalid message packet] > 2024-08-19 12:54:35 EDT: > KC1SRI>APQTH1,K1FFK-1,WIDE1*,WIDE2-2,qAR,W1HS-11::w0rmt :Trying this > out. Maybe this packet won't get rejeceted?{01} > 2024-08-19 12:54:36 EDT: > KC1SRI>APQTH1,K1FFK-1,EKONCT*,WIDE2-1,qAO,WA1VIN::w0rmt :Trying this > out. Maybe this packet won't get rejeceted?<0x00>01} [Invalid message > packet] where the WA1VIN IGate is running Direwolf if you believe his >APDW17 ToCall. I checked the Direwolf issues, but didn't quickly notice any related to messaging, so I decided to just ask here. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Hi, Today i noticed that filters do not work on third party packets coming over RF. I opened an issue on Github explaining it. https://github.com/wb2osz/direwolf/issues/428

It doesn't seem appropriate that messages are generally considered high priority yet messages from the igate to the radio are sent to the low priority transmit queue. (TQ_PRIO_1_LO in igate.c at line 2008 for V1.7 release). Is this planned to be changed to high priority? Search didn't reveal any similar topics. Thanks, Graeme VK2HFG

Greetings, I'd like to acquire a radio to use for my 2-way iGate. I've a rack-mount faceplate that can hold another Kenwood mobile, so that would be the preference. Reading direwolf-doc/Radio-Interface-Guide.pdf, I find in my box'o'stuff an RPi 3B with the NWDR "DRAWS" hat, wired for 12V operation with Andersen power poles, so here's my question, please: Will the 6 pin mini-DIN radio connector on the DRAWS hat allow hamlib/rigctl radio control at the same time as the audio, perhaps as 2 separate devices? The gpredict software can then adjust for Doppler shifting while kissutil and direwolf are {en,de}coding the APRS traffic. I think that normally an audio interface gets "locked" by direwolf? If the DRAWS radio port can be made available simultaneously for both usages, also welcomed would be a recommended 2 or 3 band hamlib-supported Kenwood mobile. Thank you.

Greetings, I'm wondering why /usr/bin/screen doesn't appear as a processID, yet /usr/bin/SCREEN does appear but doesn't even exist. direwolf is started via crontab entry as user repeater at boot time, and verified every minute as currently running, else it's started within screen: $ crontab -l | grep screen @reboot sleep 10 && /usr/bin/screen -S direwolf -d -m /usr/local/bin/direwolf -c /home/repeater/direwolf.conf -L /home/repeater/direwolf.log -T "\%H:\%M:\%S \%d\%b\%Y" * * * * * if [ x$(pidof direwolf) = "x" ]; then /usr/bin/screen -S direwolf -d -m /usr/local/bin/direwolf -c /home/repeater/direwolf.conf -L /home/repeater/direwolf.log -T "\%H:\%M:\%S \%d\%b\%Y"; fi However (emphasis mine): $ ps aux | grep screen | grep -v grep $ ps aux | grep -i screen | grep -v grep repeater 738 0.0 0.2 8092 2192 ? Ss 09:28 0:00 /usr/bin/SCREEN -S direwolf -d -m /usr/local/bin/direwolf -c /home/repeater/direwolf.conf -L /home/repeater/direwolf.log -T %H:%M:%S %d%b%Y $ ls -l /usr/bin/SCREEN ls: cannot access '/usr/bin/SCREEN': No such file or directory $ pidof screen direwolf 739 $ pidof SCREEN direwolf 738 739 It's not earth-shattering, but I find it quite curious, if anyone can explain it, please.

On Wed, Aug 7, 2024 at 12:21 PM, WB2OSZ wrote: The APRS protocol specification can be confusing and difficult to digest. A more gentle introduction can be found in Understanding APRS Packets. 73, John WB2OSZ I have read in different messages that the Telemetry packet format has been "widened" and n longer limited to 3-digits with no decimal place - in other words 000 - 999. In your document (referenced above) you state " ... All of the modern application that I tested understood this more flexible format. ..." This may not be the best forum for my questions, but the document is with Direwolf's github structure. My questions with comments: 1. Is there really a need for the EQNS message if there is an ability to provide 'real' data? In the old format, voltage was often sent as something like 138. If the value sent is 13.8, there is not need for EQNS:. Assuming the default EQNS: is ALWAYS 0,1,0. This information would ONLY be needed if "additional" conversion is required. 2. Is there any practical limitation to the values sent (like 3 or 4 significant digits)? It would make no sense to send something like pi() to the 100th decimal point. After 3 or 4 significant digits, you could change the UNIT. message to indicate: (grams vs. kilograms) or (ounces vs. lbs. vs. tons). ------- Robert Giuliano KB8RCO

Hi. I have a Kenwood TH-D74, which provides a serial TNC. It works very well, and removes the need to think about PTT as compared to using it as a sound card. Is there a way to run direwolf's digipeater functionality against a serial TNC? -- typedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "thomas@..." }; char kernel[] = { "Linux" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt" }; char pgp[] = { "9907 8698 8A24 F52F 1C2E 87F6 39A4 9EEA 460A 0169" }; char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" }; } me_t;