| |
ZL3AI > APRDIG 12.04.07 05:59l 242 Lines 8410 Bytes #999 (0) @ WW
BID : 10041-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #9, 5/6
Path: DB0FHN<DB0FOR<DB0MRW<OK0PKL<OK0PCC<OM0PBC<OK0PPL<DB0RES<DB0GOS<ON0AR<
7M3TJZ<DK0WUE<CE8FGC<VK6HGR<ZL2BAU
Sent: 070412/0448Z @:ZL2BAU.#79.NZL.OC #:42607 [Waimate] $:10041-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 33
Date: Tue, 10 Apr 2007 00:35:24 -0500
From: Doug Younker <dougy_at_ruraltel.net>
Subject: Re: [aprssig] SSID for RF only Station with backup power
OK, I better understand. I'm looking at what uiview provides, I see a
civil defense triangle, and a symbol for NTS. Perhaps one of those
combined with a beacon comment would get across the information you want
to get across?
Doug, N0LKK
Bill Vodall WA7NWP wrote:
>Maybe the power issue has gotten too much attention. The real
>priority is to have an "APRS Emergency Operation Station." Unlimited
>power (solar, etc) is one parameter of such a station. On the other
>hand, that and a bit of advertising and practising is what
>differentiates it for any other APRS station with a radio...
>
>73
>Bill
------------------------------
Message: 34
Date: Tue, 10 Apr 2007 01:12:42 -0500
From: "John Habbinga" <kc5zrq_at_gmail.com>
Subject: Re: [aprssig] SSID for RF only Station with backup power
Scott, I recall an earlier discussion about this. You got the idea from a
military specification. Can you tell me what document spelled out how that
hierarcy worked?
----- Original Message -----
>This is why, in the OpenTRAC spec, I proposed a hierarchy. I don't have
>the list in front of me, but a bike might be something like 1.2.4 (land,
>vehicle, bicycle) and a recumbent might be 1.2.4.1. The advantage is that
>you don't need all 60,000 icons - you can still tell what something is as
>long as you know the basic category.
------------------------------
Message: 35
Date: Tue, 10 Apr 2007 01:07:04 -0600
From: Joel Maslak <jmaslak-aprs_at_antelope.net>
Subject: Re: [aprssig] SSID for RF only Station with backup power
On Apr 9, 2007, at 10:50 PM, Scott Miller wrote:
>This is why, in the OpenTRAC spec, I proposed a hierarchy. I don't have the
>list in front of me, but a bike might be something like 1.2.4 (land,
>vehicle, bicycle) and a recumbent might be 1.2.4.1. The advantage is that
>you don't need all 60,000 icons - you can still tell what something is as
>long as you know the basic category.
Oh, an OID. Yes, that could work, if you could get someone to agree to be
authoritative (you need to avoid collisions - OIDs do this by assigning
each organization a second level identifier that is unique, but I don't
think that would be what we'd want).
Well, let's see if I can get back to bed (we're having weather I don't even
think I can give a name for - sleet, thunder, wind).
------------------------------
Message: 36
Date: Tue, 10 Apr 2007 10:19:48 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: [aprssig] Tiny Trak 3 config?
>.... Unless your driving down straight highways for many
>hours you just cant run agressive corner pegging [on HF]..
I see many operator errors on TInyTracks in my area. Three are beaconing a
wasteful STATUS packet saying "TinyTrack3 v 1.1" in addition to another
status text... One is beaconing every 30 seconds for a total of over 100
packets per hour, etc...
Does the Tiny Track have more than one status Text?
Since APRS defines STATUS as one-per-station, these toggling STATUS texts
then eat up log files, since APRS logs any CHANGE in status or position to
the log file. Getting two every minute from a TT is excessive...
Is this set-up error? Or does TinyTrack always output this?
Bob
------------------------------
Message: 37
Date: Tue, 10 Apr 2007 09:30:21 -0500
From: "Robbie, wa9inf" <mwrobertson_at_comcast.net>
Subject: Re: [aprssig] Tiny Trak 3 config?
Bob,
Byron offers the manual and setup program downloads at
http://byonics.com/
I have a couple of the TinyTrak IIs and one of the SMT TinyTrak III and
I know you can do most anything with status text as you feel you want as
with other client software setups. I guess it would be user education
and common sense.. :-)
Robbie
Robert Bruninga wrote:
>>.... Unless your driving down straight highways for many
>>hours you just cant run agressive corner pegging [on HF]..
>
>I see many operator errors on TInyTracks in my area. Three are
>beaconing a wasteful STATUS packet saying "TinyTrack3 v 1.1" in
>addition to another status text... One is beaconing every 30
>seconds for a total of over 100 packets per hour, etc...
>
>Does the Tiny Track have more than one status Text?
>
>Since APRS defines STATUS as one-per-station, these toggling
>STATUS texts then eat up log files, since APRS logs any CHANGE
>in status or position to the log file. Getting two every minute
>from a TT is excessive...
>
>Is this set-up error? Or does TinyTrack always output this?
>
>Bob
------------------------------
Message: 38
Date: Tue, 10 Apr 2007 07:38:59 -0700 (PDT)
From: "Curt, WE7U" <archer_at_eskimo.com>
Subject: RE: [aprssig] SSID for RF only Station with backup power
On Mon, 9 Apr 2007, Robert Bruninga wrote:
>So I propose the following:
>
>* Being there are less than 7 APRS symbols left
>* Being that there are many many more ideas to go
>* Therefore, APRS must expand its symbol set by using OVERLAYS
>* We need concurrence from all authors on receipt of an overlay:
>- Receipt on all existing "overlyable characters works"
>- Receipt on any other symbol will not break anything
>- Eventually receipt of the overlay may be displayed somehow
>- An overlay on a base symbol can trigger a different symbol
I have no problem with the above except for the last one. It requires code
changes for all APRS applications.
This could signal the end of the line for unsupported apps & radios. Not
necessarily a bad thing, but I figured I'd mention it.
If we're going to break things on purpose I'd favor the
major.minor.more-minor scheme from the military spec: It gives us
incredible capabilities as well as great compatibility for apps that don't
implement the 2nd/3rd level of detail or don't happen to have the latest
definitions. Implement the first level of detail and you're up and
running. Implement the 2nd level and you get more detailed and descriptive
icons. Same for 3rd and beyond.
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
------------------------------
Message: 39
Date: Tue, 10 Apr 2007 07:45:13 -0700
From: "'Scott Miller'" <scott_at_opentrac.org>
Subject: RE: [aprssig] SSID for RF only Station with backup power
It's in MIL-STD-2525B.
Scott
N1VG
>Scott, I recall an earlier discussion about this. You got the idea from a
>military specification. Can you tell me what document spelled out how that
>hierarcy worked?
------------------------------
Message: 40
Date: Tue, 10 Apr 2007 11:00:56 -0400 (EDT)
From: Rick Green <rtg_at_aapsc.com>
Subject: RE: [aprssig] SSID for RF only Station with backup power
All this discussion of special identifiers for stations with exceptional
UPS capabilities is moot:
In an emergency, when it is most necessary to identify such stations,
they will be conspicuous by the fact that they will be the only stations
beaconing anything at all!
....remember that one lonely rf-only digi in New Orleans, Pleading 'use me!
Use me!' to deaf ears...
--
Rick Green
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
------------------------------
Message: 41
Date: Tue, 10 Apr 2007 08:54:24 -0600
From: Earl Needham <earl_needham_at_yahoo.com>
Subject: Re: [aprssig] SSID for RF only Station with backup power
At 12:05 PM 4/9/2007, John Habbinga wrote:
>>The problem with the tags in the comment fields is that it doesn't
>>allow selecting stations on an APRS map.
>
>I'm not sure I understand what you are trying to do. If you only
>want to see stations that are transmitting on RF, don't connect to
>an APRS server, just monitor 144.390 MHz. All the stations that you
>see on the APRS map will be on RF.
Did I misunderstand? I thought you told me that any station in the Lubbock
area, that's on TCP/IP only, is gated out to 144.39. That means that every
station you see on 144.39 is NOT necessarily on RF.
7 3
Earl
KD5XB -- Earl Needham
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
------------------------------
Read previous mail | Read next mail
| |
