| |
ZL3AI > APRDIG 10.08.03 11:15l 257 Lines 9132 Bytes #999 (0) @ WW
BID : 1760-ZL3AI
Read: GUEST
Subj: TAPR Digest, Aug 07, 1/3
Path: DB0FHN<DB0RGB<DB0FSG<DB0PV<DB0MRW<OK0PKL<OK0PPL<OK0NAG<9A0BBS<VK6BBS<
VK6HGR<ZL2BAU<ZL3VML
Sent: 030809/1327Z @:ZL3VML.#80.NZL.OC #:6247 [Chch-NZ] FBB7.00i $:1760-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Thursday, August 07, 2003.
1. Stupid Lyris
2. Re: PHGR and UIDIGI Part-1
3. Re: PHGR and UIDIGI Part-2
4. New Weather Service
5. Igate or digi eating periods!
6. Re: PHGR and UIDIGI Part-1
7. Re: aprssig digest: August 04, 2003
8. WinAPRS users question
9. MFJ-1270 A,B,C differences?
10. How NOT to do an Amber alert...
11. Re: How NOT to do an Amber alert...
12. Re: How NOT to do an Amber alert...
13. Re: Stupid Lyris
14. Re: How NOT to do an Amber alert... (followup)
15. Re: MFJ-1270 A,B,C differences?
16. What's PropNET? [was:PHGR and UIDIGI Part-1]
17. Re: How NOT to do an Amber alert... (followup)
18. Re: How NOT to do an Amber alert...
19. Re: PHGR and UIDIGI Part-1
----------------------------------------------------------------------
Subject: Stupid Lyris
From: Dave Kaplan <dkaplan@steffeninc.com>
Date: Thu, 07 Aug 2003 07:19:16 -0500
X-Message-Number: 1
Trying to send a message from Bob to the group and I get the below message:
Sorry, your message was not sent out to 'aprssig'.
Your message quotes too many continuous lines of a previous message.
You quoted 58 lines, and this mailing list is set to reject messages
which quote more than 45 continuous lines of a previous message.
Please resubmit your message, this time quoting fewer lines of the previous
message.
----------------------------------------------------------------------
Subject: Re: PHGR and UIDIGI Part-1
From: Dave Kaplan <dkaplan@steffeninc.com>
Date: Thu, 07 Aug 2003 07:27:10 -0500
X-Message-Number: 2
Earlier this week I had inquired about using PHGR with UIDigi at the remote
nodes I maintain. Below are Bob's comments and why I won't be implementing
this feature. Having to do this is two parts to fool Lyris. This is Part-1
Dave
WB0WNX
>X-Authentication-Warning: arctic.usna.edu: bruninga owned process doing -bs
>Date: Sun, 3 Aug 2003 13:02:34 -0400 (EDT)
>From: Bob Bruninga <bruninga@usna.edu>
>To: Dave Kaplan <dkaplan@steffeninc.com>
>Subject: Re: PHGR and UIDIGI
>
>Hummh. Seems DIGIs are the ideal places for PHGr.. Lemme think...
>Oh! Thats easy...
>
>1) We dont care how successful a DIGI is (we can hear it) We want to know
>what the statistics are for typical USERS down on the ground...
>
>2) Many people put variable beacon rates in their digis.
> One local packet (no hops) every 10 minutes
> One AREA packet (1 hop) every 20 minutes
> One Region packet (2 hops) every 30 minutes.
>
>This would totally mess up the statistics of the PHGr concept, UNLESS
>each of the beacons was different -OR- only one of them carried the
>PHGr...
----------------------------------------------------------------------
Subject: Re: PHGR and UIDIGI Part-2
From: Dave Kaplan <dkaplan@steffeninc.com>
Date: Thu, 07 Aug 2003 07:27:45 -0500
X-Message-Number: 3
Earlier this week I had inquired about using PHGR with UIDigi at the remote
nodes I maintain. Below are Bob's comments and why I won't be implementing
this feature. Having to do this is two parts to fool Lyris. This is Part-2
Dave
WB0WNX
>Neither of these is a good idea either, because APRSdos (and hopefully
>other codes) will ALERT the operator each time the Position Packet from a
>station CHANGES. (APRSdos sends out a "N" in CW). Also...
>
>Remember, APRSdos uses the "decaying" algorithm for all packets so that it
>treats NEW or CHANGED data differently from future copies of the same old
>data. Thus, in the past, DIGIS were requested to makes sure that all of
>their POSITION beacons were 100% identical.
>
>Unfortunately, this screws up the ability to use PHGr data on digis,
>unless:
>
>1) The digi only has ONE rate (and then PHGr works great) (but this then
>either makes the digi identification not often enough for local travelers
>or too often for the whole network in general)...
>
>2) The digi uses a DIFFERENT CALL for the "different" PHGr packet
>
>But now then this doubles the number of callsigns for every digi... and
>makes them have two objects at the same location...
>
>3) OR TRANSMIT the "probe" packet to an APRS "ALTNET" call which most
>software is supposed to ignore. THen it can retain the same call, but it
>will not appear as a "changed" or NEW position packet because it is
>ignored by all software that "honors" the ALTNET concept.
>
>In thise case, send those PROBE packets to the AX.25 callsign of PROBE...
>
>But then APRSdos users (and others that honor the concept of ALTNETS) wont
>see those packets and will miss the presence of that digi. But then we
>dont care about the statistic of an ALIGATOR digi anyway. We want PHGr to
>help us know what the network is doing to USER packets.
>
>Please share this with the others...
>
>de WB4APR, Bob
----------------------------------------------------------------------
Subject: New Weather Service
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 7 Aug 2003 08:54:38 -0400
X-Message-Number: 4
While perusing the XM web site, I came across this interesting new service
(not available yet):
http://www.xmradio.com/weather/index.html
Sounds like the hardware/software company doing this is:
http://www.wxworx.com/
At $xx/month, it isn't cheap, but for some people, it will be an answer to
their prayers!
Steve K4HG
----------------------------------------------------------------------
Subject: Igate or digi eating periods!
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 7 Aug 2003 12:20:02 -0400
X-Message-Number: 5
OK, here's a good one (and an example of why no matter how hard I try I
cannot compeletely divorce myself from the APRS IS, this came as a
complaint about findU not parsing a position correctly).
http://findu.com/cgi-bin/raw.cgi?call=W0MAF-1&time=1
Look closely at this, you will see many places where two packets with
identical (or almost identical) time stamps come in to the database:
20030807154245,W0MAF-1>APRS,RELAY,WIDE*,qAR,KC0CGH:@071540z385513N/0942282W_033/
001g003t080h63b10190e1w
20030807154245,W0MAF-1>APRS,RELAY,WIDE*,qAo,KA3NAM-10:@071540z3855.13N/09422.
82W_033/001g003t080h63b10190e1w
Someone has eaten the decimals on the top one (and since this cgi orders
with the most recent packets on top, the bad one is the one that findU
reports).
Anyone have any idea what is going on here?
Is KC0CGH on the list? His IGate is the most likely source of the
problem...the same error is occurring on other packets from his IGate. You
can see some of these yourself with the command line:
telnet 2.aprs.net | grep KC0CGH
Steve K4HG
----------------------------------------------------------------------
Subject: Re: PHGR and UIDIGI Part-1
From: Steve Jones <s.jones@rogers.com>
Date: Thu, 07 Aug 2003 16:46:10 -0400
X-Message-Number: 6
on 8/7/03 8:27 AM, Dave Kaplan at dkaplan@steffeninc.com wrote:
>>2) Many people put variable beacon rates in their digis.
>> One local packet (no hops) every 10 minutes
>> One AREA packet (1 hop) every 20 minutes
>> One Region packet (2 hops) every 30 minutes.
>>
>>This would totally mess up the statistics of the PHGr concept, UNLESS
>>each of the beacons was different -OR- only one of them carried the
>>PHGr...
All my digi's are setup with PHGr enabled on one 15 minute beacon. The
beacon's path is WIDE3-3 which shouldn't put too much of a burden on the
network.
I don't quite understand the problem with APRSdos. Does it treat different
position packets from the same station as new and alert the station operator
every time?
So a weather station broadcasting a position and weather beacon every 15
minutes (with changing weather) will alert the operator every time?
Seems kind of odd to me.
--
Steve <s.jones@rogers.com>
----------------------------------------------------------------------
Subject: Re: aprssig digest: August 04, 2003
From: "K.Deckert" <kdeckert@mercuryspeed.com>
Date: Thu, 7 Aug 2003 15:20:47 -0700
X-Message-Number: 7
We here in the north thompson valley of british columbia are on high alert
do to massive forest fire activity..and no power possible for a month or
more...the ve7rnt digi is back operational and may be one of the few links
to the outside world if the phones go down again...so keep an eye out for
us...and hope for the best.....ve7whk
----------------------------------------------------------------------
Subject: WinAPRS users question
From: "Jacob Tennant" <k8jwt@adelphia.net>
Date: Thu, 7 Aug 2003 21:16:09 -0700
X-Message-Number: 8
I have a question, I am running the latest version of WinAPRS registered
only connected to the first.aprs.net feed thru a cable modem. Sometime it
changes from my prefered maps to some other area of the US map? Just a
couple of minutes ago I was watching the Middle Atlantic States map and
suddenly it jumped to the California,Utah,Nevada map and flashed a circle
for a station find. I had not done anything to look for this station and
there is no stations listed in my find fields?
What's up???
Jake K8JWT
PS: I have a firewal running as well as ZoneAlarm Pro and nothing has
triggered either one.
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
