APRS-IS to RF messages not working

[James Lyles]

I had tx/rx aprs mesages working from RF to APRS-IS and back yesterday. I toggled the APRS-IS telemetry off and then back on today and then wrote a bash script to autostart APRX on my raspberry pi. Ever since then no APRS-IS to RF messages are getting out. The message is getting to APRX and then I see the following DISCARDING:

## produce 3rd-party AX.25 frames for transmit, and original source one for filtering:
.. parse_aprs() rc=OK  type=0x08 srcif=APRSIS tnc2addr='AB2WS-5>APDR12:}AB2WS-5>APDR12,TCPIP,AB2WS-10*::AB2WS-7  :test from andriod 3{7'  info_start='}AB2WS-5>APDR12,TCPIP,AB2WS-10*::AB2WS-7  :test from andriod 3{7'
History entry for receiving call 'AB2WS-7' from RADIO is recent enough.  KEEPING.
History entry for sending call 'AB2WS-5' from APRSIS is too new.  DISCARDING.
historydb_insert_heard(APRSIS) v=0xb6f290fc
DISCARDED! (filter_discard=0, discard_this=1)

My current configuration file is below.

#
mycall  AB2WS-10
myloc lat 3348.58N lon 08417.68W

<aprsis>
passcode    21495
#server    rotate.aprs2.net
#server   euro.aprs2.net
#server   asia.aprs2.net
server   noam.aprs2.net
#server   soam.aprs2.net
#server   aunz.aprs2.net
#
#filter "m/100"         # My-Range filter: positions within 100 km from my location
#filter "f/OH2XYZ-3/50"  # Friend-Range filter: 50 km of friend's last beacon position
</aprsis>

<logging>
pidfile /tmp/aprx.pid
rflog /var/log/aprx/aprx-rf.log
aprxlog /var/log/aprx/aprx.log
dprslog /var/log/aprx/dprs.log
erlangfile /var/run/aprx.state
</logging>

#<interface>
#   ax25-device   $mycall
#   #tx-ok        false  # transmitter enable defaults to false
#   #telem-to-is  true # set to 'false' to disable
#</interface>

<interface>
serial-device /dev/ttyAMA0  19200 8n1    KISS
callsign    $mycall    # callsign defaults to $mycall
tx-ok        true    # transmitter enable defaults to false
#telem-to-is    false    # set to 'false' to disable
</interface>

<beacon>
beaconmode both
cycle-size  30m
beacon interface $mycall   symbol "T&" $myloc \
                           comment "Fill-in Digi/Tx-iGate on RPi w/ TNC-Pi"
</beacon>

<digipeater>
    transmitter    $mycall

    <source>
    source        $mycall
    relay-type    directonly
    viscous-delay    5
    </source>

    <source>                # APRSIS source adds a TX-IGATE behaviour
    source        APRSIS
    relay-type    third-party  # Must define this for APRSIS source!
    msg-path    WIDE1-1
    viscous-delay    5    # Recommendation: 5 seconds delay to give
    </source>
</digipeater>

[Kenneth Finnegan]

It looks like someone else is beating you to the RF-gate. Try removing
the viscous-delay or look at your RF logs for the same packet coming
in from someone else.
--
Kenneth Finnegan, W6KWF
http://blog.thelifeofkenneth.com/

> --
> You received this message because you are subscribed to the Google Groups
> "Aprx software" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aprx-softwar...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[kg4pid]

I would make sure I was running the latest version of aprx as that fixed a number of problems. Isn't 'aprx 2.8.1-W6KWF-4-g22e4d79' the latest?

Max KG4PID

[9W2 CEH]

This is how do I make my IS-RF-IS aprs message using aprx.

<digipeater>
source>
#MSG From APRS-IS
transmitter 9W2CEH-3
<source>
source APRSIS
relay-type 3rd-party
via-path WIDE1-1 # default: none
msg-path WIDE1-1 # default: none
filter t/m
</source>
</digipeater>

[James Lyles]

Today I did a complete reinstall of Raspian and APRX. I compiled and installed from source (from this group) version: aprx_2.8.1-W6KWF-7-g777ce75_armhf.deb. Everything seems to be working properly except (1) that APRX starts with Pi reboot even when no script that I wrote calls it and (2) still no APRS-IS to RF messages. I get RF-RF messaging via the digipeater and RF-IS messaging is working. Not sure what the issue is or where to start investigating the problem. Any suggestions?

Thanks,

James

[James Lyles]

OK so I forgot to alter my aprx.conf file. The messaging is working from RF-APRS-IS and from the internet out to RF. I changed my <digipeater> section according to 9W2CEH. It's below and thanks everyone.
------------------------------------

<digipeater>
        transmitter     $mycall

        <source>
        source          $mycall
        relay-type      directonly
        viscous-delay   5
        </source>

        <source>                # APRSIS source adds a TX-IGATE behavior

        source          APRSIS
        relay-type      third-party  # Must define this for APRSIS source!

        via-path        WIDE1-1
        msg-path        WIDE1-1
        filter t/m

[9W2 CEH]

Glad to hear that James. :)

Bonar de 9W2CEH

[SM4VEY]

Hi All,

I seem to be suffering from the same issue, but here it seems that if I dont include an area filter in the APRSIS section of <digipeater> i'm not getting any IS->RF igateing.

Here's the relevant section of my digipeater config:

    <source>                # APRSIS source adds a TX-IGATE behaviour

       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.

       ratelimit      60 120      # default: average 60 packets/minute,

                                  #          burst max 120 packets/minute

        via-path        WIDE1-1

        msg-path        WIDE1-1

#        filter t/m

#    #  filter         a/la/lo/la/lo  # service area filter

        filter         a/60.10/11.00/58.2/14.2  # service area filter

 </source>

if I replace the "a" filter with the "t/m" filter i get the "DISCARDED! (filter_discard=0, discard_this=1)" and no IS->RF igate'ing.

Bug the source code, or int my thinking?

I've just installed the "aprx_2.8.2-15-gc580b31_armhf.deb" version i buildt now, but had the same issue with "stock" aprx "aprx_2.08.593-1_armhf.deb" from Finland.

73 de SM4VEY