| |
ZL3AI > APRDIG 30.05.03 09:45l 287 Lines 9393 Bytes #999 (0) @ WW
BID : 1405-ZL3AI
Read: GUEST
Subj: TAPR Digest, May 27, 1/3
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU<ZL3VML
Sent: 030529/1329Z @:ZL3VML.#80.NZL.OC #:1273 [Chch-NZ] FBB7.00i $:1405-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Tuesday, May 27, 2003.
1. Re: Unproto Path
2. Re: Unproto Path
3. Re: Unproto Path
4. Re: Unproto Path
5. Re: Unproto Path
6. PCsat Triple hop!
7. Re: WINAPRS / TCP
8. Re: WinAPRS Crash
9. Re: DB-9 pin outs
10. Re: Jerry Schmitt KK5YY -- SK & Memorial Service
11. Re: Balloon Position Report Page
12. Re: Garmin GPS/FRS RINO
13. RE: DB-9 pin outs
14. Re: Unproto Path
15. VOICE ALERT PL100
16. Re: PCsat Triple hop!
17. Re: VOICE ALERT PL100
18. Re: PCsat Triple hop!
19. Re: 60 buck 120GB Hard Drive
20. Re: Garmin GPS/FRS RINO
21. Re: Unproto Path
22. Unproto path Spell Check
23. Re: Unproto Path
----------------------------------------------------------------------
Subject: Re: Unproto Path
From: "hasan schiers" <schiers@netins.net>
Date: Tue, 27 May 2003 06:51:39 -0500
X-Message-Number: 1
We do it slightly differently (and since we adjoin your coverage area), but
what you suggest will still work in Iowa and contiguous MN,MO,NE.
However:
This is the first time I've seen anyone recommend RELAY in a home station
unproto path. I seem to remember that this was strongly discouraged.
From central Iowa to Minneapolis, Kansas City, Omaha, and Sioux City the
same paths suggested work perfectly now (there is one more digi to convert,
but let's keep it simple)
Mobiles: Relay, Wide2-2
Home: Wide3-3 or Wide, Wide2-2
(Do not put RELAY in your unproto if you are a home station)
(Not that it won't work, it will...but it will also fire off just about
every digi and home owner in the local RF world, thus producing MANY
non-useful packets.)
....hasan, N0AN
>Home User's
>
>Please use the following Wide2-2 or Wide3-3 if your able to get into a
>digipeater direct. If not than use Relay,Wide2-2 or Relay,Wide3-3. This
>unproto is more than enough to communicate through the vast network.
----------------------------------------------------------------------
Subject: Re: Unproto Path
From: "Joseph C. Bender" <n8xre@benderhome.net>
Date: Tue, 27 May 2003 08:26:48 -0400 (EDT)
X-Message-Number: 2
hasan schiers said:
>This is the first time I've seen anyone recommend RELAY in a home
>station unproto path. I seem to remember that this was strongly
>discouraged.
Assuming you can get into a WIDE directly, you shouldn't use RELAY on a
fixed point. That's also what the original email said.
>(Do not put RELAY in your unproto if you are a home station)
>
>(Not that it won't work, it will...but it will also fire off just about
>every digi and home owner in the local RF world, thus producing MANY
>non-useful packets.)
So what would you suggest, then, for a home station that can't get into
the network any other way?
--
Joseph C. Bender
n8xre at benderhome net
----------------------------------------------------------------------
Subject: Re: Unproto Path
From: "Guy Story, KC5GOI" <kc5goi@tapr.org>
Date: Tue, 27 May 2003 07:49:24 -0500
X-Message-Number: 3
If you are new to an area, RELAY for a fixed station is acceptable until you
are able to determine what is your closest WIDE. If you are too far out,
watch for the next closest RELAY to that digi and put it in your path .
Discrete paths for fixed stations are the only way to go.
73
Guy Story, KC5GOI
----------------------------------------------------------------------
Subject: Re: Unproto Path
From: "hasan schiers" <schiers@netins.net>
Date: Tue, 27 May 2003 08:45:18 -0500
X-Message-Number: 4
In our network, we tell people to preface the WIDEn-n with a single WIDE:
(if they need it...most don't)
Wide, WIDE2-2
(again, sticking with the idea that home stations should not put RELAY in
their path)
If they can't reach a wide (we have no one in that circumstance in our
entire network), we would know (because we are a fixed station), and in that
case, put the actual callsign of the digi one CAN reach:
K0BOY-1, WIDE2-2
I can see no justification for a HOME station using RELAY (in our network).
All our STRUCTURED digi's respond to:
RELAY, WIDE, WIDEn-n, TRACEn-n, IA, IOWA
Home stations that are not a STRUCTURED part of the digi network only
support RELAY...and nothing else.
STRUCTURED = a designed part of the digi network, supporting smart
digi-peating. (WIDEn-n, TRACEn-n capable)
I'm not saying how anyone else's network should be set up. This is the way
we do it...and it prevents 20 home stations from firing off due to a widely
heard RELAY. These same 20 stations stay quiet when they hear WIDE, hence a
home path of:
WIDE3-3
or
WIDE, WIDE2-2
accomplishes what is needed. It seems to me that RELAY only invites trouble.
Basically, if you aren't deliberately part of the digi network (and your
efforts have been coordinated with the other digis), you only digipeat RELAY
and nothing else and your path is either WIDEn-n or WIDE, WIDEn-n.
(This of course leaves out the TRACEn-n, which I'm not including in the
discussion. We use TRACEn-n on paths we are trying to evaluate.)
Hope this helps. 73
....hasan, N0AN
----------------------------------------------------------------------
Subject: Re: Unproto Path
From: "hasan schiers" <schiers@netins.net>
Date: Tue, 27 May 2003 08:49:27 -0500
X-Message-Number: 5
Presactly!
Get rid of it (relay) as soon as you know what you are doing. In our area,
you would be notified "somewhat" quickly what the desired path is.
Very good point, Guy. (As long as one remembers to stop using RELAY from
home at the earliest possible opportunity.)
This is why I posted my original comment...I thought it most peculiar that a
network administrator would deliberately tell home users that the preferred
home path started with RELAY.
All I can say to that is ...."not around here".
....hasan, N0AN
----------------------------------------------------------------------
Subject: PCsat Triple hop!
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 27 May 2003 10:09:34 -0400 (EDT)
X-Message-Number: 6
During today's PCsat pass over the east coast, we saw N4ZQ relay a packet
via PCsat, then PCSAT2 (on our workbench) and then back to PCsat. The
PCSAT2 was connected through 180' of coax to a WHIP antenna on the roof!
THe range between satellites was about 1000 km.
PCSAT2 is on the workbench connected to an outside antenna to burn it in.
We are waiting to see when it's 96 hour fail-safe timer times out. I had
forgotten about the possibility of a dual hop test and in fact was just
about to go disconnect PCSAT2, because its packets were interfering with
my demo of PCsat I was showing to a new faculty member.
Anyway, too bad PCsat will probably not be around when PCSAT2 finally gets
to orbit at the end of this year. THis ability to do multiple satellite
hops via multiple APRS satellites has long been a dream of the APRS
comnmunity. We had previously demonstrated this capability between PCsat
and ISS several months ago, but only for a week, because it required ISS
to QSY to the PCSAT frequency.
But if every satellite that does UI digipeating operated on 145.825, then
we would have a mutually supporting constellation of satellites...
de WB4APR@amsat.org, Bob
PCsat WEB page http://www.ew.usna.edu/~bruninga/pcsat.html
PCsat2 WEB page http://www.ew.usna.edu/~bruninga/pcsat2.html
ISS-APRS FAQ: http://www.ew.usna.edu/~bruninga/iss-faq.html
APRS SATELLITES http://www.ew.usna.edu/~bruninga/astars.html
----------------------------------------------------------------------
Subject: Re: WINAPRS / TCP
From: Mark Sproul <msproul@jove.rutgers.edu>
Date: Tue, 27 May 2003 10:08:31 -0400
X-Message-Number: 7
Skip
There is a setting under SETTINGS / TCP/IP Connections / TCP Server
settings that wil AUTO START TCP connection, turn this OFF
Mark
At 9:12 AM -0500 5/24/03, Skip Allison wrote:
>WINAPRS starts up every time trying to connect TCP/IP. I must have done
>something to get it to do that, but I can't figure out what. Anybody
>know how to keep it from connecting to TCP/IP every time I start the
>program?
>
>Skip
>K9SA
------------------------------------------------------------------
Mark Sproul |
http://ecs.rutgers.edu |
msproul@jove.rutgers.edu |
Manager - Engineering Computing Services | 732-445-3121
Rutgers University School of Engineering |
Eng D111 |
------------------------------------------------------------------
----------------------------------------------------------------------
Subject: Re: WinAPRS Crash
From: Mark Sproul <msproul@jove.rutgers.edu>
Date: Tue, 27 May 2003 10:06:55 -0400
X-Message-Number: 8
WinAPRS will auto-reconect, currently WinAPRS has been running 15
days and has re-connected 20 times to second.aprs.net, it is still
running fine. It has processed 15 million packets.
>Mark,
>
>second.aprs.net had been up 7 days when you posted your message :)
>
>Dick
------------------------------------------------------------------
Mark Sproul |
http://ecs.rutgers.edu |
msproul@jove.rutgers.edu |
Manager - Engineering Computing Services | 732-445-3121
Rutgers University School of Engineering |
Eng D111 |
------------------------------------------------------------------
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
