APRS-IS Filter
|
Soooooooo..
toggle quoted message
Show quoted text
I have to have a little fun here as I am intrigued by this discussion. If I'm reading this right, we can take a Weather Alert and feed that to APRS via YAAC? If true, I want to learn how...... And I know what's wrong with Dale's configuration. Its that he's a Chiefs fan.. Go Hawks!!!!!!! Hi HI...... 73 all of you, thank you all for threads here. Jamie Hughes WA7JH (360) 340-8886 -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Andrew P. Sent: Tuesday, September 24, 2024 7:27 PM To: [email protected] Subject: Re: [yaac-users] APRS-IS Filter The difference between the APRS-IS port filter and the supplemental Tx I-gate filter is as follows: The APRS-IS port filter controls what extra comes _into_ YAAC from the APRS-IS backbone. The supplemental Tx I-gate filter specifies what extra will be _forced_ to RF of what was received (assuming you are configured to allow Tx I-gating at all, which is a separate checkbox in the expert-mode configuration dialog). Which means that you can force all you want, but if it doesn't come in, it won't be there to be forced out. I hope that period after K0FJ* is a typo in writing your email, because it wouldn't match either of the callsigns. I hope you don't have the literal word "filter" in your YAAC filter expressions, because it is automatically injected prior to the expression you specify, and would cause a syntax error in the filter parsers (saying "filter filter m/600 ..."). Also, specifying the NWS stations as NWSGLD isn't going to work; the examples I have seen are messages GLDSVR (for severe weather from GLD). So you might want to just look for senders GLD* and DDR* (since neither of those starts are valid amateur radio callsign prefixes). Other suffixes to those three-letter NWS offices are things like TOR (tornado), SVS (severe weather), FLS (flood), etc. Also, that is _way_ too much to specify in a supplemental Tx filter, because you won't have enough bandwidth to force all that out to RF. A 600-kilometer radius of traffic shoved onto a 1200-baud channel, when normal RF range maxes out around 100km (unless you have some serious mountain digipeaters) and channel saturation can easily be much smaller than that? An Object sticks around for 3 retransmission intervals after you kill it, to send "I'm a dead Object" message (so other stations don't have to wait for it to timeout in 80 minutes). If you delete an Object from the Local Objects table without changing it to killed status first, then the received traffic (from digipeaters) will continue to sit there until your data purging time interval is reached (since you will never receive a "killed Object" report). Hope this helps. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Chiefsfan2 <chiefsfan2@...> Sent: Tuesday, September 24, 2024 8:10 PM To: [email protected] Subject: [yaac-users] APRS-IS Filter Back when I was using UI-View I use to gate wx warnings to RF from 2 od my area NWS offices. UI-View had a special area to add stations you wanted to gate. I would put NWSDDC* and NWSGLD* in that list and I would get the warnings. In Yaac I have my APR-IS filter in the port settings to fllter m/600 b/K0FJ*.W0RBO*/NWSDDC*/NWSGLD*/ t/nwt but am getting no alerts. I have the sane in the supplemental TX I-gate filter as well. I havent figured out the differnce between the two. Also I was testing sending out objects to certain locations. I then went to kill the object but it still shows on my screen although it isnt being sent out anymore? Thanks Dale |
Jamie H