N1SU aprx configuration
|
N1SU aprx configuration
Configuration and setup overview by Jason Buchanan
|
Overview
An example of the configuration I use is shown below. You should be able to use the example by using your call and coordinates.
I've also provided a crossband aprx.conf configuration file "diversity" receiver example.
Take note of these parameters in the example:
|
filter t/poimqunw
|
for radio source
filter includes the packet types you wish to TX
st are not included and will not be sent to TX
don't use -t/st on radio source (no hyphens)
|
filter -t/st
|
for APRSIS source
filter excludes the packet types you wish to TX
st are excluded and will not be sent to TX
|
msg-path WIDE2-2
via-path WIDE1-1
|
for APRSIS source
messages are sent WIDE2-2
via packets are sent WIDE1-1
|
Filter syntax is described at the page for APRS filter commands.
Don't forget to read the aprx manual for more details.
The aprx mailing list is a good place to ask aprx questions to a large audience.
On with the show, here's what I use:
aprx.conf
<![CDATA[
### N1SU example aprx.conf file
mycall N0CALL-2
myloc lat 3732.41N lon 11159.72W
<aprsis>
passcode 12345
server rotate.aprs2.net
filter "b/N0CALL* r/37.5401/-111.9952/50"
</aprsis>
<logging>
pidfile /var/run/aprx1200.pid
rflog /var/log/aprx/aprx1200-rf.log
aprxlog /var/log/aprx/aprx1200.log
</logging>
<interface>
ax25-device $mycall
# serial-device /dev/ttyAMA0 19200 8n1 KISS # if you use serial
tx-ok true # transmitter enable defaults to false
telem-to-is true # set to 'false' to disable
</interface>
<beacon>
beaconmode aprsis
cycle-size 14m
beacon symbol "I#" lat "3732.41N" lon "11159.72W" comment "N0CALL APRS Digipeater & TX IGate 144.390 http://n0call.com/aprs/"
</beacon>
<digipeater>
transmitter $mycall
<source>
source $mycall
relay-type digipeated # default mode is "digipeated"
viscous-delay 5 # (value - 1) + 0 to 2 seconds
ratelimit 60 120 # default: average 60 packets/minute,
filter t/poimqunw # everything but st
</source>
<source> # APRSIS source adds a TX-IGATE behavior
# Note that APRSIS will only be gated to RF
# if the destination station has been heard by
# this station within the last hour AND after
# aprx was started
source APRSIS
relay-type third-party # Must define this for APRSIS source!
viscous-delay 5 # Recommendation: 5 seconds delay to give
# RF delivery time make itself known.
# make it 0 or 5 - 5 matches token bucket refill
ratelimit 240 480 # I raise this above defaults due to bursts
filter -t/st
msg-path WIDE2-2 # gate TX with 2 hops for messages
via-path WIDE1-1 # gate TX with 1 hop for everything else
</source>
</digipeater>
]]>
Telemetry and status packets are not gated from APRSIS to RF in the example. Remove the
filter
lines if you need to gate those packets to RF.
aprx FAQ
| Issue | Reason |
aprx doesn't transmit a lot
aprx doesn't gate everything to RF
I want aprx to transmit everything
|
aprx is designed to filter duplicates
viscous-delay
is designed to reduce TX by waiting for another digipeater to transmit the packet before aprx transmits it
|
| What is viscous-delay? |
think of it as "CSMA for packets"
aprx listens for other stations to send the packet
if the packet is not resent then aprx will TX the packet after the delay period
it is designed to reduce TX by allowing other digipeaters to transmit the packet first
|
| What is a good viscous-delay value? |
5 seconds is a very polite value
TX will be approximately 4, 5, or 6 seconds
Calculated as (value - 1) + 0 to 2 seconds
|
More aggressive filtering
Here's some other ways to filter by call or string in the data field, assuming you don't want to use
filter -t/st.
<![CDATA[
# APRSIS source
filter -b/P1RAT
filter -u/D0DE/F3LLER
]]>
Or, use the
regex-filter
parameter:
<![CDATA[
# APRSIS source, and/or radio source
regex-filter source ^.*(P1RAT|D0DE).*$
regex-filter via .*(F3LLER).*$
regex-filter data .*(badword|dirtyword).*$
]]>
I avoid regex filters in aprx due to their unintuitive complexity and CPU cost.
I prefer the filter parameter instead.
I created a mailing list for APRS UHF discussion, to possibly coordinate a nationwide UHF frequency for APRS, and general APRS digipeater and internet gateway topics.
Enter your email address in the box below to join the group.
The aprx mailing list is a good place to ask aprx questions to a large audience.
N1SU aprx configuration - Updated: 12-Jul-19
(C) 2019 jsb@digistar.com
Back to APRS page
