| |
ZL3AI > APRDIG 19.09.06 22:12l 333 Lines 10315 Bytes #999 (0) @ WW
BID : D9GIS0HHA01C
Read: GUEST
Subj: [APRSSIG] Vol 26 #30, 1/3
Path: DB0FHN<DB0RGB<DB0MRW<DK0WUE<DB0RES<TU5EX<F3KT<IW2OAZ<IS0HHA
Sent: 060913/1810z @:IS0HHA.ISAR.ITA.EU [OpenBCM] OBcm1.06
From: ZL3AI @ IS0HHA.ISAR.ITA.EU (Tony)
To: APRDIG @ WW
X-Info: Sent with login password
R:060913/1746Z @:IS0HHA.ISAR.ITA.EU #:26341 [27509] FBB7.01.35 alpha
R:060831/0810z @:IW2OAZ.ILOM.ITA.EU $:8690-ZL3AI
R:060831/0808z @:ON0AR.#AN.BEL.EU $:8690-ZL3AI
R:060831/0705Z @:ZL2BAU.#87.NZL.OC #:1264 [Waimate] $:8690-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Filter port 14580 (Robbie, wa9inf)
2. RE: Filter port 14580 (Roger Bille)
3. RE: Filter feeds (AE5PL Lists)
4. Re: Filter feeds (Robbie, wa9inf)
5. Re: Filter feeds (Robbie, wa9inf)
6. Filter port (Robbie, wa9inf)
7. RE: Filter port (Roger Bille)
8. Re: Filter port (Robbie, wa9inf)
9. RE: Filter port (Roger Bille)
10. RE: Filter port (AE5PL Lists)
11. RE: Filter port (AE5PL Lists)
12. Re: Filter port (Robbie, wa9inf)
13. RE: Filter port (AE5PL Lists)
14. Re: ISS (tom burkhart)
15. RE: ISS (Ron Wenig)
16. Homebrew transmitter (Stephen Brown Jr)
17. Re: Homebrew transmitter (Josh Freeman)
18. Re: Homebrew transmitter (Curt, WE7U)
19. Re: Homebrew transmitter (Jason Winningham)
20. Re: Homebrew transmitter (Tim Smith)
21. Re: Homebrew transmitter (Stephen Brown Jr)
22. Re: Homebrew transmitter (Curt, WE7U)
23. Re: Homebrew transmitter (VE7GDH)
----------------------------------------------------------------------
Message: 1
Date: Mon, 28 Aug 2006 12:14:29 -0500
From: "Robbie, wa9inf" <mwrobertson_at_comcast.net>
Subject: [aprssig] Filter port 14580
Ok, I've changed my filter string to several different configurations, I
still am being fed Europe, Africa, Australia and South America stations,
as well as from all over the U.S.
I've rebooted the computer, makes no change. I guess some recent changes
in the filter software, Case sensitive, is the culprit or what?
What is my problem? Help!
Robbie
------------------------------
Message: 2
Date: Mon, 28 Aug 2006 19:28:47 +0200
From: "Roger Bille" <roger.bille_at_telia.com>
Subject: RE: [aprssig] Filter port 14580
Robbie,
First I don't understand what you trying to achieve with 2 of your filter
settings:
t/n/ilx*
The ilx* part is not defined in the spec. It should be a full callsign with
a third parameter with a distance. For example t/n/W9INF/500, this will pass
all NWS objects within 500 km from your last known position. What do you
want to get?
t/mkx*
Only m will match messages. km* doesn't have any meaning and is rejected.
What do you want?
When you request messages you will also get the position of the message
sender.
73 de Roger/sm5nrk
------------------------------
Message: 3
Date: Mon, 28 Aug 2006 12:39:35 -0500
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Filter feeds
Let's look at what your filter says:
>-----Original Message-----
>From: Robbie, wa9inf
>Posted At: Monday, August 28, 2006 11:44 AM
>Subject: [aprssig] Filter feeds
>
>filter t/n/ilx* t/mkx* b/K9KRW*/KB9YQX-1 -b/CW*
Pass all weather objects and messages from ilx*, all messages (and
associated posits), all packets from stations starting with K9KRW and
KB5YQX-1 but nothing from stations starting with CW.
Did you mean
filter t/n/ILX* t/n/MKX* b/K9KRW*/KB9YQX-1 -b/CW*
That said, I don't see using wildcards in the t filter as currently working
(I am seeing all weather with the above filter). I would recommend using a
filter of p/ILX/MKX to get all weather from those NWS offices.
73,
Pete Loveall AE5PL
mailto:pete_at_ae5pl.net
------------------------------
Message: 4
Date: Mon, 28 Aug 2006 13:03:48 -0500
From: "Robbie, wa9inf" <mwrobertson_at_comcast.net>
Subject: Re: [aprssig] Filter feeds
Hi Pete and Roger,
Yes, exactly what I was and have been using with no foreign stations
until today...
I wanted all weather related messages sent out from the Illinois weather
stations and Milwaukee weather stations with the prefix of MKX and ILX,
which until today was giving weather related objects, and as I
understood the filter, t/n meant I wanted type NWS messages as well?
Now that said, why were there no foreign stations before today?
I just learned now, that with the filter of t/n/ilx* /t/mkx* I get an OK
from the server with NO foreign stations. As soon as I added back my
-b/CW* to filter out Citizens Weather stations, I am now receiving the
foreign or unwanted stations! I take out the -b/CW* and they cease to
fill my screen??
Again, until today, this was not happening! I don't get why if I was
not doing it right, and was happy, why did things change? :-)
Until today the -b/cw* worked as described in the text file on Filters,
now I get the unwanted APRS-IS feed..
The above string of t/n/ilx*/mkx* has been working for a few of us
around the Chicagoland and Milwaukee area, I have not pooled them to see
how there stations are functioning...
I did try the t/n/ILX*/MKX*, but got the error until I changed it to
t/n/ILX* t/MKX*, separating the ILX* and MKX* So, something isn't
right.. I will do what I can figure out that will work, but explain why
the -b/CW* now allows foreign stations through now and it hadn't before
today please.. :-)
Robbie
------------------------------
Message: 5
Date: Mon, 28 Aug 2006 13:30:54 -0500
From: "Robbie, wa9inf" <mwrobertson_at_comcast.net>
Subject: Re: [aprssig] Filter feeds
Well, even without the -b/CW* in my filter string, I am still getting
position reports from everywhere!
My current filter is "filter t/n/ilx* t/mkx* b/K9KRW*/KB9YQX-1"
After all this time with the filter port, and not having this issue
until today, I just don't get why my string now causes this.. I got the
weather related messages, I didn't get the CW stations and I always saw
my friend in California wether he was driving around or just sitting at
home, :-) plus I used the f /k9krw*/50 to see the APRS activities around
him when he was driving up to Oregon.. Sometimes he is K9KRW-14, and
sometimes he is K9KRW-9, that's why the asterisk obviously..
Oh well, I know there was a change in how the software is now case
sensitive, and if that is not the reason I see all this activity now, I
guess I will have to revisit the filter.txt files and play around with
them. Again, until today, I've not seen this situation before..
Sorry I don't seem to be able to better explain the differences, I'll
just have to live with it and learn how to regain what I was happy with. :-)
Robbie
------------------------------
Message: 6
Date: Mon, 28 Aug 2006 13:43:36 -0500
From: "Robbie, wa9inf" <mwrobertson_at_comcast.net>
Subject: [aprssig] Filter port
This can't be true!!
Pete and Roger, I set the filter to p/ILX/MKX b/K9KRW*/KB9YQX* and
immediately my screen starts displaying stations from all over!!
Please check the filter status yourselves, and visit my webpage and see
for yourselves... I stopped the rotate.aprs2.net:14580 server, and for
the last couple hours been using aprswest.aprs2.net:14580 thinking it
would make a difference...
wa9inf.shacknet.nu/1452
I don not know what to do now...
Robbie
------------------------------
Message: 7
Date: Mon, 28 Aug 2006 21:33:36 +0200
From: "Roger Bille" <roger.bille_at_telia.com>
Subject: RE: [aprssig] Filter port
Robbie,
I agree with you that something is probably wrong. I will look into that as
soon as I can. The filter below should be the correct one. Your attempts
with the t (type) filters will not (should not) do what you want.
73 de Roger
------------------------------
Message: 8
Date: Mon, 28 Aug 2006 14:55:32 -0500
From: "Robbie, wa9inf" <mwrobertson_at_comcast.net>
Subject: Re: [aprssig] Filter port
Roger,
I am trying to understand why the t (type) as you say should not work
when I was using it before and it did the job that I needed, :-)
I quote from the filter.txt file on your web page..
Syntax: t/type
t/type/call/dist
call = call of a station or object
So, using t/n/ILX*/MKX*, I was following the guideline
t(type)/n(NWS)/call(ILX*)/call(MKX*)
That should work as well as p(prefix)/ILX*/MKX since n was a type as well
as the calls equaling a type.
I will survive, but it has me confused and I will cease from pestering the
sig... :-)
Robbie
------------------------------
Message: 9
Date: Mon, 28 Aug 2006 22:05:57 +0200
From: "Roger Bille" <roger.bille_at_telia.com>
Subject: RE: [aprssig] Filter port
Robbie,
Normally the t-filter will pass all packets with the type you specify. You
can limited this by a specific call (no wildcard) and a distance. For
example if you say:
t/n/WA9INF/500
You will get all NWS weather objects within a range of 500 km from your
last position packets. It assumes that WA9INF is sending positions on APRS.
The t-filter does not have the same syntax as e.g. b-filter where you can
list a number of calls (with and without wildcard) as arguments. The
t-filter is more like the f-filter in this context.
73 de Roger
------------------------------
Message: 10
Date: Mon, 28 Aug 2006 15:14:40 -0500
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Filter port
>-----Original Message-----
>From: Robbie, wa9inf
>Posted At: Monday, August 28, 2006 2:57 PM
>Subject: Re: [aprssig] Filter port
>
>I am trying to understand why the t (type) as you say should
>not work when I was using it before and it did the job that I
>needed, :-)
The previous version of javAPRSFilter did not hold exactly to the
specification found at
http://www.aprs-is.net/javaprssrvr/javaprsfilter.htm
>I quote from the filter.txt file on your web page..
>
>Syntax: t/type
>t/type/call/dist
>
>
>call = call of a station or object
>
>So, using t/n/ILX*/MKX*, I was following the guideline
>t(type)/n(NWS)/call(ILX*)/call(MKX*)
You read more there than is in the spec. It says t/type/call/dist That
means exactly that. Not t/type/call/call or call with wildcards.
>That should work as well as p(prefix)/ILX*/MKX since n was a
>type as well as the calls equaling a type.
The p filter does not use wildcards (it is, by definition, using an
implied wildcard). As to callsigns matching ILX or MKX for a prefix, I
think you will be hard pressed to fine non-NWS packets from stations
using those prefixes.
>I will survive, but it has me confused and I will cease from
>pestering the sig... :-)
73,
Pete Loveall AE5PL
mailto:pete_at_ae5pl.net
------------------------------
Read previous mail | Read next mail
| |
