Decoded Information from Radio Emissions for Windows Or Linux Fans

Last update: Jan 3, 2023

Overview

Dire Wolf

Decoded Information from Radio Emissions for Windows Or Linux Fans

In the early days of Amateur Packet Radio, it was necessary to use an expensive "Terminal Node Controller" (TNC) with specialized hardware. Those days are gone. You can now get better results at lower cost by connecting your radio to the "soundcard" interface of a computer and using software to decode the signals.

Why waste $200 and settle for mediocre receive performance from a 1980's technology TNC using an old modem chip? Dire Wolf decodes over 1000 error-free frames from Track 2 of the WA8LMF TNC Test CD, leaving all the hardware TNCs, and first generation "soundcard" modems, behind in the dust.

Dire Wolf now includes FX.25 which adds Forward Error Correction (FEC) in a way that is completely compatible with existing systems. If both ends are capable of FX.25, your information will continue to get through under conditions where regular AX.25 is completely useless.

Dire Wolf is a modern software replacement for the old 1980's style TNC built with special hardware.

Without any additional software, it can perform as:

APRS GPS Tracker
Digipeater
Internet Gateway (IGate)
APRStt gateway

It can also be used as a virtual TNC for other applications such as APRSIS32, Xastir, APRS-TW, YAAC, PinPoint APRS, UI-View32,UISS, Linux AX25, SARTrack, Winlink Express (formerly known as RMS Express, formerly known as Winlink 2000 or WL2K), BPQ32, Outpost PM, Ham Radio of Things, Packet Compressed Sensing Imaging (PCSI), and many others.

Features & Benefits

Dire Wolf includes:

Beaconing, Tracker, Telemetry Toolkit.

Send periodic beacons to provide information to others. For tracking the location is provided by a GPS receiver. Build your own telemetry applications with the toolkit.
APRStt Gateway.

Very few hams have portable equipment for APRS but nearly everyone has a handheld radio that can send DTMF tones. APRStt allows a user, equipped with only DTMF (commonly known as Touch Tone) generation capability, to enter information into the global APRS data network. Responses can be sent by Morse Code or synthesized speech.
Digipeaters for APRS and traditional Packet Radio.

Extend the range of other stations by re-transmitting their signals. Unmatched flexibility for cross band repeating and filtering to limit what is retransmitted.
Internet Gateway (IGate).

IGate stations allow communication between disjoint radio networks by allowing some content to flow between them over the Internet.
Ham Radio of Things (HRoT).

There have been occasional mentions of merging Ham Radio with the Internet of Things but only ad hoc incompatible narrowly focused applications. Here is a proposal for a standardized more flexible method so different systems can communicate with each other.

Ham Radio of Things - IoT over Ham Radio
AX.25 v2.2 Link Layer.

Traditional connected mode packet radio where the TNC automatically retries transmissions and delivers data in the right order.
KISS Interface (TCP/IP, serial port, Bluetooth) & AGW network Interface (TCP/IP).

Dire Wolf can be used as a virtual TNC for applications such as APRSIS32, Xastir, APRS-TW, YAAC, PinPoint APRS, UI-View32,UISS, Linux AX25, SARTrack, Winlink Express (formerly known as RMS Express, formerly known as Winlink 2000 or WL2K), BPQ32, Outpost PM, Ham Radio of Things, Packet Compressed Sensing Imaging (PCSI), and many others.

Radio Interfaces:

Uses computer's "soundcard" and digital signal processing.

Lower cost and better performance than specialized hardware.

Compatible interfaces include DRAWS, UDRC, SignaLink USB, DMK URI, RB-USB RIM, RA-35, DINAH, SHARI, and many others.
Standard 300, 1200 & 9600 bps modems and more.
DTMF ("Touch Tone") Decoding and Encoding.
Speech Synthesizer interface & Morse code generator.

Transmit human understandable messages.
Compatible with Software Defined Radios such as gqrx, rtl_fm, and SDR#.
Concurrent operation with up to 3 soundcards and 6 radios.

Portable & Open Source:

Runs on Windows, Linux (PC/laptop, Raspberry Pi, etc.), Mac OSX.

Documentation

Stable Version

Latest Development Version

Power Point presentation -- Why not give a talk at a local club meeting?

Installation

Windows

Go to the releases page. Download a zip file with "win" in its name, unzip it, and run direwolf.exe from a command window.

You can also build it yourself from source. For more details see the User Guide in the doc directory.

Linux - Using git clone (recommended)

Note that this has changed for version 1.6. There are now a couple extra steps.

First you will need to install some software development packages using different commands depending on your flavor of Linux. In most cases, the first few will already be there and the package installer will tell you that installation is not necessary.

On Debian / Ubuntu / Raspbian / Raspberry Pi OS:

sudo apt-get install git
sudo apt-get install gcc
sudo apt-get install g++
sudo apt-get install make
sudo apt-get install cmake
sudo apt-get install libasound2-dev
sudo apt-get install libudev-dev

Or on Red Hat / Fedora / CentOS:

sudo yum install git
sudo yum install gcc
sudo yum install gcc-c++
sudo yum install make
sudo yum install alsa-lib-devel
sudo yum install libudev-devel

CentOS 6 & 7 currently have cmake 2.8 but we need 3.1 or later. First you need to enable the EPEL repository. Add a symlink if you don't already have the older version and want to type cmake rather than cmake3.

sudo yum install epel-release
sudo rpm -e cmake
sudo yum install cmake3
sudo ln -s /usr/bin/cmake3 /usr/bin/cmake

Then on any flavor of Linux:

cd ~
git clone https://www.github.com/wb2osz/direwolf
cd direwolf
git checkout dev
mkdir build && cd build
cmake ..
make -j4
sudo make install
make install-conf

This gives you the latest development version. Leave out the "git checkout dev" to get the most recent stable release.

For more details see the User Guide in the doc directory. Special considerations for the Raspberry Pi are found in Raspberry-Pi-APRS.pdf

Linux - Using apt-get (Debian flavor operating systems)

Results will vary depending on your hardware platform and operating system version because it depends on various volunteers who perform the packaging. Expect the version to lag significantly behind development.

sudo apt-get update
apt-cache showpkg direwolf
sudo apt-get install direwolf

Linux - Using yum (Red Hat flavor operating systems)

sudo yum check-update
sudo yum list direwolf
sudo yum install direwolf

Macintosh OS X

Read the User Guide in the doc directory. It is more complicated than Linux.

If you have problems, post them to the Dire Wolf packet TNC discussion group.

Join the conversation

Here are some good places to ask questions and share your experience:

The github "issues" section is for reporting software defects and enhancement requests. It is NOT a place to ask questions or have general discussions. Please use one of the locations above.

Comments

Connected Data from AGWPE client not sent

When an AGWPE client requests to send 5 data packets via connected AX.25, Direwolf sends only 4 of them. This problem occurs with Direwolf version 1.5 Beta (Jan 8 2018), but doesn't occur with Direwolf version 1.4. The problem doesn't occur when sending fewer frames.

To reproduce the problem, I requested to send 5 frames via an AX.25 connection with MAXFRAME 2. Direwolf sent 2 frames, received an acknowledgement (I cmd, n(r)=2), sent 2 more frames, received an acknowledgement (RR res, n(r)=4) and did not send more frames. After a long delay, the remote station sent a DISC.

I run Direwolf on Windows XP SP 3. The AGWPE client is Outpost Packet Manager version 3.2.0 c103.

opened by jmkristian 28

Segfault when -p flag used

I'm just getting in to APRS and I've hit a problem. Perhaps the shell output is the best way to demonstrate:

Ξ ~ → direwolf
Dire Wolf version 1.3
Includes optional support for:  gpsd

Reading config file direwolf.conf
Audio device for both receive and transmit: default  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate, DTMF decoder enabled.
Note: PTT not configured for channel 0. (Ignore this if using VOX.)
Ready to accept AGW client application 0 on port 8000 ...
Use -p command line option to enable KISS pseudo terminal.
Ready to accept KISS client application on port 8001 ...
^C
QRT
Ξ ~ → direwolf -p
Dire Wolf version 1.3
Includes optional support for:  gpsd

Reading config file direwolf.conf
Audio device for both receive and transmit: default  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate, DTMF decoder enabled.
Note: PTT not configured for channel 0. (Ignore this if using VOX.)
zsh: segmentation fault (core dumped)  direwolf -p
↑139 ~ →

OS: Arch Linux Compiled from latest source with

git clone https://github.com/wb2osz/direwolf/
make
sudo make install

opened by virtualdxs 25

Audio output data underrun in Linux
When using either Direwolf 1.5 or the latest master in Linux, an audio output data underrun occurs when transmitting. This does not occur in Windows

OS: Arch Linux

Rig: FT-818

Direwolf versions: 1.5, master

Alsa audio
opened by minorsecond 14
Direwolf terminal blinking.
Hello, I am actually creating a Digipeater using Direwolf on a Raspberry Pi 2. Once Direwolf is installed, when the terminal starts, Direwolf display is blinking.

Here is how I have installed Direwolf on my RaspberryPi2:

I flashed Raspbian (Raspbian Buster with desktop) on the SD Card.

Then I open a terminal and I did sudo apt-get update and sudo apt-get upgrade.

To install Direwolf, I I have used the following command in a terminal:

cd ~
git clone https://github.com/wb2osz/direwolf
cd direwolf make sudo make install make install-conf

After, when I click on the shortcut to start Direwold, the terminal is blinking. I have the same result blinking like shown here [https://github.com/wb2osz/direwolf/issues/215]

The only way found to stop this blinking problem, is to start Direwolf in black and white following theses steps:

Creating a shortcut of Dire Wolf icon on the desktop

Creating a file direwolf.sh in /home/pi with -t 0 at the end:

#!/bin/bash cd /home/pi/Desktop lxterminal -e direwolf -t 0

Creating a repertory autostart in /home/pi/.config

In the autostart repertory, creating a file named direwolf.desktop with in it:

[Desktop Entry] Type=Application Name=Journal Exec=lxterminal -e ./direwolf.sh Name[fr_FR]=direwolf

I have read the issue subject posted here before, but no solution given actually works to solve the problem. It would be great to have the Direwolf terminal in colour withtout blinking.

Could anyone help me to solve this problem? Thank you very much in advance;
opened by F4FVI 12
Invalid Transmit Channel

I am running Dire Wolf in Jessie on a RPi. Works great. I'm using it with packlink as well as simply connecting with axcall.

However, when it initially starts up, the first two transmit attempts result in "Invalid Transmit Channel" errors. The third transmit attempt always works and then all subsequent attempts work.

What am I doing wrong?

Thanks, David

opened by dhchenault 12
IGate Stats to Telemetry Data

Hello.

First off, great application! I am using it as a RX IGate on a Raspberry Pi.

My question, I see that the IGate module has stat counters (line 282 to 315 in igate.c). Is there a way to send those stats along with the PBEACON of the IGate?

I see the TODO on line 284 already so I am guessing this is more of a feature request.

Thank You.

opened by kernworks 11
direwolf dev branch will not build with gpsd 3.20

Using this version of direwolf on 1/06/2020 wget https://github.com/wb2osz/direwolf/archive/dev.zip Direwolf will not build with: gpsd -V gpsd: 3.20 (revision 3.20)

[ 29%] Building C object src/CMakeFiles/gen_packets.dir/gen_packets.c.o /usr/local/src/direwolf-dev/src/dwgpsd.c:65:2: error: #error libgps API version might be incompatible. #error libgps API version might be incompatible.

[ 36%] Building C object src/CMakeFiles/atest.dir/dwgpsd.c.o /usr/local/src/direwolf-dev/src/dwgpsd.c:65:2: error: #error libgps API version might be incompatible. #error libgps API version might be incompatible.

opened by n7nix 10
pdf files should be generated based on some marked up format

The current set of pdf's provided as docs do not allow for copy/pasting of text to and from. These docs should be generated based on markup in the git repo, rather than just added to the repo as PDF's.

If text-based source is available, I'm willing to work on the "translation" into marked up documents, and the build scripts to generate various formats.

opened by coreyreichle 10
cmake test failures on s390x Fedora 33 and 34
Direwolf 1.6 tag, building on s390x architecture on Fedora 33 and rawhide (will be F34) fails 'cmake test' with a buffer overflow detected. Build succeeds on s390x on Fedora 32, and on all other architectures of F32-34. Test #7 (enctest) has the failure.

Fedora rawhide (future F34) https://koji.fedoraproject.org/koji/buildinfo?buildID=1636157 Fedora 33 https://koji.fedoraproject.org/koji/buildinfo?buildID=1636158 Fedora 32 https://koji.fedoraproject.org/koji/buildinfo?buildID=1636159

While it's possible to ExcludeArch: s390x, and one could argue that no one sane would try running direwolf on a mainframe, it's often the case that these failures are latent on other architectures when detected on one.

From the build.log files of the rawhide build:

Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.wGau2O

umask 022

cd /builddir/build/BUILD

cd direwolf-1.6

cd s390x-redhat-linux-gnu

/usr/bin/ctest --output-on-failure --force-new-ctest-process -j3 Test project /builddir/build/BUILD/direwolf-1.6/s390x-redhat-linux-gnu Start 1: dtest Start 2: ttest Start 3: tttexttest 1/20 Test #2: ttest ............................ Passed 0.00 sec Start 4: pftest 2/20 Test #3: tttexttest ....................... Passed 0.00 sec Start 5: tlmtest 3/20 Test #5: tlmtest .......................... Passed 0.00 sec Start 6: lltest 4/20 Test #6: lltest ........................... Passed 0.00 sec Start 7: enctest 5/20 Test #4: pftest ........................... Passed 0.00 sec Start 8: kisstest 6/20 Test #8: kisstest ......................... Passed 0.00 sec Start 9: pad2test 7/20 Test #9: pad2test ......................... Passed 0.00 sec Start 10: xidtest 8/20 Test #7: enctest ..........................Child aborted***Exception: 0.80 sec *** buffer overflow detected ***: terminated Start 11: dtmftest 9/20 Test #11: dtmftest ......................... Passed 0.02 sec Start 12: check-fx25 10/20 Test #12: check-fx25 ....................... Passed 0.01 sec Start 13: check-modem1200 11/20 Test #1: dtest ............................ Passed 5.00 sec Start 14: check-modem300 12/20 Test #10: xidtest .......................... Passed 6.00 sec Start 15: check-modem9600 13/20 Test #15: check-modem9600 .................. Passed 0.38 sec Start 16: check-modem19200 14/20 Test #16: check-modem19200 ................. Passed 0.48 sec Start 17: check-modem2400-a 15/20 Test #13: check-modem1200 .................. Passed 7.42 sec Start 18: check-modem2400-b 16/20 Test #17: check-modem2400-a ................ Passed 5.60 sec Start 19: check-modem2400-g 17/20 Test #19: check-modem2400-g ................ Passed 0.30 sec Start 20: check-modem4800 18/20 Test #18: check-modem2400-b ................ Passed 4.84 sec 19/20 Test #20: check-modem4800 .................. Passed 2.46 sec 20/20 Test #14: check-modem300 ................... Passed 11.99 sec 95% tests passed, 1 tests failed out of 20 Total Test time (real) = 17.00 sec The following tests FAILED: 7 - enctest (Child aborted) Errors while running CTest error: Bad exit status from /var/tmp/rpm-tmp.wGau2O (%check)

bug
opened by mdomsch 9
Support GeneralPlus USB sound cards

I was wanting to use the cmedia 108 PTT support so tried buying several usb sound dongles that I thought would be cmedia, but it seems that these devices now use a chip called GeneralPlus and I can't find a cmedia one. It would be good if these could be used for PTT too.

They seem to have USB idVendor=1b3f and idProduct=2008.

I have three different designs. All of them are COB (black blob on the PCB) so any extra GPIO lines cannot be accessed, if they even exist. They do have status LEDs though. I am hoping the LEDs can be controlled from the host and then these lines can be used for PTT.

opened by anm 9
dw stops collecting packets after 2-6 hrs, needs restart
All working fine in the first 2 to 6 hrs after startup, then eventually, dw still beaconing but packets are not longer collected and/or sent to the internet. A workaround for now is a timer that shuts down the device for 1 min every hour. Raspberry PI 3, wifi, RTL dongle. See attached a ps- al done:

whilst is no longer collects packet;

then after restart.
opened by vk2auj 8
Add AX.25 T3 timer to be configurable -- Add notes about other AX.25 parameters to documentation

Per our conversation: "A user configurable T3 could be added for completeness. . . . If you think it is important, throw it in the issues tracking so it does not get lost in the clutter."

Also a few reminders just for the documentation side for those users who come from hardware TNCs:

T2 timer: Add the description: " This parameters was removed from the AX.25 specification in v2.2. It is not needed if the protocol stack knows the modem data carrier detect status (which Direwolf does). See the Why-is-9600-only-twice-as-fast-as-1200.pdf document for more explanation.

FRACK: Mention in the User Guide that the max is 15

CHECK: Add this item with the description "Make a periodic check/poll to determine that a connection still exists. Dire wolf does not currently have an option (to configure) this. It is hardcoded to be 300 seconds."

SENDPAC, PACTIME, and CPACTIME: Add these items with the description "These parameters seem to be applicable only to the case where you are talking to a TNC in CONVERS (interactive transmit/receive) mode. Some specified character (typically enter) results in a packet being sent immediately. With both KISS and AGW, applications deal with complete packets, not individual characters so this does not apply to Direwolf's layer."

opened by dranch 0
Documentation Update: LPT for DCD and CON signaling
Greetings,

Please consider updating the User Guide to include the option of using the LPT port on Linux for DCD and CON LED/signaling in addition to the documented PTT. This was verified to work on a Debian 11 based distribution's Direwolf 1.6 package and is believed to work across all Linux distributions where an onboard LPT port is present.

This uses LPT 0 (Pin number 2) for PTT, LPT 1 (Pin number 3) for DCD and LPT 2 (Pin number 4) for CON signaling

PTT LPT 0 DCD LPT 1 CON LPT 2

It may also be worth noting that the CON signaling only appears to work when used via the AGWPE interface and not KISS. It is not believed to be a bug, but how the two protocols handle connections differently. It appears that multiple instances of direwolf can activate this signaling simultaneously on a single LPT port. In testing on one system, the LPT pins may have a current limiting resistor inline, potentially allowing direct connection of LEDs with no other components needed. This has not been widely tested so please proceed with caution.

73
opened by radar27 0
Bugfix Third Party Filtering
This addresses issue #428.

Filters like t/o would not work on 3rd Party packets since the payload was not inspected.

Also budlist filter was applied on the outgoing igate and not on the payload. Budlist has to be apply on the payload as we want to filter the source of the packet. Outgoing igate shall be considered as a digipeater. This si also corrected here.

Filters like t/{ still works same as before and will match any 3rd party packet.
opened by F4FXL 2
Stream 0: AX.25 Protocol Error E: DM received in state 4.

https://groups.io/g/direwolf/message/7010

Brian Blanchard Oct 7 #7010

I am using direwolf to connect to local packet nodes. I intermittently receive an error message "Stream 0: AX.25 Protocol Error E: DM received in state 4." which is followed by a disconnect from the node. I can always establish a connection. Once I enter any node command I get a disconnect. Any ideas what is going on?

I have tried adjusting audio levels, toggling the FIX_BITS on and off. If I make the connection with 'axcall' in the terminal I can hold the connection. The issue seems to occur with EasyTerm. I am wondering if I need to adjust 'kissparms' beyond the 'kissparms -c1 -p wl2k' command I am using?

Current setup is as follows... 2007 Apple iMac Linux Mint 20.2 Uma EasyTerm by UZ7HO-v0.49b (running on wine) Direwolf v1.6 Icom IC705

Uncommented lines from direwolf.conf

ADEVICE plughw:1,0 CHANNEL 0 MYCALL KJ7RNY MODEM 1200 PTT RIG 2 localhost:4532 AGWPORT 8000 KISSPORT 8001 FIX_BITS 1 IGTXLIMIT 6 10 TTPOINT B01 37^55.37N 81^7.86W TTPOINT B7495088 42.605237 -71.34456 TTPOINT B934 42.605237 -71.34456 TTPOINT B901 42.661279 -71.364452 TTPOINT B902 42.660411 -71.364419 TTPOINT B903 42.659046 -71.364452 TTPOINT B904 42.657578 -71.364602 TTVECTOR B5bbbddd 37^55.37N 81^7.86W 0.01 mi TTGRID Byyyxxx 37^50.00N 81^00.00W 37^59.99N 81^09.99W TTUTM B6xxxyyy 19T 10 300000 4720000 TTCORRAL 37^55.50N 81^7.00W 0^0.02N TTMACRO xx1yy B9xxAB166AA2B4C5B3B0A1yy TTMACRO xx2yy B9xxAB170AA3C4C7C3B0A2yy TTMACRO xxyyy B9xxAB180AA3A6C4A0Ayyy TTMACRO z Cz

This is my direwolf session that shows the error message. I connect to 'WTPBBS', enter command 'LL 5', then get a disconnect.

bblanchard33@iMac:~$ direwolf -p Dire Wolf version 1.6 Includes optional support for: gpsd hamlib cm108-ptt

Reading config file direwolf.conf Audio device for both receive and transmit: plughw:1,0 (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate. Ready to accept AGW client application 0 on port 8000 ... Ready to accept KISS TCP client application 0 on port 8001 ... Virtual KISS TNC is available on /dev/pts/6 Created symlink /tmp/kisstnc -> /dev/pts/6

Attached to AGW client application 0...

Ready to accept AGW client application 1 on port 8000 ... Attempting connect to WTPBBS ... [0L] KJ7RNY>WTPBBS:(SABME cmd, p=1)

KJ7RNY audio level = 61(27/27) [NONE] |||||_|__ [0.2] KJ7RNY>WTPBBS:(SABME cmd, p=1) [0L] KJ7RNY>WTPBBS:(SABME cmd, p=1)

KJ7RNY audio level = 62(27/28) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(SABME cmd, p=1) [0L] KJ7RNY>WTPBBS:(SABME cmd, p=1)

KJ7RNY audio level = 62(26/27) [NONE] ||||||||_ [0.3] KJ7RNY>WTPBBS:(SABME cmd, p=1) [0L] KJ7RNY>WTPBBS:(SABM cmd, p=1)

KJ7RNY audio level = 63(27/25) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(SABM cmd, p=1) [0L] KJ7RNY>WTPBBS:(SABM cmd, p=1)

KJ7RNY audio level = 62(27/26) [NONE] |||||_|__ [0.2] KJ7RNY>WTPBBS:(SABM cmd, p=1)

W7MOT-6 audio level = 56(27/15) [SINGLE] _:: [0.4] W7MOT-6>BEACON:WTANKS W7MOT-5 White Tanks, AZ<0x0d> Unknown APRS Data Type Indicator "W", HELO [0L] KJ7RNY>WTPBBS:(SABM cmd, p=1)

KJ7RNY audio level = 64(29/26) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(SABM cmd, p=1) [0L] KJ7RNY>WTPBBS:(SABM cmd, p=1)

KJ7RNY audio level = 63(28/26) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(SABM cmd, p=1) [0L] KJ7RNY>WTPBBS:(SABM cmd, p=1)

KJ7RNY audio level = 61(27/26) [NONE] |||||_|__ [0.2] KJ7RNY>WTPBBS:(SABM cmd, p=1)

WTPBBS audio level = 62(27/15) [NONE] __||||||| [0.5] WTPBBS>KJ7RNY:(UA res, f=1) Stream 0: Connected to WTPBBS. (v2.0)

WTPBBS audio level = 57(26/15) [NONE] ___|| [0.5] WTPBBS>KJ7RNY:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)[KPC3P-8.3-HM$]<0x0d>40491 BYTES AVAILABLE<0x0d>THERE ARE 107 MESSAGES NUMBERED 40-697<0x0d>ENTER COMMAND: B,J,K,L,R,S, or Help ><0x0d> [0L] KJ7RNY>WTPBBS:(DM res, f=1) [0L] KJ7RNY>WTPBBS:(DM res, f=1) [0L] KJ7RNY>WTPBBS:(RR res, n(r)=1, f=0)

KJ7RNY audio level = 63(28/27) [NONE] ||||||_ [0.3] KJ7RNY>WTPBBS:(DM res, f=1)

KJ7RNY audio level = 61(28/27) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(DM res, f=1)

KJ7RNY audio level = 61(26/24) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(RR res, n(r)=1, f=0) [0L] KJ7RNY>WTPBBS:(I cmd, n(s)=0, n(r)=1, p=0, pid=0xf0)LL 5<0x0d>

KJ7RNY audio level = 61(25/27) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(I cmd, n(s)=0, n(r)=1, p=0, pid=0xf0)LL 5<0x0d> [0L] KJ7RNY>WTPBBS:(RR cmd, n(r)=1, p=1)

KJ7RNY audio level = 63(28/26) [NONE] |||||||__ [0.3] KJ7RNY>WTPBBS:(RR cmd, n(r)=1, p=1)

WTPBBS audio level = 56(25/15) [NONE] __||||||| [0.5] WTPBBS>KJ7RNY:(DM res, f=1) Stream 0: AX.25 Protocol Error E: DM received in state 4. Stream 0: Disconnected from WTPBBS.

opened by wb2osz 0
Pulseaudio direct support

Hi, In the past, when I needed to use pulseaudio in direwolf I set it to the alsa pulse device. But now I'm on a system with only pulseaudio support (termux on Android). So it would be really cool, if someone could bake direct pulseaudio support into direwolf, so I can do packet radio on my smartphone. The only way to do packet radio on Android I know is, is aprsdroid, which the name implies, only support aprs and don't make ax. 25 directly available. If some motivation is needed, I would be happy to donate something for the time to implement this, maybe I even find some other's to donate too. Thx

opened by LaneaLucy 0

Releases(1.7-dev-A)

1.7-dev-A(Mar 16, 2021)
Version 1.7 -- Development Snapshot A -- March 2021

New Feature:

CM108/119 GPIO PTT is now available for Windows. Simply specify "PTT cm108" in the channel configuration section.

Notes:

This is a development snapshot that has not gone through the same amount of testing as a normal release. New features may be incomplete. Documentation may be lagging behind new functionality.

The Windows binary distribution is in the direwolf-1.7.0- *.zip files below. The Windows version is built for both 32 and 64 bit operating systems. Use the 64 bit version if possible; it runs considerably faster.
Source code(tar.gz)
Source code(zip)
direwolf-1.7.0-dev-A_i686.zip(21.19 MB)
direwolf-1.7.0-dev-A_x86_64.zip(21.29 MB)
1.6(Oct 28, 2020)
Version 1.6 -- October 2020

New Build Procedure:

Rather than trying to keep a bunch of different platform specific Makefiles in sync, "cmake" is now used for greater portability and easier maintenance.

README.md has a quick summary of the process. More details in the User Guide.

New Features:

"-X" option enables FX.25 transmission. FX.25 reception is always enabled so you don't need to do anything special. "What is FX.25?" you might ask. It is forward error correction (FEC) added in a way that is completely compatible with an ordinary AX.25 frame. See new document AX25_plus_FEC_equals_FX25.pdf for details.

Receive AIS location data from ships. Enable by using "-B AIS" command line option or "MODEM AIS" in the configuration file. AIS NMEA sentences are encapsulated in APRS user-defined data with a "{DA" prefix. This uses 9600 bps so you need to use wide band audio, not what comes out of the speaker. There is also a "-A" option to generate APRS Object Reports.

Receive Emergency Alert System (EAS) Specific Area Message Encoding (SAME). Enable by using "-B EAS" command line option or "MODEM EAS" in the configuration file. EAS SAME messages are encapsulated in APRS user-defined data with a "{DE" prefix. This uses low speed AFSK so speaker output is fine.

"-t" option now accepts more values to accommodate inconsistent handling of text color control codes by different terminal emulators. The default, 1, should work with most modern terminal types. If the colors are not right, try "-t 9" to see the result of the different choices and pick the best one. If none of them look right, file a bug report and specify: operating system version (e.g. Raspbian Buster), terminal emulator type and version (e.g. LXTerminal 0.3.2). Include a screen capture.

"-g" option to force G3RUH mode for lower speeds where a different modem type may be the default.

2400 bps compatibility with MFJ-2400. See 2400-4800-PSK-for-APRS-Packet-Radio.pdf for details

"atest -h" will display the frame in hexadecimal for closer inspection.

Add support for Multi-GNSS NMEA sentences.

Bugs Fixed:

Proper counting of frames in transmit queue for AGW protocol 'Y' command.

New Documentation:

AX.25 + FEC = FX.25

AIS Reception

AX.25 Throughput: Why is 9600 bps Packet Radio only twice as fast as 1200?

Ham Radio of Things (HRoT) - IoT over Ham Radio

EAS SAME to APRS Message Converter

Dire Wolf PowerPoint Slide Show

Notes:

The Windows binary distribution (direwolf-1.60- *.zip files below) now uses gcc (MinGW) version 7.4.0. The Windows version is built for both 32 and 64 bit operating systems. Use the 64 bit version if possible; it runs considerably faster.
Source code(tar.gz)
Source code(zip)
direwolf-1.6.0-413855e_i686.zip(21.15 MB)
direwolf-1.6.0-413855e_x86_64.zip(21.26 MB)
1.5(Oct 8, 2018)
Version 1.5 -- October 2018

New Features:

PTT using GPIO pin of CM108/CM119 (e.g. DMK URI, RB-USB RIM), Linux only.

More efficient error recovery for AX.25 connected mode. Better generation and processing of REJ and SREJ to reduce unnecessary duplicate "I" frames.

New configuration option, "V20", for listing stations known to not understand AX.25 v2.2. This will speed up connection by going right to SABM and not trying SABME first and failing.

New "NOXID" configuration file option to avoid sending XID command to listed station(s). If other end is a partial v2.2 implementation, which recognizes SABME, but not XID, we would waste a lot of time resending XID many times before giving up. This is less drastic than the "V20" option which doesn't even attempt to use v2.2 with listed station(s).

New application "kissutil" for troubleshooting a KISS TNC or interfacing to an application via files.

KISS "Set Hardware" command to report transmit queue length.

TCP KISS can now handle multiple concurrent applications.

Linux can use serial port for KISS in addition to a pseudo terminal.

decode_aprs utility can now accept KISS frames and AX.25 frames as series of two digit hexadecimal numbers.

Full Duplex operation. (Put "FULLDUP ON" in channel section of configuration file.)

Time slots for beaconing.

Allow single log file with fixed name rather than starting a new one each day.

Bugs Fixed:

Possible crash when CDIGIPEAT did not include the optional alias.

PACLEN configuration item no longer restricts length of received frames.

Strange failures when trying to use multiple KISS client applications over TCP. Only Linux was affected.

Under certain conditions, outgoing connected mode data would get stuck in a queue and not be transmitted. This could happen if client application sends a burst of data larger than the "window" size (MAXFRAME or EMAXFRAME option).

Little typographical / spelling errors in messages.

Documentation:

New document Bluetooth-KISS-TNC.pdf explaining how to use KISS over Bluetooth.

Updates describing cheap SDR frequency inaccuracy and how to compensate for it.

Notes:

Windows binary distribution now uses gcc (MinGW) version 6.3.0.

How to install on Linux:

git clone http://github.com/wb2osz/direwolf cd direwolf make sudo make install

How to install on Windows:

Download direwolf-1.5-win.zip (the file with "win" in its name) and extract the files. Run direwolf.exe in a command window. See User Guide for more details.

How to install on Macintosh OS X

Read the User Guide in the doc directory. It is a lot more complicated than Linux.

If you have any questions, post a message to the Dire Wolf packet TNC discussion group. I don't have a Mac and probably won't be able to help you. I rely on others, in the user community, for the Mac version support.
Source code(tar.gz)
Source code(zip)
direwolf-1.5-win.zip(18.80 MB)
1.5-beta4(Sep 12, 2018)

Fix for a different case of issue 132.
Source code(tar.gz)
Source code(zip)
direwolf.exe(2.59 MB)
1.5-beta3(Jul 2, 2018)
Version 1.5 -- Beta Test 3 -- July 2018

Bugs Fixed:

Issue 132 - Under certain conditions, outgoing connected mode data would get stuck in a queue and not be transmitted. This could happen if client application sends a burst of data larger than the "window" size (MAXFRAME or EMAXFRAME option).

New Features:

"NOXID" configuration file option to avoid sending XID command to listed station(s). If other end is a partial v2.2 implementation, which recognizes SABME, but not XID, we would waste a lot of time resending XID many times before giving up. This is less drastic than the "V20" option which doesn't even attempt to use v2.2 with listed station(s).

Notes:

Windows binary distribution now uses gcc (MinGW) version 6.3.0.

How to install on Linux:

git clone http://github.com/wb2osz/direwolf cd direwolf git checkout 1.5-beta3 make sudo make install

How to install on Windows:

Download direwolf-1.5-beta3-win.zip (the file with "win" in its name) and extract the files. Run direwolf.exe in a command window. See User Guide for more details.

How to install on Macintosh OS X

Read the User Guide in the doc directory. It is a lot more complicated than Linux.

If you have any questions, post a message to the Dire Wolf packet TNC discussion group. I don't have a Mac and probably won't be able to help you. I rely on others, in the user community, for the Mac version support.
Source code(tar.gz)
Source code(zip)
direwolf-1.5-beta3-win.zip(19.13 MB)
1.5-beta2(May 12, 2018)
Version 1.5 -- Beta Test 2 -- May 2018

Bugs Fixed:

Strange failures when trying to use multiple KISS client applications over TCP.

Better error messages.

How to install on Linux:

git clone http://github.com/wb2osz/direwolf cd direwolf git checkout 1.5-beta2 make sudo make install

How to install on Windows:

Download direwolf-1.5-beta2-win.zip (the file with "win" in its name) and extract the files. See User Guide for more details.
Source code(tar.gz)
Source code(zip)
direwolf-1.5-beta2-win.zip(19.87 MB)
1.5-beta(Jan 8, 2018)
New Features:

PTT using GPIO pin of CM108/CM119 (e.g. DMK URI, RB-USB RIM), Linux only.

More efficient error recovery for AX.25 connected mode. Better generation and processing of REJ and SREJ to reduce unnecessary duplicate I frames.

New configuration option, V20, for listing stations known to not understand AX.25 v2.2. This will speed up connection by going right to SABM and not trying SABME first and failing.

New application "kissutil" for troubleshooting a KISS TNC or interfacing to an application via files.

KISS "Set Hardware" command to report transmit queue length.

TCP KISS can now handle multiple concurrent applications.

Linux can use serial port for KISS in addition to a pseudo terminal.

decode_aprs utility can now accept KISS frames and AX.25 frames as series of two digit hexadecimal numbers.

Full Duplex operation. (Put "FULLDUP ON" in channel section of configuration file.)

Time slots for beaconing.

Allow single log file with fixed name rather than starting a new one each day.

Bugs Fixed:

Possible crash when CDIGIPEAT did not include the optional alias.

PACLEN configuration item no longer restricts length of received frames.

Little typographical / spelling errors in messages.

Documentation:

New document Bluetooth-KISS-TNC.pdf explaining how to use KISS over Bluetooth.

Updates describing cheap SDR frequency inaccuracy and how to compensate for it.

How to install on Linux:

git clone http://github.com/wb2osz/direwolf cd direwolf git checkout 1.5-beta make sudo make install

How to install on Windows:

Download direwolf-1.5-beta-win.zip (the file with "win" in its name) and extract the files. See User Guide for more details.
Source code(tar.gz)
Source code(zip)
direwolf-1.5-beta-win.zip(19.79 MB)
1.4(Apr 27, 2017)
Version 1.4 -- April 2017

New Features:

AX.25 v2.2 connected mode. See chapter 10 of User Guide for details.

New client side packet filter to select "messages" only to stations that have been heard nearby recently. This is now the default if no IS to RF filter is specified.

New beacon type, IBEACON, for sending IGate statistics.

Expanded debug options so you can understand what is going on with packet filtering.

Added new document Successful-APRS-IGate-Operation.pdf with IGate background, configuration, and troubleshooting tips.

2400 & 4800 bps PSK modems. See 2400-4800-PSK-for-APRS-Packet-Radio.pdf in the doc directory for discussion.

The top speed of 9600 bps has been increased to 38400. You will need a sound card capable of 96k or 192k samples per second for the higher rates. Radios must also have adequate bandwidth. See Going-beyond-9600-baud.pdf in the doc directory for more details.

Better decoder performance for 9600 and higher especially for low audio sample rate to baud ratios.

Generate waypoint sentences for use by AvMap G5 / G6 or other mapping devices or applications. Formats include

$GPWPL - NMEA generic with only location and name.

$PGRMW - Garmin, adds altitude, symbol, and comment to previously named waypoint.

$PMGNWPL - Magellan, more complete for stationary objects.

$PKWDWPL - Kenwood with APRS style symbol but missing comment.

DTMF tones can be sent by putting "DTMF" in the destination address, similar to the way that Morse Code is sent.

Take advantage of new 'gpio' group and new /sys/class/gpio ownership in Raspbian Jessie.

Handle more complicated gpio naming for CubieBoard, etc.

More flexible dw-start.sh start up script for both GUI and CLI environments.

Bugs Fixed:

The transmitter (PTT control) was being turned off too soon when sending Morse Code.

The -qd (quiet decode) command line option now suppresses errors about improperly formed Telemetry packets.

Longer tocall.txt files can now be handled.

Sometimes kissattach would have an issue with the Dire Wolf pseudo terminal. This showed up most often on Raspbian but sometimes occurred with other versions of Linux.

kissattach: Error setting line discipline: TIOCSETD: Device or resource busy Are you sure you have enabled MKISS support in the kernel or, if you made it a module, that the module is loaded?

Sometimes writes to a pseudo terminal would block causing the received frame processing thread to hang. The first thing you will notice is that received frames are not being printed. After a while this message will appear:

Received frame queue is out of control. Length=... Reader thread is probably frozen. This can be caused by using a pseudo terminal (direwolf -p) where another application is not reading the frames from the other side.

-p command line option caused segmentation fault with glibc >= 2.24.

The Windows version 1.3 would crash when starting to transmit on Windows XP. There have also been some other reports of erratic behavior on Windows. The crashing problem was fixed in in the 1.3.1 patch release. Linux version was not affected.

IGate did not retain nul characters in the information part of a packet. This should never happen with a valid APRS packet but there are a couple cases where it has. If we encounter these malformed packets, pass them along as-is, rather than truncating.

Don't digipeat packets when the source is my call.

Source code(tar.gz)
Source code(zip)
direwolf-1.4-win.zip(17.92 MB)
1.3(May 3, 2016)
This is the same as version 1.3 beta test with a few minor documentation updates. If you already have 1.3 beta test version, there is no need to replace it with this.

Changes since version 1.2.

New Features:

Support for Mac OS X.

Many APRStt enhancements including: Morse code and speech responses to to APRStt tone sequences, new 5 digit callsign suffix abbreviation, position ambiguity for latitude and longitude in object reports

APRS Telemetry Toolkit.

GPS Tracker beacons are now available for the Windows version. Previously this was only in the Linux version.

SATgate mode for IGate. Packets heard directly are delayed before being sent to the Internet Server. This favors digipeated packets because the original arrives later and gets dropped if there are duplicates.

Added support for hamlib. This provides more flexible options for PTT control.

Implemented AGW network protocol 'M' message for sending UNPROTO information without digipeater path.

A list of all symbols available can be obtained with the -S command line option.

Command line option "-a n" to print audio device statistics each n seconds. Previously this was always each 100 seconds on Linux and not available on Windows.

Bugs Fixed:

Fixed several cases where crashes were caused by unexpected packet contents:

When receiving packet with unexpected form of GPS NMEA sentence.

When receiving packet with comment of a few hundred characters.

Address in path, from Internet server, more than 9 characters.

"INTERNAL ERROR: dlq_append NULL packet pointer." when using PASSALL.

In Mac OSX version: Assertion failed: (adev[a].inbuf_size_in_bytes >= 100 && adev[a].inbuf_size_in_bytes <= 32768), function audio_get, file audio_portaudio.c, line 917.

Tracker beacons were not always updating the location properly.

AGW network protocol now works properly for big-endian processors such as PowerPC or MIPS.

Packet filtering treated telemetry metadata as messages rather than telemetry.

Known Problem:

The Windows version in direwolf-1.3-win,zip crashes when starting to transmit on Windows XP. There have also been some other reports of erratic behavior on Windows. The crashing problem has been fixed in direwolf-1.3.1-win.zip. The original 1.3-win.zip file will be removed after it has been confirmed that the 1.3.1-win.zip version solves the problem .

Source code(tar.gz)
Source code(zip)
direwolf-1.3-Beta-MacOSX.zip(186.49 KB)
direwolf-1.3.1-win.zip(14.43 MB)
1.2(Aug 4, 2015)
Version 1.2 -- June 2015

New Features

Improved decoder performance.
Over 1000 error-free frames decoded from WA8LMF TNC Test CD.
See "A-Better-APRS-Packet-Demodulator.pdf" for details.

Up to 3 soundcards and 6 radio channels can be handled at the same time.

New framework for applications which listen for Touch Tone commands and respond with voice. A sample calculator application is included as a starting point for building more interesting applications.
For example, if it hears the DTMF sequence "2_3_4#" it will respond with the spoken words "Twenty Four."

Reduced latency for transfers to/from soundcards.

More accurate transmit PTT timing.

Packet filtering for digipeater and IGate.

New command line -q (quiet) option to suppress some types of output.

Attempted fixing of corrupted bits now works for 9600 baud.

Implemented AGW network protocol 'y' message so applications can throttle generation of packets when sending a large file.

When using serial port RTS/DTR to activate transmitter, the two control lines can now be driven with opposite polarity as required by some interfaces.

Data Carrier Detect (DCD) can be sent to an output line (just like PTT) to activate a carrier detect light.

Linux "man" pages for on-line documentation.

AGWPORT and KISSPORT can be set to 0 to disable the interfaces.

APRStt gateway enhancements: MGRS/USNG coordinates, new APRStt3 format call, satellite grid squares.

Bugs fixed

Fixed "gen_packets" so it now handles user-specified messages correctly.

Under some circumstances PTT would be held on long after the transmit audio was finished.

Known problems

Sometimes writes to a pseudo terminal will block causing the received frame processing thread to hang. The first thing you will notice is that received frames are not being printed. After a while this message will appear:

Received frame queue is out of control. Length=... Reader thread is probably frozen. This can be caused by using a pseudo terminal (direwolf -p) where another application is not reading the frames from the other side.

Source code(tar.gz)
Source code(zip)
direwolf-1.2-win.zip(7.69 MB)
1.1(Aug 4, 2015)
Version 1.1 -- December 2014

New Features

Logging of received packets and utility to convert log file into GPX format.

AGW network port formerly allowed only one connection at a time. It can now accept 3 client applications at the same time.
(Same has not yet been done for network KISS port.)

Frequency / offset / tone standard formats are now recognized. Non-standard attempts, in the comment, are often detected and a message suggests the correct format.

Telemetry is now recognized. Messages are printed for usage that does not adhere to the published standard.

Tracker function transmits location from GPS position. New configuration file options: TBEACON and SMARTBEACONING. (For Linux only. Warning - has not been well tested.)

Experimental packet regeneration feature for HF use. Will be documented later if proves to be useful...

Several enhancements for trying to fix incorrect CRC: Additional types of attempts to fix a bad CRC. Optimized code to reduce execution time. Improved detection of duplicate packets from different fixup attempts. Set limit on number of packets in fix up later queue.

Beacon positions can be specified in either latitude / longitude or UTM coordinates.

It is still highly recommended, but no longer mandatory, that beaconing be enabled for digipeating to work.

Bugs fixed:

For Windows version, maximum serial port was COM9. It is now possible to use COM10 and higher.

Fixed issue with KISS protocol decoder state that showed up only with "binary" data in packets (e.g. RMS Express).

An extra 00 byte was being appended to packets from AGW network protocol 'K' messages.

Invalid data from an AGW client application could cause an application crash.

OSS (audio interface for non-Linux versions of Unix) should be better now.

Known problems

Sometimes kissattach fails to connect with "direwolf -p". The User Guide and Raspberry Pi APRS document have a couple work-arounds.

Source code(tar.gz)
Source code(zip)
direwolf-1.1-win.zip(7.20 MB)
1.0(Aug 4, 2015)
Version 1.0 -- May 2014

New Features

Received audio can be obtained with a UDP socket or stdin. This can be used to take audio from software defined radios such as rtl_fm or gqrx.

9600 baud data rate.

New PBEACON and OBEACON configuration options. Previously it was necessary to handcraft beacons.

Less CPU power required for 300 baud. This is important if you want to run a bunch of decoders at the same time to tolerate off-frequency HF SSB signals.

Improved support for UTF-8 character set.

Improved troubleshooting display for APRStt macros.

In earlier versions, the DTMF decoder was always active because it took a negligible amount of CPU time. Unfortunately this sometimes resulted in too many false positives from some other types of digital transmissions heard on HF. Starting in version 1.0, the DTMF decoder is enabled only when the APRStt gateway is configured.

Source code(tar.gz)
Source code(zip)
direwolf-1.0-win.zip(5.73 MB)