OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   14.02.07 06:05l 243 Lines 10339 Bytes #999 (0) @ WW
BID : 9708-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 32 #11, 1/5
Path: DB0FHN<DB0MRW<DB0ERF<DB0FBB<DB0IUZ<DB0GOS<DB0RES<TU5EX<SR1BSZ<CE8FGC<
      TU5EX<CX2SA<ZL2BAU
Sent: 070214/0458Z @:ZL2BAU.#79.NZL.OC #:32731 [Waimate] $:9708-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To  : APRDIG@WW

Today's Topics:

1. RE: RE: European Digipeating standards (Cap Pennell)
2. ALogger 3.0.0 released, KISS and remote client support (Bill Diaz)
3. Re: RE: European Digipeating standards (Jan T. Pharo)
4. Re: Baycom modem (Ray Wells)
5. RE: RE: European Digipeating standards (Cap Pennell)
6. Re: Tour de Palm springs (Ron Tonneson)
7. Re: RE: European Digipeating standards (Andy AB9FX)
8. Re: ALogger 3.0.0 released, KISS and remote client support (Andy AB9FX)
9. Re: ALogger 3.0.0 released, KISS and remote client support (Andy AB9FX)
10. Weather station path? (Art)
11. RE: Tour de Palm springs (Eric Goforth)
12. Re: Weather station path? (Keith VE7GDH)
13. Re: Tour de Palm springs (Ron Tonneson)
14. RE: Tour de Palm springs (Eric Goforth)
15. RE: APRS Icons on Garmin Receivers (Scott Miller)
16. Re: APRS Icons on Garmin Receivers (Joel Maslak)
17. RE: APRS Icons on Garmin Receivers (Scott Miller)
18. RE: APRS Icons on Garmin Receivers (Scott Miller)
19. Re: APRS Icons on Garmin Receivers (Earl Needham)
20. Re: RE: European Digipeating standards (Jan T. Pharo)
21. Re: APRS Icons on Garmin Receivers (Stephen H. Smith)
22. Re: APRS Icons on Garmin Receivers (Stephen H. Smith)
23. Re: APRS Icons on Garmin Receivers (jdw_at_eng.uah.edu)
24. Re: APRS Icons on Garmin Receivers (jdw_at_eng.uah.edu)
25. RE: APRS Icons on Garmin Receivers (jdw_at_eng.uah.edu)
26. gps sneakers ? (Kevin Deckert)
27. Re: APRS Icons on Garmin Receivers (Robbie, wa9inf)
28. Re: APRS Icons on Garmin Receivers (Randy Allen)
29. D700-external PIC processing (Robert Bruninga)
30. APRSSIG  (Stan Horzepa)
31. Voice Aert redux (Robert Bruninga)
32. Re: Weather station path? (Art)
33. Re: Voice Aert redux (Wes Johnston, AI4PX)
34. Voice Alert Simplicity! (Robert Bruninga)
35. RE: Voice Aert redux (Ken Cechura)
36. Re: APRS Icons on Garmin Receivers (Jan T. Pharo)

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

Message: 1
Date: Sat, 10 Feb 2007 10:57:45 -0800
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [aprssig] RE: European Digipeating standards

See below.

>-----Original Message-----
>From: aprssig-bounces_at_lists.tapr.org
>[mailto:aprssig-bounces_at_lists.tapr.org]On Behalf Of Jan T. Pharo
>Sent: Thursday, February 08, 2007 14:32 PM
>To: TAPR APRS Mailing List
>Subject: Re: [aprssig] RE: European Digipeating standards
>
>"Cap Pennell" <cap_at_cruzio.com>, Thu, 8 Feb 2007 10:03:11 -0800:
>
>>Luckily, it's a short step from RELAY,WIDEn-N to the improved over-the-air
>>efficiency of more modern "traceable WIDEn-N" alone, and any fill-in digis
>>can operate WIDE1-1 instead of RELAY.  The improvement can even be
>>implemented one station at a time, so there's no need to wait for the better
>>modern system.  UI-View32 can be used to do the digipeating job handling
>>both systems at once.
>
>You will of course be aware that the highly dense populated areas with
>high terrain walls that your have especially in California, have a
>_much_ larger APRS user density and a _very_ different topography than
>most areas in Europe; mountain top digipeaters covering areas with
>several million inhabitants aren't there. Also, Europe are several
>independent nations with independent amateur radio associations and
>different radio frequency legislations (we have - for all practical
>purposes - one band plan, though).
>I have said previously - and am still saying - that there should be an
>agreement, preferrably through the IARU region 1, about the parameters
>in this area, rather than groups of digipeater owners doing one
>solution and other groups or individuals in the neighbouring areas
>doing another solution, making up a mess for travelling APRSers inside
>each country or crossing international borders. Unlike north America,
>we europeans can cross almost any international border inside Europe
>with car or walking/bicycling without even stopping for any customs or
>passport control, so the need for _one_ system is there; the openness
>to get to a mutual agreement, howeveer, isn't. Each party has a
>religious belief in their own system; RELAY,TRACEn-N, RELAY,WIDEn-N
>(traceable or not), the US WIDE1-1,WIDEn-N (these are for
>mobiles/portables).
>
>--
>73 de Jan, LA2BBA
>Hvaler, Norway

Jan, yes certainly, the network topology is different in "flatland" and/or
"sparse" regions (like much of the Central US and Texas too).  But there
too, the main objective a VHF station seeks to accomplish is accessing the
_first_ digi in a path, rather than needing a much _broader_ path.

In the US, where as you know we freely travel between our States, as you do
between European Union states, the newer "traceable WIDEn-N" system has been
implemented through common understanding of it's benefits as a more
efficient system allowing greater capacity on VHF and hence more potential
courtesy to more fellow ham operators as the future unfolds.  Our prior
beliefs in older less efficient systems involving RELAY have evolved forward
for the common good.  It hasn't been done by edict or enforcement, but
rather by cooperation and education and experience, and is still occurring
one station at a time.  Anybody and everybody can help.

Working toward a effective and efficient "universal" path system for VHF
travelers too?  Think "traceable WIDEn-N" (and surely not RELAY anything).
Our modern fill-in digis (WIDE1-1 only) retain the advantages old RELAY
digis once had for travelers, but eliminate the inefficiencies of that old
system.

Of course, there often _is_ political resistance to cooperation between
"empires" of all sorts due to inexperience with the advantages of
interoperability, but truly we are all in this together.

There needn't be a configuration problem to fly your tracker across the
ocean and have it work on the other side too.  If we're to share a system,
let's share the more efficient and courteous modern one.
73, Cap KE6AFE

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

Message: 2
Date: Sat, 10 Feb 2007 13:23:54 -0600
From: "Bill Diaz" <william.diaz_at_comcast.net>
Subject: [aprssig] ALogger 3.0.0 released, KISS and remote client support

ALogger 3.0.0 has been released.  This version includes support for KISS
TNC's and the ability for remote clients to access an attached TNC or
D7/D700 as well as logged packets from the APRS-IS.

The remote client capability was designed primarily to permit remote control
of a PCSAT or similar Earth Station over the Internet and to monitor all
radio/TNC traffic. 

Remote clients can connect to the ALogger session using a TelNet like
connection (HyperTerminal etc) to receive all logged packets and
communications to and from an attached serial device.  Write access to the
attached serial device and APRS-IS is password protected, while other users
will have read only access.

When used with a Virtual Serial Port (see
http://www.hw-group.com/products/hw_vsp/index_en.html ) applications can
obtain ALogger output, including Serial communications, via existing
application serial port interfaces.  For example, it will now be possible
for APRS-DOS to connect to an ALogger session via it's serial port and to
access the Internet for communications via the APRS-IS.  

ALogger continues to provide the ability to log selected packets to disk for
later review, and to gate selected packets received over the serial port to
the APRS-IS.

ALogger 3.0.0 can be downloaded from http://www.billdiaz.dynip.com

Bill KC9XG

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

Message: 3
Date: Sat, 10 Feb 2007 20:54:52 +0100
From: "Jan T. Pharo" <la2bba_at_jpharo.net>
Subject: Re: [aprssig] RE: European Digipeating standards

"Cap Pennell" <cap_at_cruzio.com>, Sat, 10 Feb 2007 10:57:45 -0800:

>In the US, where as you know we freely travel between our States, as you do
>between European Union states,

(I have read the rest, as well; just wanted to add this comment)

Differently from the USA, Europe is a number of independent states; some
are in the European Union (but still independent), some are not in the
Union (like Norway, Iceland, Switzerland, Liechtenstein). However, we have
an agreement about freedom of travel, and can pass freely between e.g.
Norway (non-EU) and Sweden (EU); unlike the passage over the border between
Canada and USA. So a car driver will be able to drive from the south of
Italy to the North Cape without even stopping (except to sleep, eat, and
fill gas), passing a number of international borders (6, at least). But if
he or she is a radio amateur with APRS, it's necessary to change setup. I
would really welcome a mutual agreement of APRS path standards for this
area.

>Working toward a effective and efficient "universal" path system for VHF
>travelers too?  Think "traceable WIDEn-N"

I do. And I would welcome it. But for quite some time, I see that I and
other APRS hams will have to travel around, remembering where to change
path....

My digi, standing close to the LA/SM border, will for the time being allow
both WIDEn-N (traceable) and TRACEn-N (UIflood, just to let them through)
packets (n<4), and even RELAY. Eventually, it will be reduced to a fill-in,
when our club has set up its digi.

-- 
73 de Jan, LA2BBA
Hvaler, Norway

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

Message: 4
Date: Sun, 11 Feb 2007 07:05:46 +1100
From: Ray Wells <vk2tv_at_exemail.com.au>
Subject: Re: [aprssig] Baycom modem

An HTML attachment was scrubbed...

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

Message: 5
Date: Sat, 10 Feb 2007 12:22:34 -0800
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [aprssig] RE: European Digipeating standards

Jan LA2BBA wrote:
>>Working toward a effective and efficient "universal" path system for VHF
>>travelers too?  Think "traceable WIDEn-N"
>
>I do. And I would welcome it. But for quite some time, I see that I
>and other APRS hams will have to travel around, remembering where to
>change path....
>
>My digi, standing close to the LA/SM border, will for the time being
>allow both WIDEn-N (traceable) and TRACEn-N (UIflood, just to let them
>through) packets (n<4), and even RELAY. Eventually, it will be reduced
>to a fill-in, when our club has set up its digi.
>
>--
>73 de Jan, LA2BBA
>Hvaler, Norway

Thanks!  That's a very helpful interim step, and so easy to setup using
Ui-View32 as a digi!
Fine business!
73, Cap

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




Read previous mail | Read next mail


 01.02.2026 14:30:38lGo back Go up