[OZAPRS] Navigator Updates and ZL2 Experience.

Robert Thirkettle rob.thirkettle at canterbury.ac.nz
Tue Feb 3 11:55:30 EST 2009


Hi All that is not correct wide1-1 has worked in Christchurch for more
than a year we never have needed to know the name of the Marleys APRS
digi since it was installed in 1999 probably the first APRS digi in the
country and before the adoption of wide1-X it used the relay wide. Of
course Marley-1 will work as that is its callsign and any TNC will
always allow you to use its callsign

Just because you see Marley-1 in the digi path what you see is UITrace
command working as it should replacing wide1-X with its callsign
Marley-1. I am waiting for the changes to come through from MED/FMTAG
then Marleys will be issued a proper ZL callsign. The H bit * is only
seen on the last station to digi the packet. Looking at raw packet we
have another digi on the air as 
The packets are being digied 2 times and its not Marleys as it would put
in its callsign.

2009-02-02 05:41:25 UTC:
ZL3RX-9>APT311,MARLEY-1,WIDE1*,WIDE3-3,qAR,ZL3TMB:>VHF 

Regards Rob Thirkettle  ZL3RX         
Dept  Physics & Astronomy
University of Canterbury     
Private Bag 4800,         
Christchurch 8020,
New Zealand
Tel: +64 3 364 2510
Fax: +64 3 364 2469
mailto:rob.thirkettle at canterbury.ac.nz


-----Original Message-----
From: ozaprs-bounces at aprs.net.au [mailto:ozaprs-bounces at aprs.net.au] On
Behalf Of Andrew Errington
Sent: Tuesday, 3 February 2009 11:14 a.m.
To: Australian APRS Users
Subject: Re: [OZAPRS] Navigator Updates and ZL2 Experience.

> It seems uniquely NZ to have to know the name of a digi in your area.
> For example, WIDE1-1,WIDE2-2 didn't work last year in Christchurch as
I
> think I needed MARLEY-1,WIDE2-2 or something, and likewise in the Nth
Is
> you have TPO etc that need to be explicitly listed. This makes it
tricky
> for a wanderer with a tracker device and no laptop!

Hear hear!  There is a slow but sure push for streamlining the APRS
infrastructure here, using the new paradigm and a single frequency. 
Unfortunately, over time the APRS infrastructure had become fragmented,
and there is still some reluctance to "un-fragment" it.  However,
progress
is being made (and it's experiences like yours that serve to highlight
*why* we should be doing it).

I'm glad you enjoyed your ZL trip, and thanks for writing about it.

73,

Andrew
ZL3AME

_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs
_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs



More information about the Ozaprs mailing list