OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 14:28l 241 Lines 9287 Bytes #999 (0) @ WW
BID : 770-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 23, 4/7
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<VK3TE<VK4TUB<ZL2BAU<ZL3VML
Sent: 030128/1057Z @:ZL3VML.#80.NZL.OC #:58324 [Chch-NZ] FBB7.00i $:770-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: Re: No Altitude Info with D7A
From: "Gregg G. Wonderly" <gregg@skymaster.cytetech.com>
Date: Thu, 23 Jan 2003 13:32:33 -0600
X-Message-Number: 20

>Any ideas on why an etrex Legend/D7A (original firmware) do not beacon
>altitude.
>
>IS it not  possible or am I doing something wrong.

Not possible with the original firmware.  The (g) upgrade adds support for 
$GPGGA sentences and transmit altitude using the MIC-E encoding for such.

-----
gregg@cytetech.com  (Cyte Technologies Inc)

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

Subject: Re: new IGATE on the way!
From: "Tim Cunningham" <tim_cunningham@mindspring.com>
Date: Thu, 23 Jan 2003 13:18:03 -0600
X-Message-Number: 21

We use APRS+SA for our IGate at N8DEU-4 with extremely good reliability.
 
It runs APRS+SA v2.15 at the moment. It has experienced 150 continuous days
of uptime the last 2 times it was rebooted and software was upgraded. It
runs under Windows 95B, 96MB RAM, and a P166 CPU.

Tim - N8DEU
 
----------------------------------------------------------------------

Subject: Re: Symbols/Icons was something else
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 23 Jan 2003 14:48:22 -0500
X-Message-Number: 22

On 1/23/03 at 7:10 AM spider@rivcom.net (Spider) sent:

>Why?
>Because certain people make it so?
>That is the second thing I've heard we can not depend with APRS in the last
>couple weeks.
>No doubt some stations using certain symbols are pretty much
>worthless/pointless to the rest of the APRS community.

There is no need to depend on the icon for anything. The only exception
that I am aware of is the weather icon when used in a position weather
report. The icons in APRS are for people to choose how they wish to appear
on the map. I should be free to advertise my operating system, my vehicle
type, or my hardware (e.g. Kenwood), my island location (IOTA), or the
service I provide. How I appear on the map is my choice.

I believe what should be depended upon is the actual function. What to see
who has weather (for example my near page weather column)? The figure out
who is sending weather data, rather than using the icon.

Want to know who is an IGate? Then see who is actually sending data to the
internet (easy with the q construct).

Steve K4HG

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

Subject: Re: Fixing APRS and SPEC Errata
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Thu, 23 Jan 2003 11:54:12 -0800 (PST)
X-Message-Number: 23

On Wed, 15 Jan 2003, Bob Bruninga wrote:

>Finally, I have put together a single APRS page with all the errata to the
>SPEC that I and Curt Mills have collected and also a collection of some of
>the things that need fixing and addressing in APRS that are not in the
>SPEC.
>
>See:     http://www.ew.usna.edu/~bruninga/aprs/errata.html

We've implemented "RFONLY" and "NOGATE" in the Xastir igate code now, which
aren't included on the errata page.

Yea I know those are APRS-IS specific things, but they are useful for APRS
software authors to know about.  Perhaps add another section with a few
important APRS-IS related things to your web page?

Are there others besides RFONLY and NOGATE that are in common use?

Anything having to do with satellite gateways or hf gateways?

I want to make sure we don't miss anything important.

-- 
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: Symbols/Icons was something else
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 23 Jan 2003 14:58:11 -0500
X-Message-Number: 24

On 1/23/03 at 11:49 AM spider@rivcom.net (Spider) sent:

>>>No doubt some stations using certain symbols are pretty much
>>>worthless/pointless to the rest of the APRS community.
>>
>>
>>That's a pretty bold statement!
>
>It's valid too, imho.
>Things that are shown on maps are Symbols.  If your station is an Island
>that is great!  I do not know of one APRS station that "is" an island.  I
>know a bunch of station operators that live in their own little
>worlds....maybe we need a world symbol.
>My map tells me what island that station is on....so to me, having your
>station show up as an Island means nothing.  I once watched an Island drive
>around the Phoenix area.....all I could think was  "What an idiot."
>What should be important is to accurately describe your station to the best
>of your ability ....I can't see where there would be an arguement about
>that.

Every man is an island...:-)

Regardless, my station points out why you cannot depend on the icon. Even
if I picked an icon based on my function, two others could not be
represented. I could use the IGate, but then the weather and digi are not
covered.

The only reliable way to determine function is by function...IGates are
those that IGate, weather stations are those that send weather, digis are
ones that digi. All of these function can be determined with features in
the protocol...there is not need to rely on the icon, which is guaranteed
to miss some providers of the service.

Steve K4HG

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

Subject: Re: I-gate and findu
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 23 Jan 2003 15:03:43 -0500
X-Message-Number: 25

On 1/23/03 at 12:29 PM art@nk8x.net (Art Snapper) sent:

>Is there a way to have findu.com display all stations gated by an i-gate in
>a given time period?

No, this data is not parsed out.

Steve K4HG

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

Subject: Re: Symbols/Icons was something else
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 23 Jan 2003 15:09:16 -0500 (EST)
X-Message-Number: 26

>Want to know who is an IGate? Then see who is actually sending data to the
>internet (easy with the q construct).

I agree that choice of ICONS is completely a personal choice.  But
mobiles cannot view the "q" construct, and unless they see an IGate
ICON, they cannot find out where the Igate is wherever they are.. so
stations acting as Igates not using the "I"gate icon should but the workd
"Igate" into their position or status text to help mobiles or visitors be
able to figure out where they can get into the net...

I agree that it is a problem, since so many stations are so multi-faceted.
I wonder what kind of abbreviation we can include in these comment fields
to suggest that they are also acting as an IGate?  SImply putting in
"Igate" into the posit text would be handy for mobiles...

APRSdos allows Overlay characters on ANY ICON, which was their original
intent when I added them to APRS in 1995. That way a WX station can be a
WX station but with an "I" overlay or an EOC can be an EOC but with an I
overlay...  But because WinAPRS could not do them except by specific
exception on specific ICONS, we could not get agreement to put
generalized ICON Overlays into the spec...  Thus there are only 6 Icons
(or so) in WinAPRS that allow overlays and each character that is desired
to overlay has to be manually added as an addition to the ICON table...

I wonder if they still have that limitation?  I think APRSdos and the
Kenwoods do not have that restriction... (somebody needs to check the
Kenwoods)..

The overlay characters were the main approach we wanted to take to solve
the problem of identifying multifunctional stations...

So there is no easy way to display multifunctional stations... :-(

Bob

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

Subject: Re: Symbols/Icons was something else
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 23 Jan 2003 20:32:56 -0000
X-Message-Number: 27

Sounds like what we need is a richer capabilities description field, like
the PHG message.

To back up a bit to a previous thread, has there been any movement toward
developing the UHF backbone we've discussed?  What are your thoughts on
using such a backbone to introduce an 'APRS v2' spec?  It sounds to me like
that (and maybe some APRS-IS systems) would be the perfect place to start.

And on a completely unrelated subject, what the heck is with these Mic-E
position reports?

IW5CCC-9>L@,0,IZ5AXT-11*,WIDE,TRACE7-7,qAS,IW5DAM:'!l >/
IW5CCC-9>L@,0,IZ5AXT-11*,WIDE,TRACE7-7,qAS,IW5DAM:'l >/
IW5CCC-9>L@,0,IZ5AXT-11*,WIDE,TRACE7-7,qAS,IW5DAM:'l >/Alex
realales@blu.it
IW5CCC-9>L@,0,IZ5AXT-11*,WIDE,TRACE7-7,qAS,IW5DAM:'$l >/Alex
realales@blu.it
IW5CCC-9>L@,0,IZ5AXT-11*,WIDE,TRACE7-7,qAS,IW5DAM:'$l >/Alex
realales@blu.it
IW5CCC-9>L@,0,IZ5AXT-11*,WIDE,TRACE7-7,qAS,IW5DAM:'$l >/

These came in over several minutes, so I don't think it's a one-time glitch.
Am I missing something in the spec or is the use of @  in the destination
address not valid?  If it's not valid, what's generating these packets?
Every time this guy keys up my parser service crashes.  (Max, libaprs2 is in
desperate need of some more error checking!)

Scott / N6UQE

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



Read previous mail | Read next mail


 16.11.2026 12:21:32lGo back Go up