Packet radio: Direwolf and pilinbpq

I’ve been playing around recently with setting up some packet radio software on the Raspberry Pi. The next thing I was interested in getting working was a BPQ32 node with BBS and Chat. G8BPQ’s instructions here are pretty easy to follow. What I got stuck on however was whether BPQ needed or used ax25, and apparently it doesn’t. So from the simplest direwolf and linbpq setup, you start direwolf, configure linbpq to point to Direwolf’s virtual kiss tnc serial port, and off you go.

I played around testing with 2 radios, one with Direwolf, linbpq and a Rigblaster connected to a Yaesu FT-60 HT, and the second, an Icom 880 connected with a Rigblaster Plug and Play to a desktop running Linux Mint, also using Direwolf. There was some random oddness wth connecting from one to the other, maybe because of the radios in close proximity, that turned out I just needed to increase default timeout settings. I set these both to the same in direwolf.conf and bpq32.cfg:

TXDELAY=300

TXTAIL=30

Once I’d added these (based on other suggested settings elsewhere in other people’s BPQ configs), then I was off and running. Looks good!

Packet Radio: sending unproto frames with Linpac (and other useful commands)

Thanks to David’s (KI6ZHD) reply to my post on the Linpac site, here’s a quick summary on setting up Linpac for unproto frames:

:unsrc yourcall
:undest "Yourname node1 node2 node-etc"

where node1 etc is your digipeater node list for routing your unproto packets between nodes that can hear each other.

:unproto the message

sends an unproto frame with the text specfied.

You can also open the F10 window and all text typed there gets sent as unproto frames.

unsrc and undest can be defined in the ~/Linpac/macros/init.mac file.

 

Packet Radio: AX25, Direwolf and Linpac on a Raspberry Pi

I’ve been playing around trying to get a working config for using Direwolf as a soundcard modem for packet radio on the Raspberry Pi. I’ve played with getting ax25 and Direwolf running on Ubuntu (see here), and then I tried to copy across what I’d learnt to the Pi (running Raspbian).

The trouble with a lot of this stuff is there’s not much in the way of docs (although the Direwolf docs are really good), so when things don’t work you either start trying stuff randomly or just get stuck. Anyway, here’s the combination I have working:

  • Raspberry Pi (v1 model B) running Raspbian
  • RigBlaster connected via USB, connected to an Icom 880h
  • soundlevels at around 3/4 via alsamixer
  • Per ax25 on CentOS here, I used the ax25 sources from VE7FET’s github repo, compiled and installed

Most of my steps are the same as from my prior experience getting Direwolf and Linpac working on Ubuntu, so follow those steps if you’re looking to get setup, and then I’ve summarized the differences here.

The VE7FET source when you ‘sudo make install’ creates config files to /usr/local/etc/ax25 and not the default location of /etc/ax25. I’m not sure if Linpac likes this, so per a posting I found somewhere, the quick way to keep everyone happy is just create a symlink:

cd /etc/
sudo ln -s /usr/local/etc/ax25 .

Edit the axports file, add a line like:

1 KK6DCT-2 38400 253 2 2m packet

‘1’ is the portname

On the Pi I did run into the kissattach issue getting the ‘error setting line discipline’ error as described in the direwolf docs. Per the docs, I used the second of the workarounds:

sudo /usr/sbin/kissattach /dev/ptmx radio 44.56.4.118

then:

sudo mkiss /tmp/kisstnc /dev/pts/5

where the /dev/pts/5 value is returned from the kissattach step.

At this point I’m ready to go:

‘call 1 kberr’ opens a connection to my nearest node (using port 1)

And also Linpac starts up (with linpac -m), can can connect the same there with ‘:c kberr’

At some point I should probably walk through these steps with a fresh Raspbian install to confirm I didn’t change anything else along the way that was key to getting this to work, but I think this summarizes the key points.

A few other helpful points:

  • in the Mac Terminal app by default, the Alt key doesn’t work so can’t do a Alt-X to exit Linpac. There’s a tip here to enable the Option key as Alt so you can use this to cleanly exit Linpac.