| |
ZL3AI > APRS 25.10.00 06:36l 201 Lines 7786 Bytes #999 (0) @ WW
BID : 34107_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 22, 6/8
Path: DB0MRW<DB0RGB<OK0PPL<OK0POK<9A0YRB<VK6BBS<VK2CPG<VK2CZR<VK2IO<VK2GJB<
ZL2TZE<ZL2TZE<ZL2WA<ZL2BAU<ZL3VML
Sent: 001023/1111Z @:ZL3VML.#80.NZL.OC #:44475 [Chch-NZ] FBB7.00g25 $:34107_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
From: James Smith <k9apr@tawg.org>
Date: Sun, 22 Oct 2000 17:32:10 -0500
X-Message-Number: 20
Test
----------------------------------------------------------------------
Subject: Re: APRS and The New York City Marathon
From: Arte Booten <n2zrc@webspan.net>
Date: Sun, 22 Oct 2000 18:49:00 -0400
X-Message-Number: 21
Hi all,
Roger G. wrote:
>Do TPTB give a reason for their opposition ...
Yes. As Rich Amirault and I have discussed privately, The New York
City Marathon is a *very* public event. There are Police escorts. The
runners are preceeded by a dozen vehicles (three of which have hams in
them), one of which has the TV cameras. There's a helicopter above them
also.
New York City has street signs on every corner. We can see them on
Channel 11 when the camera is pointed in that direction. So we know ex-
actly where the lead male and lead female runners are virtually all the
time.
I've tried to sell to TPTB that these aren't the resources we'd be
tracking. There are precursor trucks and SAG busses and other moving
things that are more appropriate to the use of APRS. But the overriding
concern is that of the Net Control Trailer.
This trailer, which is actually IN Central Park, some 150 yards be-
fore the finish line, has about a dozen concurrent FM voice nets ...all
of which need as close to 100% reliablilty as can be. The sound of so
much as one little packet is unacceptable. And I don't blame them. We
deal with life-and-death situations sometimes. Not the place for any
distractions.
These Net Control Stations are busy! We have nearly 500 hams in-
volved in various aspects of the Marathon. The NCS's don't have time to
figure out how to use APRS, much less how to interpret what they see. I
would like to see APRS used in The New York City Marathon, but know that
it's not really necessary, nor would it particularly add information we
don't already have access to.
Maybe someday ... but not this year. 73
+----------------------------------------------------------------------+
|Arte Booten <n2zrc@arrl.net> AEC for Digital Services, NYC ARES/RACES|
|Riverdale, New York [FN30bu] !4052.71N/07354.06WNPHG5370/A=00240|
|Packet: N2ZRC@KB2VLX.#BRONX.NY.USA.NA HTX-202/RS Brick/KPC-3 6.0/X-510|
|PGP Key Fingerprint: D73E B889 C630 6F4A F31F 3083 56BD 0AAD 9996 3B03|
+----------------------------------------------------------------------+
----------------------------------------------------------------------
Subject: Re: Igate / Findu "Hyper-Jump" problems in Los Angeles area ???
From: "Byon Garrabrant" <byon@mail.com>
Date: Sun, 22 Oct 2000 15:54:28 -0700
X-Message-Number: 22
> On 22 Oct 00, at 11:49, Brent Hildebrand wrote:
> > > > On 22 Oct 00, at 7:06, Brent Hildebrand wrote:
> > Congratulations, you are observing the non-printable character
> > problem (not bug) of all Mic-E style stations, which included,
> >
> > > I don't think this is the non-printable char problem, but rather the
> > WinAPRS 2.4.6 bug. I have found that WinAPRS version 2.4.6
> >
> > place. No, I do not believe it is just a simple problem with WinAPRS
> > v246 (which may indeed have a problem). I do not have the definitive
> > answer, however, it would be "simple" to test. Connect the various
> > Internet client program up to a test server, and feed Mic-E data to the
> > client and observe the TCP/IP data stream.
OK, I just ran a test which REALLY makes me think this is a
WinAPRS 2.4.6 problem only. Here is what I did.
-Turn off my IGATE TNC (which has FILTER OFF, BTW), so
parameters will not be changed.
-Launch WinAPRS 2.4.6
-Turn on my IGATE TNC
-Set my D7 to EL power, and no packet path, so only my IGATE
will hear it.
-Launch a telnet aprs.net to watch the Inet stream
-Press BCON on the D7
-Capture the following two sentences from aprs.net:
N6BG-7>APK001:@222312z3610.98N/01516.35W[000/000/Mic-
E/M2/In Service>Byon's D7 Las Vegas!
N6BG-7>S6QPYY/1:'+,?l [/>Byon's D7 Las Vegas!
-Look at map.findu.com/n6bg-7, notice I am in the ocean
-Look at WinAPRS, notice I am in the ocean
-Turn off my IGATE TNC
-Quit WinAPRS 2.4.6
-Launch WinAPRS 2.4.7
-Turn on my IGATE TNC
-Press BCON on the D7
-Capture the follow two sentences from aprs.net:
N6BG-7>APK001:@222314z3610.98N/11516.35W[000/000/Mic-
E/M2/In Service>Byon's D7 Las Vegas!
N6BG-7>S6QPYY/1:'+,?l [/>Byon's D7 Las Vegas!
-Look at map.findu.com/n6bg-7, notice I am at my house
-Look at WinAPRS, notice I am at my house
What this tells me is just changing the version of WinAPRS, and
no TNC settings, changes my position stored on findu.com. I am
almost postitive that it is WinAPRS who converts the MIC-E format
it receives to the longer text form, and WinAPRS sends BOTH
versions to the Internet feed. If you look at the MIC-E packets
received, both are identical, but the long text version is only
different in time, and the dropped 100s digit.
Now, as for the dropping characters issue, you may notice that the
above data has dropped a char. Thats because the terminal
program I was using was set for non-binary mode. When I set it for
binary mode, and watched my TNC directly, I saw:
N6BG-7>S6QPYY/1:'+,?l [/>Byon's D7 Las Vegas!
Which is, in Hex Dump:
000000: 4E 36 42 47 2D 37 3E 53 36 51 50 59 59 2F 31 3A N6BG-
7>S6QPYY/1:
000010: 27 2B 2C 3F 6C 20 1C 5B 2F 3E 42 79 6F 6E 27 73 '+,?l
.[/>Byon's
000020: 20 44 37 20 4C 61 73 20 56 65 67 61 73 21 0D 0A D7
Las Vegas!..
Note the non-printable chars at offset 0x16.
I also noticed the following coming through aprs.net:
N6BG-7>S6QPYY/1:'+,?l [/>Byon's D7 Las Vegas!
which, in hex, is:
000000: 4E 36 42 47 2D 37 3E 53 36 51 50 59 59 2F 31 3A N6BG-
7>S6QPYY/1:
000010: 27 2B 2C 3F 6C 20 1C 5B 2F 3E 42 79 6F 6E 27 73 '+,?l
.[/>Byon's
000020: 20 44 37 20 4C 61 73 20 56 65 67 61 73 21 0D 0A D7
Las Vegas!..
Identical! So, it appears that non-printable chars (at least 0x1C)
can travel in from the TNC, through WinAPRS, through APRServe,
and back to the users, when FILTER is ON. The only problem I
have seen is when WinAPRS ALSO converts and outputs the text
form of the data, since 2.4.6 had a bug in that code.
Byon
________________________________________
Byon Garrabrant N6BG byon@mail.com
----------------------------------------------------------------------
Subject: Further thoughts on dual-band TNCs and cross-freq digipeating ...
From: WA8LMF1@aol.com
Date: Sun, 22 Oct 2000 19:01:17 EDT
X-Message-Number: 23
I've received a number of responses to my initial query that now indicates I=
didn't make one fact clear:
The cross-freq digipeater setup would not be located at the repeater site=
..
I would be listening to the repeater's OUTPUT off-the-air from a location
about a mile from the repeater site. I DON'T want to keep Mic-E packets fro=
m
being repeated over the voice repeater. This way, users that have only one
two-meter rig can monitor the voice activity and the APRS reports with a
single radio listening to the repeater output(and see only their own club
group without having to filter calls in APRS programs) --OR-- they can use=
a
2nd 2M radio on 144.39 --OR-- they can use the Internet.
I have already done this successfully during a demo at the club. I just set=
up a two-meter rig operating normally on the repeater in the club meeting
hall, connected it to a laptop running the AGW Packet Engine and APRSplus
(Look Ma! No TNC!), handed a TinyTrak in a box with a mic jack and cable to=
a
club member and told them to just go out and drive around town for a while.=
It worked perfectly on the first try
Read previous mail | Read next mail
| |