| |
ZL3AI > APRDIG 05.12.03 20:49l 233 Lines 8715 Bytes #999 (0) @ WW
BID : 2427-ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 01, 1/1
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PBX<OK0PHK<OK0NAG<OK0PPL<DB0RES<ON0AR<
ZL2BAU<ZL2BAU<ZL3VML
Sent: 031205/1821Z @:ZL3VML.#80.NZL.OC #:14012 [Chch-NZ] FBB7.00i $:2427-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, December 01, 2003.
1. Re: TOCALL allocation
2. Question regarding 'duplicate' packets on RF
3. New APRS860
4. Re: Digitraveler altitude limit?
5. Re: Digitraveler altitude limit?
6. Re: Setting up an OLD system... CD on Sound card
7. Re: Question regarding 'duplicate' packets on RF
----------------------------------------------------------------------
Subject: Re: TOCALL allocation
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 1 Dec 2003 08:54:24 -0500 (EST)
X-Message-Number: 1
On Sun, 30 Nov 2003, Scott Miller wrote:
>like a product-specific TOCALL. According to Bob's spec page, all of the
>letters of the alphabet are allocated, and sub-allocations should be
>coordinated amongst the developers. The TOCALL that makes the most sense to
>me would be APOTxx, which falls under APRSPoint's allocation, but so far I
>haven't had any response from KF6ZDM at aprspoint@yahoo.com. Does anyone
>know how I can contact him?
Ill go ahead and add you to the list at:
http://www.ew.usna.edu/~bruninga/aprs/errata.html
Bob
----------------------------------------------------------------------
Subject: Question regarding 'duplicate' packets on RF
From: James Washer <washer@trlp.com>
Date: Mon, 1 Dec 2003 07:39:30 -0800
X-Message-Number: 2
Here's 3 back-to-back packets heard by my TNC. (I've changed the orginators
callsign and the digi's callsign, to protect the innocent ;-)
SOMECALL>APTW01,DIGI1*,WIDE3-3:_11272313c060s000g000t041r000p000P000h97b10203tRW
SSOMECALL>APTW01,DIGI1*,WIDE3-2:_11272313c060s000g000t041r000p000P000h97b10203tW
RS
SOMECALL>APTW01,DIGI1*,WIDE3-1:_11272313c060s000g000t041r000p000P000h97b10203tRW
S
Am I correct in guessing that SOMECALL originated this packet which was
heard by (at least) two wide digi's. DIGI1, and another digi, let's call it
DIGI2. Both digi's then repeat the packet with a WIDE3-3. DIGI1, hearing
the DIGI2's WIDE3-3 packet, sends the packet again as a WIDE3-2. Meanwhile
DIGI2 heard DIGI1's WIDE3-3, so it responded with a WIDE3-2. Finally, DIGI1
hear's that other digi sending the WIDE3-2, so it sends a WIDE3-1.
Is that correct?
If so, this doesn't seem to be very efficient. I heard that some nodes use
a 30second window to avoid sending duplicate packets. Is that correct? If
so, would the 30second window have stopped these duplicates? How widespread
is the use of this 30second window? Almost every packet that hits my TNC is
duplicated.
thanks
- jim
----------------------------------------------------------------------
Subject: New APRS860
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 1 Dec 2003 10:57:38 -0500 (EST)
X-Message-Number: 3
APRS860 1 Dec 2003 First APRSdos new release in over 2 years
* Changed to shareware. No validation # required.
* Eliminated OPS-DIGI commands. Default path is WIDE,WIDE
* Removed automatic myalias of RELAY
* Added Nusance routine if operator enters abusive paths
* New config file in C:ROOT directory CFIG860.APR (w/o digi list).
* New MILEMARK function displays circles not lines (see MILEMARK.TXT)
* Changed QUIT to FILE-QUIT
* removed .../... when no PHG is entered (Kwds assumed moving)
* Added HOOKED-HEIGHT. Enter EL angle and ALTITUDE is computed
Download from TAPR.ORG in the APRSdos directory...
I assume that only old APRSdos users will have any interest in this, but
if you have not used APRSdos before, all you have to do is create an APRS
directory, PKUNZIP -DN the APRS860.ZIP file and at the DOS prompt, type
APRS. After answering all the start-up questions, and placed yourself on
the map, then do an alt-S-SAVE and next time it will go straight to the
map. (These instructions are in APRS\README\INSTALL.TXT)
I would ask the APRSdos users treat this as a BETA release, since I cannot
be certain that I used the most current SOURCE. But you can help me
by zooming into your state and testing the MILE-MARK feature. At least
compare the major turns in your interstates with your state highway map to
be sure I got the mile-markers right in those areas.
The milemarks are not supposed to be super accurate, but only to indicate
approximately where the given milemark should be. But the OLD method
which simply drew a horizontal or vertical line to intersect the
interstate was very forgiving of zig-zag stretches. ANd that is what I
based my data base on.
The new method of drawing a 1 mile ambiguity circle around a mile mark is
less forgiving. So if your state needs to be cleaned up, then I would ask
you to read MILEMARK.TXT and do it yourself (and send me the result)...
or if you canot figure it out, send me the LAT/LONG of the important
milemarkers at the critical changes in direction and I will add them...
I hope ALL APRS client software will inmplement the MILEMARK system since
it is the PRIMARY means that most hams use for reporting position on the
interstates...
de WB4APR, BOb
----------------------------------------------------------------------
Subject: Re: Digitraveler altitude limit?
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Mon, 1 Dec 2003 10:52:09 -0800 (PST)
X-Message-Number: 4
On Wed, 26 Nov 2003, Neil Johnson wrote:
>It depends. The limits are required by the U.S. Government to prevent Civilian
>GPS systems from being used for guidance systems by terrorists/"rouge"
>countries..
>
>I believe there are limits on the top speed to be reported, and a limit some
>how related to acceleration.
I think it was max altitude and max speed limits.
The interesting thing (to me anyway) is that some GPS manufacturers
interpreted the rules to mean "spec1 AND spec2", while others interpreted
them as "spec1 OR spec2". This gives us the range of products that the
high-altitude ballooning people can use which allow the gps to function at
high altitudes if and only if the speed is slow.
ICBM's can't go slow.
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: Re: Digitraveler altitude limit?
From: "Scott Miller" <scott@opentrac.org>
Date: Mon, 1 Dec 2003 11:15:10 -0800
X-Message-Number: 5
Good to know. I'd always assumed it was to make private pilots buy the
expensive aviation models...
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Setting up an OLD system... CD on Sound card
From: Gary Hinton <ghinton@eng.mcd.mot.com>
Date: Mon, 01 Dec 2003 13:12:53 -0700
X-Message-Number: 6
It can be found at driverguide.com:
http://members.driverguide.com/index.php?action=dosearch&qm0=JAZZ16&qa5=19&sm=s
Gary
AC7R
Mike Yetsko wrote:
>
>I'm trying to set up an old system for someone, and just blew away
>what was on it to put down 'known' data.
>
>But I made a mistake.
>
>It has a JAZZ16 sound card in it, with a single speed Sony CD
>player attached to the sound card, NOT to the IDE channel for
>ATA.
>
>Anyone know where I can pick up a driver to recognize this CD
>from DOS just so I can load suff onto the HD?
>
>Mike
----------------------------------------------------------------------
Subject: Re: Question regarding 'duplicate' packets on RF
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 1 Dec 2003 18:43:07 -0500 (EST)
X-Message-Number: 7
On Mon, 1 Dec 2003, James Washer wrote:
>SOMECALL>APTW01,DIGI1*,WIDE3-3:_11272313c060s000g000t...
>SOMECALL>APTW01,DIGI1*,WIDE3-2:_11272313c060s000g000t...
>SOMECALL>APTW01,DIGI1*,WIDE3-1:_11272313c060s000g000t...
The DIGI1 is incorrectly set to UIFLOOD WIDE,ID and this CAUSES this DIGI1
then to overwrite or obliterate the path data that could have told you what
was the first digi for that packet to hit. Since this digi is inocrrectly
set to "ID" instead of the receommended APRS standard of "NOID", it thus
kills path data and traceability.
If the packet had originated as WIDE,WIDE3-3, then it would have arrived as
above, BUT the first digi in the PATH would not be THIS digi, but would be
the three separate digis callsigns that first heard the packet. A much
more valuable piece of info.
Thus, this DIGI1 is either improperly set to "ID" or if the owner insists
on operating this way, then it SHOULD have an OVERLAY character of "I" to
show everyone that this digi is ID'ing itself in EVERY packet and
obliterating useful path data...
Unless it has the overlay I, we cannot tell what it is doing for certain...
Bob
---
END OF DIGEST
Read previous mail | Read next mail
| |
