OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 14:29l 266 Lines 9238 Bytes #999 (0) @ WW
BID : 792-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 26, 1/4
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<W7NTF<VK3TE<ZL2BAU<ZL3VML
Sent: 030130/1001Z @:ZL3VML.#80.NZL.OC #:58447 [Chch-NZ] FBB7.00i $:792-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Sunday, January 26, 2003.

1. RE: installed infrastructure, WAS: Symbols/Icons was something else
2. APRS Symbols (versus Windows ICONS)..
3. Re: Icon for I'net-only station?
4. New List - ham-80211@lists.tapr.org
5. How to connect to APRS server using PERL (linux)
6. Proposals, was something else
7. Re: APRS Symbols (versus Windows ICONS)..
8. RE: APRS Symbols (versus Windows ICONS)..
9. RE:  New Garmin PDA
10. RE: [ui-view] DOS APRS Map Server For UI-View32
11. New List - ham-80211@lists.tapr.org
12. Re: APRS Channel Metric! Wow
13. RE:  New Garmin PDA
14. Re: APRS Channel Metric! Wow
15. Re: Future of 144.39
16. RE: Big Digis - another idea
17. JUI?
18. aprsworld.net needs your help
19. Re: JUI?
20. Re: JUI?
21. problem with d7 digipeater/tnc
22. SV: Re: new IGATE on the way! (CQ AA3JY)
23. Signals
24. Re: Proposals, was something else
25. Re: APRS Symbols (versus Windows ICONS)..
26. Re: Proposals, was something else
27. Re: APRS Symbols (versus Windows ICONS)..
28. Re: Proposals, was something else
29. Re: ARRL Public Service Manual regarding RACES
30. FT-100 operations.
31. RE: Big Digis - another idea
32. Re: FT-100 operations.
33. Re: ARRL Public Service Manual regarding RACES
34. maps for findu
35. Re: FT-100 operations.
36. Re: maps for findu
37. Re: maps for findu
38. Re: FT-100 operations.
39. Re: ARRL Public Service Manual regarding RACES

----------------------------------------------------------------------

Subject: RE: installed infrastructure, WAS: Symbols/Icons was something else
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 26 Jan 2003 00:26:47 -0500 (EST)
X-Message-Number: 1

On Sat, 25 Jan 2003, Bob D. wrote:

>... but somehow we do need to get many of these DIGIs up to
>date in a relatively short time as Henk says. Hey, we did it when we
>QSY'd from 145.790, it can be done again. Yes, there may be those who
>will balk at having to replace equipment that has been working just fine
>for the last 5 years, but technology waits for no Ham.
>
>BEFORE we jump into this though, we should hash out here what that new
>system will be, as has been going on in these informative and thoughtful
>discussions.

Im working up a web page to collect all my thoughts I have posted about
UHF backboning to offload the totally saturated big metro areas.  It has
only begun, but is a start and a work in progress...
FOllow the link to "Fixing the Network"... on the errata page

     http://www.ew.usna.edu/~bruninga/aprs/errata.html

then go to the bottom for UHF BACKBONE SOLUTION...

A work in progress, but a start..

Bob, WB4APR

----------------------------------------------------------------------

Subject: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 26 Jan 2003 00:42:32 -0500 (EST)
X-Message-Number: 2

On Sat, 25 Jan 2003, James Smith wrote:
>Being in APRS for all these years, I haven't ever seen a Skywarn symbol
>
>Phil Pacier, AD6NH wrote:
>>I konw you say one exists, Bob, but I have been unable to find it.

Yes, that is because APRS was not designed to use "icons".  That is a
window's term.  APRSdos draws the symbols on the screen, instead of using
bit-mapped "Icons".  This is beacuse "SYmbols" in APRS are supposed to
convey several layers of information about each "thing" on a map for
instant recognition.  Thus APRS, as designed in the original APRSdos,
displays each "symbol" on a map using COLOR (and overlays) as variables:

 White     - means fully capable APRS active station (Message capable)
 LightGray - means Tracker or otherwise non-msg capable
 DarkGray  - means not heard in over 80 minutes
 Yellow    - means my object (I am currently transmitting)
 Blue      - means previous posit of any station
 Cyan      - means dead reckoned posit
 Violet    - means object from somone else
 Green     - is any station that is a digipeater
 Brightblue- is WX
 Red       - is emergency or unknown, or Alarmed

Thus, a whole layer of visual information was lost in most Windows
versions of APRS that took the simplistic "Icon" approach to displaying
APRS stations on their maps.

A "thing" on an APRS map is multidimensional as indicated above.  All of
this information is lost in most current implementations unless the
individual clicks on each Icon in turn to see what "kind" of thing it is.
Some authors have taken pains to try to convey some of this information,
but none of them are as simple and visual as APRS was designed to do (as
implemented in APRSdos)...

So, lack of seeing what an "icon" is, is not the fault of "APRS", it is
the fault of many implementations of "APRS"...

Bob, WB4APR

----------------------------------------------------------------------

Subject: Re: Icon for I'net-only station?
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 26 Jan 2003 00:43:14 -0500 (EST)
X-Message-Number: 3

Sorry, havent done any PIC work since the MIM...

So I am out of date..
Bob

On 26 Jan 2003, Andrew Rich wrote:

>Hi
>
>I would like to program a PIC that has 2 UARTS
>
>Can anyone suggest one ? The basic stamp is TOO expensive at $100
>
>Why ? GPS on one side (RX) , modem (TX / RX) on the other side.
>
>Cheers
>
>Andrew VK4TEC

de WB4APR@amsat.org, Bob

PCsat WEB  page     http://www.ew.usna.edu/~bruninga/pcsat.html
ISS-APRS FAQ:       http://www.ew.usna.edu/~bruninga/iss-faq.html
CUBESAT Designs     http://www.ew.usna.edu/~bruninga/cubesat.html
APRS LIVE pages     http://www.ew.usna.edu/~bruninga/aprs.html
APRS SATELLITES     http://www.ew.usna.edu/~bruninga/astars.html
MIM/Mic-E/Mic-Lite  http://ssdl.stanford.edu/mims/

----------------------------------------------------------------------

Subject: New List - ham-80211@lists.tapr.org
From: "Darryl Smith" <Darryl@radio-active.net.au>
Date: Sun, 26 Jan 2003 23:17:33 +1100
X-Message-Number: 4

Given the increased interest in Amateur applications for 802.11b, we
have decided to add another mailing list for discussions specifically on
its implementation in the Ham Radio world. 

The list is designed to be a meeting place for all 802.11b experimenters
- regardless of where in the world they are located, or what protocol
changes are being advocated. 

If you wish to join this mailing list the best way is probably to visit
the following URL
	
	http://www.tapr.org/cgi-bin/lyris.pl?enter=ham-80211&text_mode=0

To post to this mailing list send an email to

	ham-80211@lists.tapr.org

Darryl
TAPR Board Member.
---------
Darryl Smith, VK2TDS   POBox 169 Ingleburn NSW 2565 Australia
Mobile Number 0412 929 634 [+61 4 12 929 634 International] 
Darryl@radio-active.net.au | www.radio-active.net.au  

----------------------------------------------------------------------

Subject: How to connect to APRS server using PERL (linux)
From: Andrew Rich <andrew.rich@bigpond.com>
Date: 26 Jan 2003 22:47:35 +1000
X-Message-Number: 5

Here is a really basic example of how to establish a connection to an 
APRS server, using PERL under LINUX.

#!/usr/bin/perl
use IO::Socket::INET;
$sock = IO::Socket::INET->new(PeerAddr => 'aprs.net.au',
                              PeerPort => '10151',
                              Proto    => 'tcp');
while(<$sock>) {
    print;
}

Andrew VK4TEC

----------------------------------------------------------------------

Subject: Proposals, was something else
From: "Spider" <spider@rivcom.net>
Date: Sun, 26 Jan 2003 05:44:15 -0700
X-Message-Number: 6

>>---
>>Who adds them to the Specification?  Bob?
>
>After they are proposed, they are presented to all the authors on the
>SPEC discussion list and if there are no objections, then they are
>considered adopted..
>
>Bob

Thanks for that info, Bob.  But who presents them?  I am not on that list,
nor should I be.
Are you going to take the ICP symbol and propose it there, for example?

----------------------------------------------------------------------

Subject: Re: APRS Symbols (versus Windows ICONS)..
From: "Spider" <spider@rivcom.net>
Date: Sun, 26 Jan 2003 05:54:03 -0700
X-Message-Number: 7

----- Original Message -----
From: "Bob Bruninga" <bruninga@usna.edu>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Cc: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Saturday, January 25, 2003 10:42 PM
Subject: [aprssig] APRS Symbols (versus Windows ICONS)..

>On Sat, 25 Jan 2003, James Smith wrote:
>>Being in APRS for all these years, I haven't ever seen a Skywarn symbol
>>
>>Phil Pacier, AD6NH wrote:
>>>I konw you say one exists, Bob, but I have been unable to find it.
>
>Yes, that is because APRS was not designed to use "icons".  That is a
>window's term.  APRSdos draws the symbols on the screen, instead of using
>bit-mapped "Icons".  This is beacuse "SYmbols" in APRS are supposed to
>convey several layers of information about each "thing" on a map for
>instant recognition.  Thus APRS, as designed in the original APRSdos,
>displays each "symbol" on a map using COLOR (and overlays) as variables:

In APRSdos (never have seen it) how does it handle several stations within a
few feet of each other?  How do you seperate stations?

Jim

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 09:45:22lGo back Go up