News from the TARPN front.

I received a nice email from Tadd KA2DEW, there is a lot of development in the NinoTNC. Read the great news below.

We fixed the FTDI USB problem with the NinoTNC board by putting a USB-B socket on the PCB and a Microchip USB IC. This actually cut the parts cost by a few $. We’ll have the boards for sale on ETSY in April. Go to and search for TARPN. If the search doesn’t come up, then it isn’t listed yet. Our plan is to take orders in advance of shipping, and prime the pump with 200 boards ordering in early April with 3 weeks to get the boards into stock. At a time closer to ship time we’ll order programmed PIC CPUs with the latest firmware. When we get down to 50 or so in stock, we’ll order more. Because we’re running on out-of-pocket funding for the boards and CPUs, there may be some out-of-stock issues, but the price is right so hopefully people will smile and deal with it.

The new board is called the N9600A3. The last version was the A2, a black PCB with a 2-bit dip switch and the FTDI module on headers. The new board is the A3 blue PCB with USB B connector and a 4 bit dip switch. The new switches will be used to select more bit-rates. We’re not ready with anything new yet, but hopefully by the time the board ships? We’re likely to have 1200, 2400, 4800 and 9600 for FM and maybe some support for HF via SSB. Just like the A2 board, this one will come with IL2P Forward Error Correction mode which is a very efficient packet encoding providing Forward Error Correct in the same length packet as an AX.25 packet. (Full disclosure, as I understand it, packets with > 64 payload bytes will grow larger than AX.25 but small payloads result in shorter than AX.25 packets).

The NinoTNC A3 will come with a over-the-USB bootloader to update the firmware over USB, and we’ll be shipping a free Raspberry PI Raspbian application to boatload the TNC from a hex file. The hex file will be shipped for free one way or another. TARPN node ops will just do an UPDATEAPPS command on the TARPN scripts.

There is much software support to write for this which is not yet done. Our crack firmware and software teams are busy busy busy. Even though we’re not going to be ready with updated software in time we wanted to rush the A3 out there to solve the availability problem with the FTDIs. In addition we discovered that the tolerances for the Micro USB plugs and sockets are so bad that many people are breaking the FTDI modules plugging and unplugging. That’s not good. It’s easy to work-around but ugly. The A3’s USB-B connector is a much better deal.

See our news and info page starting at

Like before, we won’t be taking profit from this, and we’ll be selling the PCB + CPU for well under $10 on ETSY. Search on ETSY for TARPN. If it isn’t coming up, then we’re not ready to take pre-orders yet. It should be ready in early April. The news and info page will be updated when we get the store back up and when we have a clue about shipping this. We’ll also be posting a new A3 assembly link with access to the new bill of materials.

If you are interested in this, you should also sign up for the email reflector.

Tadd — KA2DEW

Direwolf <> Symek Tnc3s

144.800Mhz @ 1200Baud (Two tests one on 03-23 and one on 03-24 (rx only))

The first test I did was of course not entirely fair, different antennas were used and different transmitters/receivers. Now I made a setup with the same antenna and the same receiver, so with the same audio input.
First the setup, as a computer(if I haven’t lost it.some where) I use a Raspberry PI 2B+, as a sound card I use an Fe-Pi Audio Z V2. As a receiver I use a Realistic pro 2006. It is an old receiver but still works 100%. The antenna is a x50 from Diamond. Of course the Tnc3s from Symek, and Direwolf from John WB2OSZ. I use Kissutil from WB2OSZ, this allows me to connect to Direwolf and the Tnc3s as well as save the received Frames. This makes comparing easy/easier.

Now I have made two start files, one for Direwolf and one for the Tnc3s. I start these in different terminals. I do this manually, so there is a slight delay in starting up.


# Start kissutil on Direwolf kiss port 8001
# Let it run for 30 minutes and kill the process
# Start options "timeout -s 9 1800 ./"
# Kissutil for Direwolf save to /home/aprs/rec-direwolf
/usr/local/bin/kissutil-direwolf -o /home/aprs/rec-direwolf


# Start kissutil on the /dev/ttyUSB0 for the Symek Tnc3s
# Let it run for 30 minutes and kill the process
# Start options "timeout -s 9 1800 ./"
# Kissutil for the Tnc3s save to /home/aprs/rc-tnc3s
/usr/local/bin/kissutil-tnc3s -p /dev/ttyUSB0 -s 38400 -o /home/aprs/rec-tnc3s

I start the scripts with the option “timeout” now I can specify the time how long the script runs.
Example. “timeout -s 9 1800 ./”
In this comparison, both scripts run for 30 minutes. 1800 Second. Now it is time for the comparison.

With the command “ls -A | wc -l” the number of files in the directory are counted. (Frames received.)



Here you can see the difference between the received frames of the Tnc3s and Direwolf. There is a difference of 73 and 125 missed frames from the Tnc3s. I tried something with the reception levels of the Tnc3s. It is To soft – Ok – To hard, there is little difference between To soft and Ok and To hard.

I did some tests with the amount of calls received. Just for fun.

NinoTNC arrived.

A while ago I wrote something about the NinoTNC.

The NEW… NinoTNC form TARPN

There are some Dutch Radio amateurs who have ordered them.
Now I came across some pictures of a Dutch Radio Amateur who own and build the NinoTNC.


Direwolf <> Kpc9612

Today I made a comparison between Direwolf and a KPC9612. Now I have to say that it is difficult to compare. As the first set I use a KPC9612 and a Yaesu 7900 with an x30 as antenna and as software PinPoint Aprs Client for Windows. As the second set I use a Realistic pro 2006 scanner with an x50 as antenna and Direwolf. These antennas are at the same height.

Now I am very impressed with Direwolf, it seems that my KPC9612 is completely deaf. I clearly hear the packet signal but there is no decode. Unfortunately I don’t have two the same sets and two the same antennas to make the comparison better. But it is very clear here that Direwolf wins big.

Below you can see the difference between the setups. The Communication monitor is from PinPoint Aprs Client, the rest is from direwolf and some aprs parsing.


Okay, I know the comparison isn’t entirely fair. But for me Direwolf is the big winner.

Pinpoint Windows Aprs Client

I was playing with uiview32, but I was very bothered by the map that comes with uiview32. So I went looking for another Aprs client for windows. I ended up at PinPoint. In PinPoint you can choose from 40 different Map providers. Very nice.

I am satisfied with how it works. It is clear and fast. Only found out if at “Tools> Options” something changes you have to close the program and restart. There is also something disturbing, if you close the program and restart you have lost the received aprs messages. Very annoying.

Ax25-apps, Ax25-tools, Ax25-utils, Libax25

Please use the latest version, this prevents irritation and annoying things that you do not understand.

-rw-r–r– 1 pd9q pd9q 185677 Mar 8 14:25 ax25-apps-0.0.1.tar.gz
-rw-r–r– 1 pd9q pd9q 196284 Mar 8 14:25 ax25-apps-0.0.2.tar.gz
-rw-r–r– 1 pd9q pd9q 197901 Mar 8 14:25 ax25-apps-0.0.3.tar.gz
-rw-r–r– 1 pd9q pd9q 198064 Mar 8 14:25 ax25-apps-0.0.4.tar.gz
-rw-r–r– 1 pd9q pd9q 207347 Mar 8 14:25 ax25-apps-0.0.5p2.tar.gz
-rw-r–r– 1 pd9q pd9q 207624 Mar 8 14:25 ax25-apps-0.0.5.tar.gz
-rw-r–r– 1 pd9q pd9q 273846 Mar 8 14:25 ax25-apps-0.0.6.tar.gz
-rw-r–r– 1 pd9q pd9q 462058 Mar 8 14:25 ax25-apps-0.0.8-rc1.tar.gz
-rw-r–r– 1 pd9q pd9q 430456 Mar 8 14:25 ax25-apps-0.0.8-rc2.tar.gz
-rw-r–r– 1 pd9q pd9q 469313 Mar 8 14:25 ax25-apps-0.0.8-rc3.tar.gz
-rw-r–r– 1 pd9q pd9q 442172 Mar 8 14:25 ax25-apps-0.0.8-rc4.tar.gz
-rw-r–r– 1 pd9q pd9q 479590 Mar 8 14:25 ax25-apps-0.0.8-rc5.tar.gz

-rw-r–r– 1 pd9q pd9q 515474 Mar 8 14:25 ax25-tools-0.0.10-rc1.tar.gz
-rw-r–r– 1 pd9q pd9q 381575 Mar 8 14:25 ax25-tools-0.0.10-rc2.tar.gz
-rw-r–r– 1 pd9q pd9q 370079 Mar 8 14:25 ax25-tools-0.0.10-rc3.tar.gz
-rw-r–r– 1 pd9q pd9q 364332 Mar 8 14:25 ax25-tools-0.0.10-rc4.tar.gz
-rw-r–r– 1 pd9q pd9q 372851 Mar 8 14:25 ax25-tools-0.0.10-rc5.tar.gz
-rw-r–r– 1 pd9q pd9q 162320 Mar 8 14:25 ax25-tools-0.0.1.tar.gz
-rw-r–r– 1 pd9q pd9q 176989 Mar 8 14:25 ax25-tools-0.0.2.tar.gz
-rw-r–r– 1 pd9q pd9q 234032 Mar 8 14:25 ax25-tools-0.0.3.tar.gz
-rw-r–r– 1 pd9q pd9q 230243 Mar 8 14:25 ax25-tools-0.0.4.tar.gz
-rw-r–r– 1 pd9q pd9q 230243 Mar 8 14:25 ax25-tools-0.0.5.tar.gz
-rw-r–r– 1 pd9q pd9q 251941 Mar 8 14:25 ax25-tools-0.0.6.tar.gz
-rw-r–r– 1 pd9q pd9q 254019 Mar 8 14:25 ax25-tools-0.0.8.tar.gz

-rw-r–r– 1 pd9q pd9q 103151 Mar 8 14:25 ax25-lib-0.0.1.tar.gz
-rw-r–r– 1 pd9q pd9q 122941 Mar 8 14:25 ax25-lib-0.0.2.tar.gz
-rw-r–r– 1 pd9q pd9q 123970 Mar 8 14:25 ax25-lib-0.0.3.tar.gz
-rw-r–r– 1 pd9q pd9q 143265 Mar 8 14:25 libax25-0.0.10.tar.gz
-rw-r–r– 1 pd9q pd9q 231325 Mar 8 14:25 libax25-0.0.11.tar.gz
-rw-r–r– 1 pd9q pd9q 361613 Mar 8 14:25 libax25-0.0.12-rc1.tar.gz
-rw-r–r– 1 pd9q pd9q 332178 Mar 8 14:25 libax25-0.0.12-rc2.tar.gz
-rw-r–r– 1 pd9q pd9q 359045 Mar 8 14:25 libax25-0.0.12-rc3.tar.gz
-rw-r–r– 1 pd9q pd9q 335535 Mar 8 14:25 libax25-0.0.12-rc4.tar.gz
-rw-r–r– 1 pd9q pd9q 360123 Mar 8 14:25 libax25-0.0.12-rc5.tar.gz
-rw-r–r– 1 pd9q pd9q 122442 Mar 8 14:25 libax25-0.0.4.tar.gz
-rw-r–r– 1 pd9q pd9q 129510 Mar 8 14:25 libax25-0.0.5.tar.gz
-rw-r–r– 1 pd9q pd9q 130198 Mar 8 14:25 libax25-0.0.6.tar.gz
-rw-r–r– 1 pd9q pd9q 131177 Mar 8 14:25 libax25-0.0.7.tar.gz
-rw-r–r– 1 pd9q pd9q 264673 Mar 8 14:25 libax25-0.0.9.tar.gz

-rw-r–r– 1 pd9q pd9q 282655 Mar 8 14:25 ax25-utils-1.3.30.tar.gz
-rw-r–r– 1 pd9q pd9q 155821 Mar 8 14:25 ax25-utils-1.3.80.tar.gz
-rw-r–r– 1 pd9q pd9q 246854 Mar 8 14:25 ax25-utils-2.0.12c.tar.gz
-rw-r–r– 1 pd9q pd9q 204439 Mar 8 14:25 ax25-utils-2.0.12.tar.gz
-rw-r–r– 1 pd9q pd9q 359082 Mar 8 14:25 ax25-utils-2.1.22b.tar.gz
-rw-r–r– 1 pd9q pd9q 346153 Mar 8 14:25 ax25-utils-2.1.42a.tar.gz
-rw-r–r– 1 pd9q pd9q 344332 Mar 8 14:25 ax25-utils-2.1.42.tar.gz
-rw-r–r– 1 pd9q pd9q 21657 Mar 8 14:25 ax25utils.tar.gz

Uronode 2.11

Brian N1URO, has released Uronode 2.11 (Mar 03, 2020)


03/03/2020 v2.11
Changed node.h to reflect current version.

Note: The system has been behaving as best as it can be expected considering
it`s a front-end to the linux protocol stacks. As long as there can be an
ax# or sp# interface, it can attach to it and work the protocol(s) the user
wishes to use. There`s still the 2-line patch that the kernel maintainers 
need to add to ax25.ko so that netrom will continue to properly function
however that`s not the issue of URONode, it`s the kernel ax25 module.

Made a couple of changes in gateway.c where the color schema wasn`t properly
resetting the netrom prompt only in regards to aborting ping or a connect
request. This is now fixed.

Made changes in system.c where it wasn`t displaying the user being on IPv6
properly. While at it, I changed how it handles the user when they`re on
IPv4 in the lastlog and loggedin databases.

Changed user.c to reflect incoming session is via IPv6 which also fixes the
output of nodeusers so that instead of displaying ??????? it now shows that
Telnet6 is being used as the incoming protocol. This one was really getting
under my skin. Now I can rest in peace (as per QST 2/2020 haha!)

----------- Note on SystemD --------
In uronode.socket, you`ll notice the line:
This tells SystemD to listen on TCP socket 3694 for any IPv4 ONLY incoming
connection. If you wish to filter JUST your amprnet and IPv4 localhost
IPs make a line for each changing to and another for
your amprnet IP. This will by default filter any commercial IP requests
to URONode. If you want SystemD to try IPv6 *first*, don`t enter in any
IP schemas and just list the port number. SystemD by default appears to
use IPv6 prior to IPv4.

You can verify the above by running systemctl status uronode.socket:
systemctl status uronode.socket
● uronode.socket - URONode Server Activation Socket
   Loaded: loaded (/usr/lib/systemd/system/uronode.socket; enabled)
   Active: active (listening) since Mon 2016-03-07 15:30:39 EST; 6min ago
   Listen: (Stream)
 Accepted: 3; Connected: 1

----------- Wish-list: -----------
Original Development Information (aka Disclaimer): URONode was developed 
on an IBM eSeries 330 eServer with dual 1.2GHz CPUs The OS is Debian 
Linux 4 using kernel 2.4.27, libax25 v0.0.11, ax25-tools v0.0.8 and 
ax25-apps v0.0.6. This software comes with absolutely NO guarantees so 
crash n burn at your own risk. We all may be surprised and find out that 
it actually DOES something useful! URONode may not run 100% depending on 
environmental conditions specific to your system.

URONode is GLPv2 code, and tested by it`s main author on the following 
platforms: Raspberry Pi ver. B, Debian 7.7 on a Core-i3, Ubuntu 
12.0.4LTS on a Core-i3, Fedora ver. 21

Source Link