| |
ZL3AI > APRS 29.10.00 15:59l 209 Lines 7898 Bytes #999 (0) @ WW
BID : 34164_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 25, 6/6
Path: DB0MRW<OK0PKL<OK0PPR<OK0PRG<OK0POK<9A0YRB<HI8GN<KP4IG<7M3TJZ<IK1ZNW<
VE1DRG<WA7V<KB7FRV<VK4WIT<ZS6RO<ZL3VML
Sent: 001027/1048Z @:ZL3VML.#80.NZL.OC #:45151 [Chch-NZ] FBB7.00g25 $:34164_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
record, and the transmission of these messages were restricted to APRServers
then many of these problems would be avoided. However, if the time messages
were included in dumps from port 10151, it could cause trouble.
Time messages or record transmissions could be generated periodically, and only
after successfully obtaining a time update from a time server. Consideration
could also be given to including a timestamp record when an APRS client
application logs onto a server.
Bill KC9XG
>
> 73s,
> Alex
>
>
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: David VanHorn <dvanhorn@cedar.net>
Date: Wed, 25 Oct 2000 17:10:11 -0500
X-Message-Number: 30
At 05:55 PM 10/25/00 -0400, Alex wrote:
>Hi Bill,
>
>I'm not as concerned where the time information comes from, be it from
>the net, gps or wwv, as I am about the propagation of these time sync
>messages on RF. Propagation delays on 144.39 are enormous compared to
>the internet (although I doubt we have any time critical (as in split
>second) applications on APRS). Another problem is how a client
>application can verify that the time sync message it just received is a
>valid one (how do they expire?). Perhaps the earlier mentioned RFC can
>help us there.
Perhaps time sync packets don't get digi'd, or if they do, they go a single
hop only. That keeps the delay to a minimum. There's still problems, but
not as thorny.
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Bob Bruninga <bruninga@nadn.navy.mil>
Date: Wed, 25 Oct 2000 19:22:36 -0400 (EDT)
X-Message-Number: 31
> >Of course, IGATES could also use GPS receivers for time synchronization.
> Gaaak.. Expensive, and yet another cable, serial port, and...
Huhh? The 144.39 channel abounds with NMEA GPS data. Its there for the
taking. All APRS programs are capable of synchrnoizing to these existing
signals. Yes, the software must be smart enough to filter out the BAD
data, but this is easy to do. This will get to within a second or so.
Even better timing is possible with smarter software. THe minimum delay
through a TNC direct is X+T+D+R where X is the delay throgh the TNC, T is
the TXD delay, D is the unknown CD delay due to a busy channel and R is
the delay in your receiving/decoding system.
Through one hop is X+T+D+R+X+T+D+R etc...
The only unknowns are the D's, but, By watching enough packets, there will
always be one that experiences no Channel-busy delay. Thus by comparing
our clock with all NMEA strings and only taking the one with the least D,
we can itterate to the best solution.
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?
Just a thought?
de WB4APR, Bob
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Alex <kg4ecv@amsat.org>
Date: Wed, 25 Oct 2000 21:52:55 -0400
X-Message-Number: 32
Hello David,
I think that the number of involved digis should indeed be kept to a
minimum. That's why I was thinking of using a digi as a time server
rather than using an igate. Most people can hear a digi directly but not
necessarily an Igate. With every introduction of another hop the chance
that a packet gets dropped gets bigger and figuring out which time sync
packet is valid gets more tedious perhaps. I think the 1 hop maximum as
you proposed is probably best. Another reason to start out at a digi
rather than an Igate would be an emergency situation in which no
internet feed would be available. Just a thought.
73s,
Alex
David VanHorn wrote:
>
> Perhaps time sync packets don't get digi'd, or if they do, they go a single
> hop only. That keeps the delay to a minimum. There's still problems, but
> not as thorny.
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Mark Fellhauer <sparkfel@primenet.com>
Date: Wed, 25 Oct 2000 22:05:46 -0500
X-Message-Number: 33
I think the last time this came up there was some very vocal opposition to
any outside "tampering" with timesetting of an individual's PC.
When I pointed out a possible low-cost solution for time setting of
stand-alone digipeaters I was given a significant amount of static both on
the SIG and through private email. I even got email to the effect of "why
would you ever want the day/date/time of your KPC-3 in a stand-alone
digipeater to be accurate?" Other people accused me of playing with
fancy expensive toys (my proposed solution was targeted to cost less than
$100). And then others suggested their low-cost solution (of which they
have a financial interest in) - which was not low-cost at about $450 per
digi. Of course with a GPS engine now under $100 it renders using NIST
receivers moot at this point.... But this technology is steadily
dropping in price as radio timesetting clocks are dropping into the sub
$25.00 market.
Anyhow it's all fine and dandy to talk about implementing new features in
APRS, but a few vocal luddites can halt any progress. It also occurs to
me that current crop of APRS software out there has so many other features
already not working that we don't need to add any more code bloat. Let's
give the programmers some time to sort out some other problems, like the
ability to run a program for more than 15 minutes without an unhandled
exception. Unfortunately, I've given up on providing bug reports because
they don't seem to ever get addressed in any of the APRS software I've used.
73,
Mark
KC7BXS
----------------------------------------------------------------------
Subject: The APRS Network: Our Awesome Achievement
From: Mike Musick <mcmusick@anet-stl.com>
Date: Wed, 25 Oct 2000 23:41:45 -0500
X-Message-Number: 34
The wire reports should read something like: "MERE HOBBYISTS SUCCEED WHERE
BIG CORPORATIONS FAIL MISERABLY". Or maybe "SHOESTRING-BUDGET WIRELESS
NETWORK CONNECTS THOUSANDS".
What am I talking about? Wireless messaging and data interchange, that's what.
In brief, I have been looking to move the Palm version of APRS into the
commercial arena using the "wireless Internet". And you know what? The
commercials on TV are crap. There are at least a half-dozen different
connectivity standards, the best of 'em might cover 40 metro market cores
(and forget suburban and exurban coverage), connections are slow and
erratic, and the user cost is obscene.
In my frustration it finally dawned on me... I'm spoiled. Seriously,
seriously spoiled.
Compare this nonsense against what *WE* have put together on 144.390 -
local and wide area coverages, an Internet backbone (thanks, Steve!), a
common and consistent basic protocol (thanks, Bob!), a very fast and
flexible system that accommodates at least a half-dozen divergent uses, and
an "air time" cost of zero per byte. Nada. Free.
At least in the US, if there's a population center of over 50,000, there's
a 99.5% chance that it has respectable APRS coverage. And coverage on the
East Coast and California is almost seamless, and it's getting that way in
a lot of other places. Can any of the big wireless data companies come
close? Heck no - they're not even in the ballpark. I look around in awe and
amazement in the realization of what has actually been achieved.
Yes, we get mired in the details, and bicker, and lose sight of the big
picture. But that doesn't diminish the importance nor magnitude of the vast
success.
So let's pause a moment and raise our steins and glasses to each other in
toast, as we have done something truly, truly great.
Prost!
...mike/N0QBF
---
END OF DIGEST
Read previous mail | Read next mail
| |