Fill-In configuration

234 views
Skip to first unread message

LA5PPA

unread,
Mar 24, 2012, 2:46:17 PM3/24/12
to Aprx software
Hi, according to the manual page 14 it is possible to configure APRX
as a Fill-In digi so that it only digipeat WIDE1-1, if something else
comes up first like WIDE3-3 it will not digipeat.

I have test this on version: aprx_2.03test3.452-1_i386.deb5 but
it's not operating as a Fill-In, it digipeats everything

Any tips on "How to"

--
Lasse

Daniel Nelson

unread,
Mar 24, 2012, 2:52:19 PM3/24/12
to aprx-s...@googlegroups.com
Please post your configuration file so we can make sure you've got it set up properly.
-- 
Daniel Nelson
KJ6LVS

--
To unsubscribe from this group, send email to aprx-softwar...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/aprx-software

LA5PPA

unread,
Mar 24, 2012, 3:01:33 PM3/24/12
to Aprx software
Hi, this is my configuration on -3

mycall "MyCallSign"
<aprsis>
server srv.aprs.la 14580 # Norsk server
</aprsis>
<interface>
serial-device /dev/ttyS1 9600 8n1 KISS
tx-ok true # true = TX On / false = TX Off
</interface>

<digipeater>
transmitter $mycall # radio port

<source>
source $mycall
relay-type directonly
</source>

<source>
source APRSIS
relay-type third-party
via-path WIDE2-1
filter t/m
</source>

</digipeater>

<beacon>
beaconmode both
cycle-size 15m
beacon via WIDE2-1 \
symbol "I&" lat "5944.51N" lon "01002.03E" \
comment "PHG2400IGateTest 70cm (433.800) Mjondalen"
</beacon>

Daniel Nelson

unread,
Mar 24, 2012, 3:54:12 PM3/24/12
to aprx-s...@googlegroups.com
Well, that looks good to me. Have you tried it with other versions of the software?

-- 
Daniel Nelson

LA5PPA

unread,
Mar 25, 2012, 12:16:14 PM3/25/12
to Aprx software
No, but I can try one of the older versions and see if it works there

--
Lasse

LA5PPA

unread,
Mar 28, 2012, 2:00:38 PM3/28/12
to Aprx software
I'm now down to aprx_2.01.422-1_i386.deb5 on my -3 with the same
config file and its still digipeating when receiving WIDE3-3

--
Lasse

Angelo Rossi

unread,
Mar 28, 2012, 4:05:13 PM3/28/12
to aprx-s...@googlegroups.com
Hi....

Aprx, in this configuration, repeats all and only the packets, listening directly, so even wide7-7 WIDE4-4, etc. ...
Do not repeat frames that are passed through another digipeater.
To configure aprx as fill-in digipeater only repeats WIDE1-1, put maxreq and maxdone = 1,  or use the regex-filter and put all the possibilities of wide you do not want to pass. wide7-7 wide7-6 ...... wide6-6 wide6-5 .... etc.  


<source>
source     $mycall
relay-type directonly
<wide>
keys WIDE
maxreq 1
maxdone 1
<\wide>
</source>

 Try this configuration and let us know......

73 - Angelo - IW0QHA

2012/3/28 LA5PPA <div....@ebnett.no>
--
To unsubscribe from this group, send email to aprx-softwar...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/aprx-software



--
73 de Angelo - IW0QHA

LA5PPA

unread,
Mar 29, 2012, 4:24:59 PM3/29/12
to Aprx software
Thanks for the tips but... sorry It's not working, still digipeating
WIDE3-3
Maybe I have to upgrade again to latest version and try ?

--
Lasse

LA5PPA

unread,
Mar 30, 2012, 3:28:44 PM3/30/12
to Aprx software
I'm back on the latest version but it's still not working as a fill-in

--
Lasse

LA5PPA

unread,
Mar 31, 2012, 2:07:55 PM3/31/12
to Aprx software
An update....
Been doing a lot of testing today trying to solve my problem getting
APRX to work as a Fill-In, only digipeating WIDE1-1 package

Honestly I dont think APRX work this way at all but it will digipeat
on anything as the first station if no one else is digipeating the
same package within the viscouse time
Based on the Relay-type directonly is will only digipeat if it receive
a clean path from any statio without the * (star) in the path.
If the received path contain a *, then it is not directonly but via
another digipeater and APRX will not digipeate

relay-type directonly

Is my observation correct ?

Angelo Rossi

unread,
Mar 31, 2012, 5:56:08 PM3/31/12
to aprx-s...@googlegroups.com
Sure it is.
In this configuration only digipeats frames without star (*), and then frames that have not passed through another digipeater.
But, in my previous post I had written it. 

Have you tried to set maxdone and maxreq =1 , to digipeat only wide1-1???


73 - Angelo - IW0QHA


2012/3/31 LA5PPA <div....@ebnett.no>
--
To unsubscribe from this group, send email to aprx-softwar...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/aprx-software

LA5PPA

unread,
Apr 1, 2012, 3:31:54 AM4/1/12
to Aprx software
Hi, as I confirmed earlier, yes I tried that but it's not working

I tested the setting below on version aprx_2.01.422-1_i386 and
aprx_2.03test3.452-1_i386

<source>
source $mycall
relay-type directonly
<wide>
keys WIDE
maxreq 1
maxdone 1
</wide>
</source>

--
Lasse

Angelo Rossi

unread,
Apr 1, 2012, 4:34:44 AM4/1/12
to aprx-s...@googlegroups.com
OK...
try to test the regex-filter.... write on all the alias that you want no digipeat....

try it....

73 - Angelo - IW0QHA 

2012/4/1 LA5PPA <div....@ebnett.no>
--
To unsubscribe from this group, send email to aprx-softwar...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/aprx-software

LA5PPA

unread,
Apr 1, 2012, 11:49:27 AM4/1/12
to Aprx software
ok, this looks better :)

Added the following into the first <source> section and now it will
only digipeat on WIDE1-1

regex-filter destination WIDE3-3|WIDE3-2|WIDE3-1|WIDE2-2|WIDE2-1

Even if you use this filter it will Igate the station but not digipeat
so... I'm happy
(TX of messages is working)

Thank you Angelo

<digipeater>
transmitter $mycall
<source>
source $mycall
relay-type directonly
regex-filter destination WIDE3-3|WIDE3-2|WIDE3-1|WIDE2-2|WIDE2-1
</source>
<source>
source APRSIS
relay-type third-party
via-path WIDE2-1
filter t/m
</source>
</digipeater>


LA5PPA

unread,
Apr 1, 2012, 2:49:22 PM4/1/12
to Aprx software
Is there a ghost somewhere in this software?
After a couple of hours testing is suddenly started to digipeat on my
-8 again with WIDE3-3 settings
Nothing is changes, config the same...

--
Lasse
Reply all
Reply to author
Forward
0 new messages