Would not digipeat WIDE1 as intended.

[Heber Soto]

Hello

Sorry this is long but would like to include all data for the required assistance.

I am setting up a WIDE1 Fill In Digi, I have it working properly using Direwolf 1.6 but need additional function that APRX can provide.  I will continue to use Direwolf as the TNC for APRX.

Here is an APRS packet sending out from my HT and APRX is not Digipeating:

As received by DW-TNC:

NP4JN-7 audio level = 0(0/0)   [NONE]   ______|||

[0.7 15:17:45] NP4JN-7>APAT81-1,WIDE1-1,WIDE2-2:!1807.76N/06610.31W[/A=001342Saludos - Winlink RMS Gatewey Cayey

Position, Human, for Anytone. 81 for 878 HT

N 18 07.7600, W 066 10.3100, alt 1342 ft

Saludos - Winlink RMS Gatewey Cayey

As ingested  by APRX:

81313   NP4JN-13  R     NP4JN-7>APAT81-1,WIDE1-1,WIDE2-2:!1807.76N/06610.31W[/A=001342Saludos - Winlink RMS Gatewey Cayey

but it would not digipeate it.

Here is my configuration, your assistance would be appriciated.

Conf File:

mycall  NP4JN-13

myloc lat 1808.40N lon 06605.02W #ddmm.mmN lon dddmm.mmE

<aprsis>

passcode 18424

server    rotate.aprs2.net

filter "m/10"        # My-Range filter: positions within 100 km from my location

</aprsis>

<logging>

pidfile /var/run/aprx.pid

rflog /var/log/aprx/aprx-rf.log

aprxlog /var/log/aprx/aprx.log

</logging>

<interface>

   tcp-device   192.168.86.26  8001    KISS

   callsign     $mycall # callsign defaults to $mycall

   tx-ok        true    # transmitter enable defaults to false

   telem-to-is  true # set to 'false' to disable

</interface>

<beacon>

beaconmode  both

cycle-size  20m

beacon symbol "X#" lat "1808.40N" lon "06605.02W" comment "eXperimental digipeater" via "WIDE1-1,WIDE2-1"

beacon interface $mycall   symbol "X#" $myloc \

                           comment "eXperimental digipeater" via "WIDE1-1,WIDE2-1"

</beacon>

<digipeater>

    transmitter     $mycall

    <source>

        source          $mycall

#        relay-type     digipeated # default mode is "digipeated"

        relay-type      directonly      # default mode is "digipeated" WIDE1

        viscous-delay   0               # no viscous delay for RF->RF digipeating

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

        filter          -d/KP4IA-1

#       filter          -d/KP4IA-1/JAYUYA/MARQSA        # always block these

    </source>

    <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

#       filter          -b/KP4IA-1        # always block these

        via-path        WIDE2-1

        msg-path        WIDE2-1

    </source>

</digipeater>

[Bill Arthur]

I don't claim to be an aprx expert.
But if I was working on a digipeat problem I'd turn off the aprs-is interface to start.
You'll never know how your digipeat function works if you're feeding the data to aprs-is

[LAPADU-HARGUES Matthieu (GMAIL)]

Hi,

Bill is right and I think you should remove any filter too.

I could not see anything wrong in your config file, compared with the example in the manual.

73 de F4ACU

Matthieu

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/63b366f3-6fe8-4422-8b69-7d84a730ab88n%40googlegroups.com.

[Danny]

Hi,

Everything looks fine in your config. Try to change the ‘Destination Call Sign’ from ‘APAT81-1’ to ‘APAT81’ in your HT and try again. 

73 de PD2WR Danny

To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/CAEnKaf8WQwODevHBJZRM11nThOBy9037DUFvZCN%3Dfyp5rvMZvA%40mail.gmail.com.

[Heber Soto]

So an update.

I first removed the filters and it started working Digipeating WIDE1 as desired.

So if I want to filter one call sign that ingest into the RF a lot of traffic from the internet with errors and traffic not for this area I know as WIDE1 it would not retransmit those packet but if changed to WIDE1,WIDE2 then it will be sending out those packet and creating non need it additional RF traffic.

What would be the correct way to filter to limit the Digi WIDE1?

Thanks

[Patrick Domack]

I'm confused by what you are talking about here.

Digipeating works cause you defined a relay-type directonly, this will
digipeat rf to rf on anything it hears without going through a
digpeater, doesn't matter if they use WIDE1 or not

You have a negative filter, I remember something about negative
filters work funny and not as expected, but don't remember what, it's
been a long time.

You have the aprsis relay to rf, not digipeat, but 3rd party transmissions.

if you use WIDE at all, noesn't matter if it is WIDE1 or WIDE2,
another digipeater will retransmit them.

and you say you know as WIDE1 it would not retransmit (who would not
transmit?)
You either 3rdparty transmitted the packet or not, it has no bearing
on what path you put on it, the path doesn't matter to yourself, only
if others will retransmit your packet that came from aprsis.

>>>> *As received by DW-TNC:*

>>>> NP4JN-7 audio level = 0(0/0) [NONE] ______|||
>>>> [0.7 15:17:45]
>>>> NP4JN-7>APAT81-1,WIDE1-1,WIDE2-2:!1807.76N/06610.31W[/A=001342Saludos -
>>>> Winlink RMS Gatewey Cayey
>>>> Position, Human, for Anytone. 81 for 878 HT
>>>> N 18 07.7600, W 066 10.3100, alt 1342 ft
>>>> Saludos - Winlink RMS Gatewey Cayey
>>>>

>>>> *As ingested by APRX:*

>>>> 81313 NP4JN-13 R
>>>> NP4JN-7>APAT81-1,WIDE1-1,WIDE2-2:!1807.76N/06610.31W[/A=001342Saludos -
>>>> Winlink RMS Gatewey Cayey
>>>>
>>>> but it would not digipeate it.
>>>>
>>>> Here is my configuration, your assistance would be appriciated.
>>>>

>>>> *Conf File:*

>>> <https://groups.google.com/d/msgid/aprx-software/63b366f3-6fe8-4422-8b69-7d84a730ab88n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .

>>>
>>
>
> --
> 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.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/aprx-software/ebf9f0e9-7e48-4e8e-90bd-7b4a03bb9b2dn%40googlegroups.com.

[Ryszard Labus]

Hi.

It's not working as it should because there are errors in the configuration file.

In the digipeater section you did not specify which maximum path you support, you did not specify which path is traced and which is not.
You have set the digi source type as directonly, which means you will only repeat frames heard directly. For non-traced packets, there is no way to tell if a frame was repeated or is direct. Because you can send a frame with path WIDE2-2 after one repetition it will be WIDE2-1. But you can also send WIDE2-1 frame.
I have not analyzed the algorithm, but from my observation it seems that non-traced paths with unequal values in the path are treated as repeated.

And viscous-delay is set to zero. Just comment it out, because it does not work anyway

Look in the manual on page 10, section 2.3
https://thelifeofkenneth.com/aprx/aprx-manual.pdf


SQ9MDD

W dniu 07.07.2021 o 20:50, Heber Soto pisze:

To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/ebf9f0e9-7e48-4e8e-90bd-7b4a03bb9b2dn%40googlegroups.com.

[Mike Shepherd]

(And viscous-delay is set to zero. Just comment it out, because it does not work anyway)

I beg to differ. If set to zero then it is redundant. However, I use it on my implementation with a setting of 5 seconds and it works just fine.

Regards,

Mike,

Ve7prt.

[Heber Soto]

Ryszard

 

That was the trick.

 

Did this changes to my config:

 

        <trace>

                maxreq 1 # in range: 1 .. 7, default: 4

                maxdone 1 # in range: 1 .. 7, default: 4

                keys TRACE,WIDE,RELAY

        </trace>

        <wide>

                maxreq 1 # in range: 1 .. 7, default: 4

                maxdone 1 # in range: 1 .. 7, default: 4

                keys TRACE,WIDE

        </wide>

 

And its took the WIDE1 packet and it did Digipeated.

 

In via the TNC

NP4JN-7 audio level = 0(0/0)   [NONE]   ______|||

[0.7] NP4JN-7>APAT81-1,WIDE1-1,WIDE2-1:!1807.76N/06610.31W[/A=001342Saludos 73 - Winlink RMS Gatewey Cayey

Position, Human, for Anytone. 81 for 878 HT

N 18 07.7600, W 066 10.3100, alt 1342 ft

Saludos 73 - Winlink RMS Gatewey Cayey

 

In to APRX

3902    NP4JN-13  R     NP4JN-7>APAT81-1,WIDE1-1,WIDE2-1:!1807.76N/06610.31W[/A=001342Saludos 73 - Winlink RMS Gatewey Cayey

 

Out to RF

[0H] NP4JN-7>APAT81-1,NP4JN-13,WIDE1*,WIDE2-1:!1807.76N/06610.31W[/A=001342Saludos 73 - Winlink RMS Gatewey Cayey

 

If I am not confused did read that APRX really doesn’t care for the content if its WIDE1,WIDE2,etc its just looking at the “position” of the packet since its also degipeating this:

 

In via the TNC

CAYEYS audio level = 0(0/0)   [NONE]   ______|||

[0.7] CAYEYS>APMI06,WIDE2-2:@091906z1804.69N/06611.52W#KP4MSR Digi - Ya al aire digipeater de Vieques!! Welcome NP3MR-10 U=14.4V

Position with time, DIGI (white center), SQ3PLX http://microsat.com.pl/

N 18 04.6900, W 066 11.5200

KP4MSR Digi - Ya al aire digipeater de Vieques!! Welcome NP3MR-10 U=14.4V

 

In to APRX

3630    NP4JN-13  R     CAYEYS>APMI06,WIDE2-2:@091906z1804.69N/06611.52W#KP4MSR Digi - Ya al aire digipeater de Vieques!! Welcome NP3MR-10 U=14.4V

 

Out to RF

[0H] CAYEYS>APMI06,NP4JN-13,WIDE2-2*:@091906z1804.69N/06611.52W#KP4MSR Digi - Ya al aire digipeater de Vieques!! Welcome NP3MR-10 U=14.4V

 

Gracias

 

Heber NP4JN 73

 

From: Ryszard Labus
Sent: Thursday, July 8, 2021 7:54 AM
To: aprx-s...@googlegroups.com
Subject: Re: [Aprx] Re: Would not digipeat WIDE1 as intended.

 

Hi.

To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/ee629895-7259-ec87-0be0-50932c131cdc%40gmail.com.