| |
ZL3AI > APRS 29.10.00 15:50l 205 Lines 7360 Bytes #999 (0) @ WW
BID : 34175_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 26, 3/9
Path: DB0MRW<DB0HOT<OK0PKL<OK0PPR<OK0PPL<OK0POK<9A0YRB<HA5OB<HA3PG<VE1DRG<
WA7V<KB7FRV<VK4WIT<ZS6RO<ZL3VML
Sent: 001027/1118Z @:ZL3VML.#80.NZL.OC #:45154 [Chch-NZ] FBB7.00g25 $:34175_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
digi'd when there are still digis due in the path. So if after a number
of tries the packet still doesn't get digipeated it will drop it since
the counter reaches zero and a next time sync packet will be coming up
soon. This could perhaps prevent outdated packets from being propagated
through the network.
> No, this is not "precise", but I would think that it would be easy to get
> within a second (with enough smarts in the software). Maybe a better
> question for APRS, is how-close-is-close-enough before we go re-inventing
> the wheel?
Personally I would say as good as possible. Not so much for current
applications as well for future applications that might rely on
resonably accurate timing. I think at this time we don't have any
applications that are that time critical that wouldn't allow a client's
time to slide for a minute or so. I think it will also be harder later
on to change the protocol if ever a more accurate time is needed than we
currently can anticipate.
>
> Just a thought?
> de WB4APR, Bob
73s,
Alex
----------------------------------------------------------------------
Subject: Re: aprssig digest: October 25, 2000
From: Mark Kempisty <kempisty@pav.research.panasonic.com>
Date: Thu, 26 Oct 2000 10:10:17 -0400
X-Message-Number: 10
In regard to Mike's (N0QBF) comment about what APRS has achieved, maybe
Mike and Bob B. can write a press release and send it out to the
national media and wire services. Get a little publicity and wouldn't
cost anything.
-- Mark N3GNW
----------------------------------------------------------------------
Subject: Re: Weather warnings
From: "Shirley and Frank Mondt" <n0sms@janics.com>
Date: Thu, 26 Oct 2000 11:58:00 -0500
X-Message-Number: 11
----- Original Message -----
From: David VanHorn <dvanhorn@cedar.net>
To: TAPR APRS Special Interest Group <aprssig@lists.tapr.org>
Sent: Tuesday, October 24, 2000 9:46 AM
Subject: [aprssig] Re: Weather warnings
>
> >
> > > They don't color my map in WinAPRS, so I guess it's time to update my
> > > counties folder. I have the OLD style county files, where do I find
> > the new?
>
> They won't color over precision mapping maps either. It's a "feature".
>
Click on the county of interest with precision Mapping and the county WILL
color and the type of warning Will show. It will give you the name of the
county. If the Alert/warning is nws office area wide
it will show the nws coverage area such as TUL or SGF. I don't know about
others but it does this for me. This is NOT on the precision mapping maps
however. The counties or coverage areas are drawn on a dos-like map on top
of PM. I have never seen this discussed on the sig but this is the way it
works for me.
Frank/n0sms
> ---
> You are currently subscribed to aprssig as: n0sms@janics.com
> To unsubscribe send a blank email to leave-aprssig-18700I@lists.tapr.org
> Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org
>
>
----------------------------------------------------------------------
Subject: Re: Weather warnings
From: David VanHorn <dvanhorn@cedar.net>
Date: Thu, 26 Oct 2000 12:17:13 -0500
X-Message-Number: 12
>
>Click on the county of interest with precision Mapping and the county WILL
>color and the type of warning Will show. It will give you the name of the
>county. If the Alert/warning is nws office area wide
>it will show the nws coverage area such as TUL or SGF. I don't know about
>others but it does this for me. This is NOT on the precision mapping maps
>however. The counties or coverage areas are drawn on a dos-like map on top
>of PM. I have never seen this discussed on the sig but this is the way it
>works for me.
I don't understand.
It sounds like you're saying it does work but it dosen't??
"Click on the county of interest with precision Mapping and the county WILL
color and the type of warning Will show."
"This is NOT on the precision mapping maps however."
I'm using precision mapping maps, because of their great level of detail.
It's very important that we be able to direct spotters and not hang them in
a dead end, which under some conditions could turn out to be a literal
meaning..
Clicking on the county would sort of work, but that's not how it's supposed
to work, and it's another thing for the VERY busy control op to remember to do.
Using WAPRS maps, the counties color automagically, as you would expect,
but that means having another window open, which isn't real workable
either. We don't all have 20 inch screens, and even when we do, it dosen't
handle multiple windows well.
Going in for round II with Dr Arnold today.
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: "Ciemon G0TRT" <g0trt@amsat.org>
Date: Thu, 26 Oct 2000 18:48:48 +0100
X-Message-Number: 13
I'll probably regret this, but I'll touch on a little bit of egg sucking.
Is everyone aware of the timezone letters that zulu is part of? In the UK
we're currently on alpha and Europe is on bravo, etc etc
I'm sure it wouldn't be that difficult for software to adjust themselves
depending on the callsign entered, but when did I last write any software
;o)
73....Ciemon G0TRT
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Bill Diaz <billdiaz@megsinet.net>
Date: Thu, 26 Oct 2000 13:11:59 -0500
X-Message-Number: 14
Ciemon,
I don't think that would be viable since it is possible to have callsigns
that span several time zones. For example, in the US the 9 call zone spans the
eastern and central time zones. Most people observe daylight savings time, but
some don't.
It is possible in the US to be licesned with any valid prefix and reside in
entirely different area. KC9's can be found in California for example.
Bill KC9XG
On Thursday, October 26, 2000 12:49 PM, Ciemon G0TRT [SMTP:g0trt@amsat.org]
wrote:
> I'll probably regret this, but I'll touch on a little bit of egg sucking.
>
> Is everyone aware of the timezone letters that zulu is part of? In the UK
> we're currently on alpha and Europe is on bravo, etc etc
>
> I'm sure it wouldn't be that difficult for software to adjust themselves
> depending on the callsign entered, but when did I last write any software
> ;o)
>
> 73....Ciemon G0TRT
----------------------------------------------------------------------
Subject: Re: [Re: Next Layer of Standards]
From: John Ackermann <jra@febo.com>
Date: Thu, 26 Oct 2000 14:43:05 -0400
X-Message-Number: 15
Re setting time over the air via APRS -- there are a couple of ideas in the
NTP (network time protocol) that might be usable in a very simplified form.
First, you have a big "flywheel" in the adjustment so you don't make massive
changes based on one time report, but rather build the adjustment over
several received signals. That helps deal with massive propagation delays.
You can also adjust via an average of multiple time sources and that also
minimizes the effect of outliers.
Second -- and most important -- compare multiple time sources and throw out
any that are "insane." If three or more stations transmit the time and one
of them is way off, the system would ignore that one. This can be useful
even if only two remote time servers are available, because you can use
Read previous mail | Read next mail
| |