How to Enable APRS and Automated BBS Mail Notifications in BPQ
If you run a BPQ packet node and want to bridge it into the global APRS network, you can easily activate its built-in APRS digipeater and IGate components. Even better, you can configure the BPQ Mail Server to automatically send an APRS text message to local operators the moment they receive a new private BBS message.
Here is a complete, step-by-step guide to updating your bpq32.cfg and linmail.cfg configuration files to get everything running.
Step 1: Update Your VHF RF Port in bpq32.cfg
Open your bpq32.cfg file. First, we need to ensure that BPQ’s native node digipeater is turned off on your local VHF user access port. This prevents the core node software and the new APRS engine from conflicting over control of your TNC.
Locate your VHF Port (it may be PORTNUM=2) and verify or update the following parameters before the ENDPORT statement:
; Inside your PORTNUM=2 block:
DIGIFLAG=0 ; Disables native node digipeating
DIGIPORT=0 ; Keeps native routing clear
(Note: Ensure there are no active UNPROTO lines inside this specific radio port block).
Step 2: Add the APRSDIGI Block to bpq32.cfg
Scroll down to the bottom of your bpq32.cfg file. Right below your ROUTES: section (and just above your *** and Applications lines), insert the following configuration block.
Be sure to replace the callsign, coordinates, and APRS-IS passcode with your own station data:
APRSDIGI
APRSCall=WS1EC-15
StatusMsg=Cumberland County EMA 145.05 MHz
Symbol=B ; Symbol (e.g., B for BBS, R for Rover)
Symset=/ ; Symbol set
LAT=4343.86N ; 22 High St, Windham, ME
LON=07025.09W ; 22 High St, Windham, ME
; Path and Beacon Controls
APRSPATH 2=APRS,WIDE1-1,WIDE2-1 ; Defines the packet path over RF for Port 2
Aliases=WIDE1-1,WIDE2-1 ; Stations to rebroadcast
BeaconInterval=30 ; Pushes station beacon to the map every 30 mins
; IGATE Params
ISHost=rotate.aprs.net
ISPort=14580
ISPasscode=22260
Digimap 2=2,IS ; Gates Port 2 (VHF 145.050 MHz) to the internet (APRS-IS)
***The Digimap 2=2,IS line is the magic here: it tells the IGate to take traffic heard on your local VHF RF port (Port 2) and push it out to the internet, and vice-versa.
Step 3: Enable Automatic BBS Mail Alerts in linmail.cfg
Now let’s configure the Mail Server to alert users on their APRS clients (like PinPoint APRS or APRSdroid) when they have a message waiting on the BBS.
Open your mail configuration file (named linmail.cfg on Linux/Raspberry Pi or BPQMail.cfg on Windows). Near the top of the file where the global mailbox settings are defined, add these three lines:
EnableAPRSAlerts=1 ; Activates automated APRS text notifications
APRSAlertInterval=60 ; Retry interval in minutes if the mail goes unread
APRSAlertPort=2 ; Sends the RF notification out on VHF Port 2
How It Works
- A new private message arrives on your BBS for a local ham (e.g.,
KC1JMH). - BPQ looks at its internal APRS tables to see if that callsign has been heard recently.
- If active, BPQ fires an APRS text message over VHF Port 2 saying: “You have new mail waiting on WS1EC BBS”.
- It will cleanly retry every 60 minutes until the user connects to the BBS via packet to read it!
Step 4: Save and Restart
Save both files and completely restart your BPQ service.
When the node fires back up, check your main console window. You should see a successful connection message to rotate.aprs.net. Within a few minutes, local RF traffic will start populating your APRS map, your red unacknowledged message text will clear up, and your automatic BBS email notifier will be fully armed!
Hopefully, this helps your blog readers get their nodes linked up. Let me know if you want to tweak any of the explanations or formatting before you publish it!