I use watchdog to monitor my RPI. Do services go offline or the RPI is not responding, watchdog kicks in and restart the system. Now I also want watchdog to watch my Linbpq. This is possible with watchdog, watchdog looks at a PID file. As far as I know, no PID file is created when starting Linbpq.

Now there is a possibility that when starting Linbpq with systemd a command can be given so that a PID file is created.

This is my linbpq.service file from systemd

This command creates a file, now it is possible that watchdog monitors linbpq.

At the end of my watchdog configuration file (/etc/watchdog.conf) I have added the following line.

Take a look at what happens when you stop Linbpq.

Yes the system is ReBoOtInG (I hoop)

Lcd Display on a PI

After a busy period, I finally have a bit  “Me Time” again.

David KI6ZHD (drache), has written a fantastic article about setting up and configuring a RaspBerry PI. This article also contains a piece about setting up an LCD display at the GPIO port of the Raspberry PI.

This can be read here.

I have ordered a 20×4 LCD display and an I2C LCD interface on the internet.The price was $ 14.96 including shipping costs. Nice.

Take the time to read this good article.

Xfbb interface with Linbpq

In bpq32.cfg add


This creates a DED Host mode TNC on device /home/pi/fbbded, accessible from the LinBPQ Node as Application 3. Change APPLMASK and APPLICATION line if you already use APPL 3


This allows uses to connect to FBB. You can add the usual Call, Alias and Quality if you want to be able to access FBB directly instead of via the Node.

Change APPLMASK and APPLICATION line if you already use APPL 3

In /usr/local/etc/ax25/fbb/port.sys#

# FBB7.0.8-beta8
#Ports TNCs
1 1
#Com Interface Adress (Hex) Baud
1 9 /home/pi/fbbded 9600
#TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 0 0 0 0 0 0 0 0 00/01 —- File-fwd.
1 4 1 1 250 2 1 10 00/15 DUWYL 145
# End of file.

This tells fbb to use /home/pi/fbbded as a DED Mode TNC.

Kantronics Kam xl stops transmitting

I came across some interesting in the BPQ32 news group about a Kantronics TNC`s.
On 10 May 2018 I also posted about this on my website.

Ray N3HYM runs into the following problems.

  1. Replace an mfj tnc with a new kam xl dual port
  2. Dual port kam xl seems to stop transmitting after 2 days or less of use. Have to cycle the power button to get it back to transmitting . I do see bpq32 sending to the kam when the sta  light flashes.
  3. All cables have troids on them , power, serial, radio interface cable.
  4. Kam xl has been set to 19200 abaud rate to computer.
  5. Turned off all other transmitting equipment to try an eliminate rf getting into kam xl.
  6. Kam is exactly where mfj tnc was on the bench. Mfj tnc did not have any issues.
  7. Running Windows 7 with bpq32 and tnc’s in kiss mode.

Also Don N7HPX is running into this issue with the KPC3+

The issue you describe is nearly identical to the one I had for a while when using a Kantronics KPC3+ in KISS mode.
The fault problem I observed was consistent and repeatable.
While the TNC was in KISS mode and attached to a real serial port it would hang-up and not transmit.
This would seemly happen randomly, however, the observed external factor that most often caused it was receiving a faint packet burst that was just below the decode threshold.

You could hear the packet tones and the low signal level static. After the freeze-up and from the BPQ32 Terminal console, I could send a specific connect command to the KPC3+ and note that the STA light would flicker but it would never actually transmit as it normally would.
At that point I knew I was stuck, yet again, and needed to power cycle the TNC.

I would assume that the KAM XL and the KPC3+ probably have the same KISS software routines.

Matt Ackerman said…

I was working with Kantronics support on this issue and I seem to have solved it by shorting the RTS and CTS pins together within my serial cable. (PINS 4/5 on DB25 and PINS 7/8 on DB9)
I simply ran a jumper between the two. This appears to be an issue with how the APRS software and/or the AX.25 stack controls the RTS pin and shorting the RTS and CTS together prevents the software from holding the RTS pin low.
If the RTS pin is at low voltage the KPC3+ will start buffering and does not get caught back up.
I have been running mine for several weeks without showing this behavior again.
Before I made the change it would happen after about 12 hours.

Jean-Jacques ON7EQ has try the mod.

After applying the mod with RTS/CTS, both on TNC and PC side, now running systems one week completely in-sync !

So sure this is a mod to be considered!

By default, the KPC3+ is configured for software flow control. In particular, when operating as digipeater, it is very likely that in the datastream sent to the TNC, soon or later there are frames containing ‘flow control characters’ sent – what will start the buffering!

It is therefore essential to completely disable the software flow control, this can be done by giving following commands:

  • START $00
  • STOP $00
  • XON $00
  • XOFF $00

Winlink Gateway HB9AK

As Winlink Gateway i`m using HB9AK from Switzerland on dail 7.050Mhz. HB9AUR (Martin) is the Operator (SysOp) of HB9AK.
I have test the system of Martin with Winmor, Ardop, Robust 300/600. I have a old AEA DSP2232 modem that can make Pactor 1, but i have some issues to get things going.

HB9AK is a big boy with many possibilities. Here a small list.

Technical details of HB9AK (JN36PV, 650 m asl):

QRGs (dial frequency): 3’613.0, 7’050.0, 10’144.4(NB), 14’108.9, 18’114.4, 21’113.5 (NB: narrow band only). Use USB for all QRGs. Center frequency is 1.5 kHz higher than dial frequency.

TRX1 (40m): KENWOOD TS-590S, dipole(N/S); Modes WINMOR, PACTOR(1-4), Robust Packet Radio, ARDOP, VARA

TRX2 (30m): KENWOOD TS-590SG, dipole(N/S); Modes WINMOR(500), PACTOR(1-2), ARDOP

TRX3 (20m): KENWOOD TS-590SG, dipole(N/S) or LogPer; Modes WINMOR, PACTOR(1-4), Robust Packet Radio, ARDOP, VARA

TRX4 (80m/17m/15m): KENWOOD TS-590S, 80m dipole, 17/15m fan dipole; Modes WINMOR, PACTOR(1-4), Robust Packet Radio, ARDOP, VARA

Technical details of HB9AK-1 (JN47LI, 1130 m asl):

TRX5 (10m): ICOM IC-706, vertical dipole; Modes WINMOR, PACTOR(1-4), Robust Packet, ARDOP, VARA

TRX6 (2m): MOTOROLA GM340, X-50; Mode Packet Radio AFSK 1200 Bd, BPSK 1200 Bd, BPSK 2400 Bd, QPSK 2400 bps, QPSK 3600 bps

Technical details of HB9AK-14 (JN46FS, 3020 m asl):

TRX7 (10m): KENWOOD TS-480SAT, Inv-V; Modes PACTOR(1-4), Robust Packet, WINMOR, ARDOP, VARA

I have contacted Martin, and we have been talking for a while about anything and everything. I asked him about his configuration, he found it no problem to share it.

 Very nice system. 


New project.


Bind ax25 interface to Direwolf

It can be easy to link an ax25 interface to Direwolf. This makes it possible to use RMSGateway, Uronode etc with Direwolf.
In this script Direwolf is started with the -p option. With the -p option a virtual tnc is created. /tmp/kisstnc.

With mkiss a kiss connection is made on the /tmp/kisstnc. With kissattach the PTY is connected to the ax25 interface.

Fist edit the file axports in /etc/ax25

Config the direwolf.conf file to set the right audio device and ptt port. Save file to /etc/ax25/direwolf.conf

Run the script

Let’s check if everything went well.

Try it out…

Now it’s possible to setup RMSGateway or Uronode of whatever you want.

Related NewsGroups

LinuxRMS RMSGateway
Direwolf Packet
Scs Tracker Modes
Digital Amateur Radio
Digital Radio
Vara Modem
RaspberryPi 4 Hamradio
Network 105
Pactor and Packet Group

AX25 Dual port TNC (kpc-9612)

Here is an ax25 script that I use to control the Dual port KPC-9612 with mkiss and kissattach.