| |
ZL3AI > APRDIG 03.02.03 11:36l 280 Lines 9630 Bytes #999 (0) @ WW
BID : 808-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 28, 1/6
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<EB4BCS<IR0NET<VK3TE<VK4TUB<ZL2BAU<
ZL3VML
Sent: 030201/0938Z @:ZL3VML.#80.NZL.OC #:58555 [Chch-NZ] FBB7.00i $:808-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Tuesday, January 28, 2003.
1. User defined ICON (was RE: APRS Symbols)
2. Server Test, Don't Read
3. RE: APRS Symbols (versus Windows ICONS)..
4. RE: APRS Symbols (versus Windows ICONS)..
5. SATELLITE RADIO STATION
6. Case translation was ICP Symbol
7. RE: APRS Symbols (versus Windows ICONS)..
8. Re: findu2 backup remaining funds
9. RE: APRS Symbols (versus Windows ICONS)..
10. RE: APRS Symbols (versus Windows ICONS)..
11. RE: APRS Symbols (versus Windows ICONS)..
12. RE: APRS Symbols (versus Windows ICONS)..
13. RE: APRS Symbols (versus Windows ICONS)..
14. Re: regarding RACES
15. RE: Incident Command Post Symbol
16. RE: APRS Symbols (versus Windows ICONS)..
17. RE: APRS Symbols (versus Windows ICONS)..
18. Re: regarding RACES
19. RE: APRS Symbols (versus Windows ICONS)..
20. Re: findu2 backup remaining funds
21. Re: SATELLITE RADIO STATION
22. D700 and VS3
23. OnStar GPS for APRS
24. client software testers needed
25. Re: APRS Symbols (versus Windows ICONS)..
26. RE: APRS Symbols (versus Windows ICONS)..
27. RE: APRS Symbols (versus Windows ICONS)..
28. Backbone Spec WAS: RE: APRS Symbols
29. Re: APRS Symbols (versus Windows ICONS)..
30. EMERGENCY BEACON
31. Re: Backbone Spec WAS: RE: APRS Symbols
32. RE: findu2 backup remaining funds
33. RE: User defined ICON (was RE: APRS Symbols)
34. Re: findu2 backup remaining funds
35. RE: APRS Symbols (versus Windows ICONS)..
36. Re: findu2 backup remaining funds
37. Re: APRS Symbols (versus Windows ICONS)..
38. RE: findu2 backup remaining funds
39. RE: User defined ICON (was RE: APRS Symbols)
40. RE: findu2 backup remaining funds
41. THD7a and AWGPE
42. Re: Backbone Spec WAS: RE: APRS Symbols
43. GPS Jammed by junk consumer electronics...
44. Re: GPS Jammed by junk consumer electronics...
45. RE: findu2 backup remaining funds
46. TCP/IP Connects
47. Re: findu2 backup remaining funds
48. Re: Backbone Spec WAS: RE: APRS Symbols
49. Re: TCP/IP Connects
50. RE: APRS Symbols (versus Windows ICONS)..
51. Re: Backbone Spec WAS: RE: APRS Symbols
----------------------------------------------------------------------
Subject: User defined ICON (was RE: APRS Symbols)
From: Ken Koster <n7ipb@algedi.seatcp.net>
Date: Mon, 27 Jan 2003 21:36:47 -0800
X-Message-Number: 1
... (Bob,KD7NM's comment about a user defined icon deleted)
... (Brent,KH2Z's discussion of his playing with doing this in APRS+SA also
deleted)
And I've been playing with the same idea and Xastir, only I end up creating
a 24x24 bit 8-color icon.
The packet ends up being:
{ APRS User Defined Data
X Xastir special data
? Packet type identifier = binary 10000000 = Icon bit plane 1
binary 10000001 = Icon bit plane 2
binary 10000010 = Icon bit plane 3
72 bytes of icon data in binary, arranged in a 24x24bit array.
(msb first, top left of icon to bottom right)
Send the packet three times, once for each bit plane and either display
the standard icon until you've received all three, or go ahead and
display each plane as received, building up the icon over time.
Send the packets in bursts of three, each plane seperated by a minute or two
with the triple bursts once every half hour or so.
It's a work in progress without a working example yet, but give me time.
Ken, N7IPB
----------------------------------------------------------------------
Subject: Server Test, Don't Read
From: "Matthew Stennett" <wa4tkg@iwon.com>
Date: Tue, 28 Jan 2003 01:34:26 -0500 (EST)
X-Message-Number: 2
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Steve Dimse <k4hg@tapr.org>
Date: Tue, 28 Jan 2003 03:21:19 -0500
X-Message-Number: 3
On 1/27/03 at 5:05 PM bruninga@usna.edu (Bob Bruninga) sent:
>>Please don't blame TAPR. TAPR was only a facilitator for the APRS Spec
>>Working Group. It provided a forum (the Working Group's e-mail list) and
>>Web space for the group. It never specified any guidelines for the spec.
>>The Working Group specified the guidelines, not TAPR.
>
>This is totally false. I was locked in a room and not allowed to leave
>until I agreed to the terms. Either I agreed to do the spec with all
>its shortcomings and without what I considered to be some of the
>fundamentals of APRS (how information is displayed) or the other authors
>would go there own way and do it anyway they individually wanted.
Bob, this is a complete lie, and I demand an apology. I was there, I am
certain there was no locked door. If you need the others that were present
to speak up, I'm sure they will do so.
Perhaps you felt trapped by the circumstances, but if so, it was the
combination of your actions and the opinions of others within the APRS
community that left you with that feeling. In fact you did not have many
choices at that point, you could have tried to keep APRS proprietary to
yourself and the few you chose to license, and killed APRS, or you could
open it up as others wanted. I think you chose the right way, but there was
a choice.
There was no lock on the door, you could have walked out any time you
wanted. Admit the truth.
Steve K4HG
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Juergen Frank <db2fm@jfsattv.de>
Date: Tue, 28 Jan 2003 11:23:35 +0100
X-Message-Number: 4
am 28.01.2003 1:13 Uhr schrieb The Hildebrands unter
b.hildebrand@verizon.net:
---- snip ----
>----- Original Message -----
>This represents a simple, big X, with bits like this:
>1000000000000001
>0100000000000010
>0010000000000100
>0001000000001000
>0000100000010000
>0000010000100000
>0000001001000000
>0000000110000000
>0000000110000000
>0000001001000000
>0000010000100000
>0000100000010000
>0001000000001000
>0010000000000100
>0100000000000010
>1000000000000000
>
>The first 6 bits, are 100000, which represents 32, add 48 yields 80 which is
>ASCII "P". The next six bits are all 0 which yeilds ASCII 48, or "0". The
>next six, 000101 = 5, add 48 yields 53, ASCII "5", etc.
>
>In APRS+SA one can play with this a little using the APRS+SA "Calculator"
>function, and no, it does not work over the air, it is not supported (<devil's
>advocate> but it could </devil's advocate>). Try entering this:
>N.B. create an icon:
>icon #is TacIcon 'Create'
>N.B. see the bits:
>icon
>N.B. Convert the bits to text:
>text #is TacIcon 'Icon2Text' icon
>N.B see the text:
>text
>N.B. see the bits in the text string
>TacIcon 'Text2Icon' text
>N.B. edit the icon
>icon #is TacIcon 'Wait' icon
>N.B. see the bits again
>icon
>
></lingua in bucca>
>Brent KH2Z
Hi all,
I find this a very constructive idea! One very important thing is to not
have colours define anything! Think of APRS-clients not able to display
colors (e.g. PocketAPRS). There my idea of using a small triangle like a
count down timer around a symbol instead of colors for icons would work,
too.
Bob's initial idea of showing a symbols status (Deadreckoning) is important
but the way it could be done should be discussed. Bob?
73 de Juergen db2fm
P.S: One thing: most symbols will remain fixed, only some will we user
defined!!! (The ones not used anymore '/0 to /9' e.g.)
--
DB2FM
Juergen Frank
mailto: db2fm@amsat.org
mailto: db2fm@darc.de
mailto: db2fm@jfsattv.de
ICQ: 144135020
----------------------------------------------------------------------
Subject: SATELLITE RADIO STATION
From: "Fernando Stancato" <fernando.stancato@unopar.br>
Date: Tue, 28 Jan 2003 10:30:23 -0200
X-Message-Number: 5
Dear all
I would like to know if it is possible to hear satellite packets with a
common HT (0,14 microV sensitivity) and 10 m of coax and a 3 Dbi
omnidiretional 5/8 wave antenna. The frequency would be at 144 Mhz and no
Doppler compensation.
In the case it would not, does the TH-D7A(G) can ?
Fernando Stancato
SPACE - Sistema de Pesquisa Aerospacial Educativa Cient=EDfica
UNOPAR
fernando.stancato@prof.unopar.br
www.unopar.br/portal/space
----------------------------------------------------------------------
Subject: Case translation was ICP Symbol
From: "Spider" <spider@rivcom.net>
Date: Tue, 28 Jan 2003 05:40:46 -0700
X-Message-Number: 6
----- 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: Monday, January 27, 2003 6:27 PM
Subject: [aprssig] RE: Incident Command Post Symbol
>On Mon, 27 Jan 2003, Curt Mills, WE7U wrote:
>
>>Looks like you can't create mixed-case/lower-case object names? I
>>now have multiples of each object on my screen, some with
>>lower/mixed-case (the way I created them), and some with all
>>upper-case (the ones you created).
>
>Great testing! Yes it has to be an exact match... go for it...
>bob
Curt noticed an interesting problem. Curt runs Xastir, I run UI-View.
He created an Object. The object identifier was made in lower case.
Later, I took ownership of that object and UI-View automatically changed
the Object identifier to all upper case.
On my screen, Curt's object went away and my new object was where I had
placed it.
On Curt's screen, his object remained in lower case, and mine showed in
upper case.
As soon as Curt's station beaconed his object, his object appeared on my map
and
my object disappeared!
So....there is what appears to be a case translations problem?
I wonder what the other software products do?
Jim, WA6OFT
----------------------------------------------------------------------
Read previous mail | Read next mail
| |