| |
ZL3AI > APRDIG 19.11.03 23:25l 262 Lines 9870 Bytes #999 (0) @ WW
BID : 2321-ZL3AI
Read: GUEST
Subj: TAPR Digest, Nov 11, 1/6
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<WB0TAX<SP7MGD<VK3TE<ZL2BAU<
ZL2BAU<ZL3VML
Sent: 031119/1729Z @:ZL3VML.#80.NZL.OC #:13134 [Chch-NZ] FBB7.00i $:2321-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Tuesday, November 11, 2003.
1. Re: What Symbol? [was: APRS Icon statistics]
2. RE: APRS Icon statistics
3. Mini-Din
4. Re: Mini-Din
5. Re: Aprs DOS GPS String questions
6. Re: What Symbol? [was: APRS Icon statistics]
7. MULTI-ICON proposal
8. Re: What Symbol? [was: APRS Icon statistics]
9. RE: APRS Icon statistics
10. Re: MULTI-ICON proposal
11. APRS' Protocol Holes [was: APRS Icon statistics]
12. Re: MULTI-ICON proposal
13. RE: APRS Icon statistics
14. Re: APRS' Protocol Holes [was: APRS Icon statistics]
15. Re: MULTI-ICON proposal
16. Re: APRS' Protocol Holes [was: APRS Icon statistics]
17. Re: APRS' Protocol Holes [was: APRS Icon statistics]
18. Re: APRS' Protocol Holes [was: APRS Icon statistics]
19. Re: APRS' Protocol Holes [was: APRS Icon statistics]
20. Re: APRS' Protocol Holes [was: APRS Icon statistics]
21. Re: APRS' Protocol Holes [was: APRS Icon statistics]
22. Freq of Origination [was:APRS' Protocol Holes]
23. Re: Freq of Origination [was:APRS' Protocol Holes]
24. Re: APRS' Protocol Holes [was: APRS Icon statistics]
25. Re: MULTI-ICON proposal
26. Re: APRS' Protocol Holes [was: APRS Icon statistics]
27. Re: APRS' Protocol Holes [was: APRS Icon statistics]
28. Adding Frequency of TX to the Protocol [was:APRS' Protocol Holes]
29. Other ways to embed the info? [was:APRS' Protocol Holes]
30. Re: MULTI-ICON proposal
31. UI-View setup
32. RE: APRS Icon statistics
33. Re: Adding Frequency of TX to the Protocol [was:APRS' Protocol Holes]
34. Re: Other ways to embed the info? [was:APRS' Protocol Holes]
35. RE: APRS Icon statistics
36. tm-d700A / Peet Ultimeter question
37. Re: tm-d700A / Peet Ultimeter question
38. RE: APRS Icon statistics
39. Re: tm-d700A / Peet Ultimeter question
40. Re: tm-d700A / Peet Ultimeter question
41. Re: tm-d700A / Peet Ultimeter question
42. Re: tm-d700A / Peet Ultimeter question
43. Re: Freq of Origination [was:APRS' Protocol Holes]
----------------------------------------------------------------------
Subject: Re: What Symbol? [was: APRS Icon statistics]
From: Chris Rose <kb8uih@sbcglobal.net>
Date: Tue, 11 Nov 2003 04:01:30 -0800 (PST)
X-Message-Number: 1
Why not use the different buffers in a KPC3+ to send different strings of
data to identify different aspects of your station. Would the LT buffers
work? Enter different data to ID at intervals to highlight whatever is
going on with your station.
Chris
KB8UIH
--- "Gregg G. Wonderly" <gregg@skymaster.cytetech.com>
wrote:
>
>>What about multiple funcitons from the same
>station? What icon should be used
>>and how does one make mention of the other
>functions so that they are
>>identifiable too?
>
>This is precisely why icons loose when it comes to
>APRS. We really need apps
>to support multi-faceted station identification...
>Colors, appendage graphics
>or something needs to be in place to identify all
>aspects of a stations
>capabilty.
>
>-----
>gregg@cytetech.com (Cyte Technologies Inc)
----------------------------------------------------------------------
Subject: RE: APRS Icon statistics
From: "Spider" <spider@rivcom.net>
Date: Tue, 11 Nov 2003 06:08:54 -0700
X-Message-Number: 2
Maybe we need a "multi-use" station symbol!!! What do you want it to be?
I think we all have this problem to some extent. My stations is an Igate,
Digi, Wx station. Although I use UI-View, which allows me to separate my
weather station...allowing me to use a weather station map symbol for it.
So, the Wx station problem is solved. What is left is the Igate and Digi.
which should it be??? I choose the Igate map symbol because really, that is
what I choose it's primary purpose to be and where it does most of it's
work.
In your case, what does your station do the most? What is it's greatest
function? It would be nice to have all sorts of map symbols to represent
every possibility but we don't....and it would look goofy watching a station
change from one to the other.
Jim, WA6OFT
----------------------------------------------------------------------
Subject: Mini-Din
From: Reid Crowe <bigreidous@sbcglobal.net>
Date: Tue, 11 Nov 2003 05:14:21 -0800 (PST)
X-Message-Number: 3
Am I really behind or something? Since when did RadioShack stop carrying
six pin mini Din connectors?
73 Reid KC=D8IDI
----------------------------------------------------------------------
Subject: Re: Mini-Din
From: John Place <jplace@sc.rr.com>
Date: Tue, 11 Nov 2003 08:20:32 -0500
X-Message-Number: 4
I found them in their computer cable section here!
--
Amateur Radio
W4HNK
----------------------------------------------------------------------
Subject: Re: Aprs DOS GPS String questions
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 11 Nov 2003 08:32:57 -0500 (EST)
X-Message-Number: 5
On Mon, 10 Nov 2003, Michael Glennon wrote:
>I need a refresher on GPS Strings and how APRS DOS handles them. I When
>I use $GPGGA in Normal APRS DOS mode (should provide me with position
>and height). <not getting height information>
>
>KB4JHU-2>APRB03,RELAY,WIDE3-3/1:@071353z3523.10N/08612.02WCGGA/NUL/APRS*/Las
>tgps fix/A=001026
Im confused. It looks perfect to me. Height is 1026 feet.
>$GPGGA Compressed APRS String (should provide me with position and height)
><not getting height information>
>
>KB4JHU-2>APRB03,RELAY,WIDE3-3/1:@071422z/<X;!8aE!C{*!APRS*/Last gps
>fix/A=001026
Same, height is 1026
>When I use $GPRMC (should provide me with position, course and speed) I
>have also set up APRS DOS in Both (GGA and RMC) mode and I get the
>below. What make the statement state "old RMCs fix"?
>
>KB4JHU-2>APRB03,RELAY,WIDE3-3/1:@071418z3523.10N/08612.02WC033/000/APRS*/old
>RMCs fix/A=001026
CSE/SPD is 033 at 00 Knots. Old RMC fix meanse the VALID GPS FIX bit in
the NMEA string is not set. Probably the GPS is indoors and not seeing
satellitess at this instant.
>My goal is to send out position, course, speed and height information. I
>have plans to use this as a tracker APRS unit. Can someone give me the
>knowledge to fix this using APRS DOS and set it up correctly?
It looks like it is working correctly.
Bob
----------------------------------------------------------------------
Subject: Re: What Symbol? [was: APRS Icon statistics]
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 11 Nov 2003 08:45:00 -0500 (EST)
X-Message-Number: 6
On Mon, 10 Nov 2003, Gregg G. Wonderly wrote:
>We really need apps to support multi-faceted station identification...
>Colors, appendage graphics or something needs to be in place to identify
>all aspects of a stations capabilty.
Actually that was exactly what APRS was supposed to do. Back in the first
APRS paper presented in 1992 at DCC, the 37 byte coment field in the
position report could contain everything possible about your station. One
byte selected a TABLE (1 of 37 tables) and then each additional byte in
the string defined a capability. THus you could indicate what bands you
were on, types of antennas, types of ermergency and portable capability.
The idea was that the full capabilities were included in your single
position packet. Kind of a RESOURCE indication.
If other authors could support it, I would support an added FORMAT that
could say handle up to 8 additional ICONS per station. THey could be
arranged in a BLOCK (thats why 9)... We would do it this way:
If the construct +xyz+ appeared as the first bytes of the position comment
field, then the additional xyz icons could also be displayed. The
original ICON is what old clients would see, but new code would display a
block of ICONs around the original.
de wb4apr
----------------------------------------------------------------------
Subject: MULTI-ICON proposal
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 11 Nov 2003 08:55:25 -0500 (EST)
X-Message-Number: 7
MULTI-ICON proposal:
If other authors could support it, I would support an added construct that
could say handle up to 8 additional ICONS per station. THey could be
arranged in a BLOCK (thats why 9)... We would do it this way:
If the construct +xyz+ appeared as the first bytes of the position comment
field, then the additional xyz icons could also be displayed. The
original ICON is what old clients would see, but new code would display a
block of ICONs around the original.
DISCUSSION:
- This is backwards compatible with all existing code
- Using the + as the ending character means we cannot use the RED CROSS
ICON as one of the added ICONS thought it could be the primary one still.
- Using just single letters means we are limited to PRIMARY TABLE only
but I designed the alternate table mostly to contain OBJECT types of
ICONS and not the kinds that would normally be associated with a
station. But I am at home now and havent had time to study the
alternate table that closely.
I chose the + identifier because this is clearly an addition...
PARSING CODE must look for the + in the FIRST or SECOND position of the
comment text after the CSE/SPEED or PHG because the PHGR construct can be
one byte longer than the original PHG.
MY FEAR is that this will open pandoras box, and no HAM will be able to
resist inserting all 9 BRAG ICONS about everything he can do.... and maps
will become cluttered. Maybe clinet software then can have a switch to
disable multi-icons on demand...
But aside from that, it is a GOOD way to show VISUALLY the multi station
capability. BUT IT ALSO KILLS the utility of the COLOR ATTRIBUTES that I
wanted clients to show on ICONS by a surrounding background to show the
attributes of Moving, Old, Deadreckoned, Object, MY-object, ambiguity,
killed, etc... But mostly these only apply significantly to mobiles and
mobiles should remain as one ICON...
de WB4APR, Bob
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
