| |
ZL3AI > APRDIG 26.11.06 01:01l 239 Lines 9287 Bytes #999 (0) @ WW
BID : 9137-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 29 #22, 3/4
Path: DB0FHN<DB0MRW<DK0WUE<I0TVL<IW8PGT<VK4TRS<ZL2BAU
Sent: 061125/2355Z @:ZL2BAU.#79.NZL.OC #:17072 [Waimate] $:9137-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 17
Date: Fri, 24 Nov 2006 21:42:16 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Point-to-point telemetry addressing
>>W9IP-2's path to W9IP-1 would be APRS,KB2FAF-10,K2AMB-3,W9IP-1
>
>Why are you including your own stations at the end of the path?
Agree. In some TNC's if the own-stantion TNC digipeats a packet, then it
does NOT appear to that own-station TNC serial port unless certain
parameters are set just right.
>If the device doing the telemetry is a stand-alone TNC rather
>than a program running on a PC, the path will be entered into
>it's hardware using an ASCII terminal program for setup. It
>will be something like: "APRS via KB2FAF-10,K2AMB-3" [Exact
>syntax will vary depending on the particular TNC being used.]
The KPC-3+ is ideal not only for 5 channels of telemetry, but also for
giving you remote control of up to 4 separate on/off circuits. So you can
monitor the temperature and then any time you want, logon remotely with the
pasword protected remote sysop mode and turn the switches on and off.
We use these TNC's all the time for telemery command and control this way.
See our mods (about half way down this page):
http://www.ew.usna.edu/~bruninga/labsats.html
WB4APR, Bob
------------------------------
Message: 18
Date: Fri, 24 Nov 2006 19:00:54 -0800
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [aprssig] Point-to-point telemetry addressing
Michael, your neighborhood has a lot of mis-configured stations and
digipeaters, and stations with obsolete settings. It's a shame that their
settings haven't been optimized because it makes using the VHF network more
difficult and because it makes understanding how that network is operating
more difficult too.
Although the KB2FAF-10 IGate is porting what it hears on VHF into APRS-IS
(Internet Stream), there's no indication that KB2FAF-10 does any
_transmitting_ on VHF. I'd suggest trying to digipeat through the nearby
KB2LUV-1 station instead of KB2FAF-10.
So then,
W9IP-1's path to W9IP-2 would be APRS,K2AMB-3,KB7LUV-1
and
W9IP-2's path to W9IP-1 would be APRS,KB7LUV-1,K2AMB-3 or maybe simply
APRS,K2AMB-3 would work.
A couple of points.
Michael, your W9IP-1 position shows as being in an exactly the same location
as K2AMB-3 and W9IP-1's map symbol shows as an obsolete type of digipeater
too, but W9IP-2 is not producing a valid position packet at all.
RELAY and WIDE and TRACE are long obsolete (at least in North America).
Courteous modern routine (generic) digipath, Base:WIDE2-2
Mobile:WIDE1-1,WIDE2-1.
73, Cap KE6AFE
-----Original Message-----
>From: aprssig-bounces_at_lists.tapr.org
>[mailto:aprssig-bounces_at_lists.tapr.org]On Behalf Of Michael R. Owen
>Sent: Friday, November 24, 2006 15:44 PM
>To: scott_at_opentrac.org
>Cc: 'TAPR APRS Mailing List'
>Subject: Re: [aprssig] Point-to-point telemetry addressing
>
>Scott -
>
>I forgot to mention that I'm using a homebrew program. It sets the UNPROTO
>address list of the THC (A TNC-2 clone), then sends the message as a UI
>packet. If I don't include APRS as the first entry in the address list,
>nobody will digipete the message.
>
>W9IP
>
>scott_at_opentrac.org wrote:
>However, neither of these appear to work. The only addressing that
>seems to work is APRS,WIDE2-2, but that only works from time to time,
>
>APRS should not be part of your path, unless you're using a program that
>takes the first entry as the destination callsign. I forget which ones do
>that. Do you have an example of one of your packets after it's been
>digipeated? That might tell you what's going on.
>
>Scott
>N1VG
>--
>Michael R. Owen, Ph.D.
>Northern Lights Software Associates
>http://www.nlsa.com
------------------------------
Message: 19
Date: Fri, 24 Nov 2006 22:07:12 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Point-to-point telemetry addressing
>There is a good APRS digipeter (K2AMB-3) near W9IP-1 and another good
>one (KB2FAF-10) near W9IP-2.
Several comments come to mind and I appologize if I appear to be frustrated
by the lack of fundamental information in the nearby digis. But this
example shows exactly why the initiatives of the New-N Paradigm are so
important to network determination:
It is clear why WIDE2-2 wont work:
Looking at KB2FAF-10 on FINDU.COM,
http://www.findu.com/cgi-bin/find.cgi?kb2faf-10
there is nothing to indicate it is a digipeater or supports any of the
modern APRS digipeating functions. It is an Igate. It has no mention of
support for WIDEn-N digipeating and most importanly, it shows no indication
of its PHG data which is fundamental to a digipeater so people can infer
its relative coverage. Without a digi symbol and without PHG data, it
could be an HT in someone's basement serving only as an IGate.
You say it is "near W9IP-2" but you also say the "terrain is rough". Since
the KB2FAF-10 station has no PHG data, the word "near" is practically
meaningless. It could be 1 mile away by LAT/LONG, but could be in a
basement on an HT and have a worse path by far than a good digi 20 miles
away that is on a good high site. This is why PHG (Power-Height-Gain data)
is fundamental to APRS and why all fixed APRS stations (home and digis)
should include this data in their beacons.
Looking at K2AMB-3:
http://www.findu.com/cgi-bin/find.cgi?k2amb-3
This digi has a good PHG, but it also has none of the modern
APRS indication of the proper settings for an APRS digipeater:
* it is using an obsolete WIDE,WIDE,WIDE path
* It does not indicate the type of TNC in its header,
* it does not indicate its support of WIDEn-N, or limits on N
* it does not indicate its support of Nyn-N
* It does inidcate it is a TRACE digi which is obsolete
So it appears to me this digi does not support WIDEn-N in the first place.
The owner of this digi needs to update its settings in accordance with the
2004 recommendations for the New-N Paradigm. Since it is an old PACCOMM
digi, it can be made to work using those parameters found on this page:
http://www.ew.usna.edu/~bruninga/aprs/PacComm-settings.txt
And see this page for all the reasons that old digis like the two in your
area need to be set to proper settings..
http://www.ew.usna.edu/~bruninga/aprs/fix14439.html
Hope this helps.
Bob, WB4APR
------------------------------
Message: 20
Date: Fri, 24 Nov 2006 20:41:58 -0800
From: Warren Kean <ve7dpg_at_telus.net>
Subject: [aprssig] help with proper paths
Hi everyone,
I am new to the group, and my question is about the proper path to use
when trying to get packets through pcsat or pcsat11 or ariss ? I am
using a tiny trak3 and a d700 and would like to get my beacons too show
up on findu. and also what timing is recommended.
thanks Warren
------------------------------
Message: 21
Date: Sat, 25 Nov 2006 09:35:32 -0500
From: "Amir's email" <sarlabs_at_twcny.rr.com>
Subject: RE: [aprssig] Point-to-point telemetry addressing
Bob and all:
I live outside Syracuse NY and with your permission, I will forward your
post to one of the guys who is taking care of K2AMB-3 (Coordinator of the
County SAR team) so maybe something might change there.
73 de K9CHP, Amir Findling, member ARRL, AMSAT #36083
1st Special Response Group (1SRG) http://www.1srg.org/
Apprentice Tracker, Joel Hardin Professional Tracking Services
http://www.jhardin-inc.com/index.htm
------------------------------
Message: 22
Date: Sat, 25 Nov 2006 10:03:21 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] help with proper paths
>...my question is about the proper path to use
>[for]... pcsat or pcsat11 or ariss ?
The desired ultimate path is VIA APRSAT so that all APRS satellites would
respond to that path. But to be compatible with ARISS, we also give all
APRS satellites the alias of ARISS too. So I receommend VIA ARISS.
Now, if you want to ping off of PCSAT-1 which is semi-operational and in
this default mode, defaults to the callsign of W3ADO-1, then you have to
use its specific call (VIA W3ADO-1). You may get packets through PCSAT-1
when it is in good sun, but we do not expect it to fully recoever until
the first week of January. This should be very exciting when we will have
three APRS satellites in constellation on 145.825 supporting the aliases of
APRSAT and ARISS.
>I... would like to get my beacons to show up on findu.
>and also what timing is recommended.
Be sure to use a MYCALL for your station with a separate SSID for space
operations than terrestrial, because if you use the same call for
terrestrial, then FINDU will overwrite any data you got through the
satellite.
Unatteneded operation is not generally welcome except for special
circumstances or tests. If unattended, we recommend a 5 minute rate. You
won't get in every orbit, but you will get in once a day maybe. If you are
trying to make QSO's and are manning the pass, then a 1 minute rate is
fine.
But with PCSAT-1 hibernating and ARISS off the air, the only digipeater in
space right now is ECHO (AO-51) operating at 9600 baud. We are not sure if
there are any Igates monitoring the dowlink of this bird and feeding into
FINDU. On ECHO, you must use the path of VIA PACB-1.
De Wb4APR, Bob
------------------------------
Read previous mail | Read next mail
| |
