| |
ZL3AI > APRDIG 25.02.04 14:22l 121 Lines 3852 Bytes #999 (0) @ WW
BID : 2902-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 23, 3/3
Path: DB0FHN<DB0FOR<DB0MRW<DB0SON<DB0ERF<DB0FBB<DB0IUZ<DB0GOS<ON0AR<ON0AR<
VK3TE<VK6ISP<ZL2TZE<N1UAN<ZL2BAU<ZL2BAU<ZL3VML
Sent: 040225/1150Z @:ZL3VML.#80.NZL.OC #:19822 [Chch-NZ] FBB7.00i $:2902-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Wider paths than Wide2-2
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Mon, 23 Feb 2004 16:11:18 -0600
X-Message-Number: 21
Maybe not, but your packets from west Texas and NM quite often come into
the DFW area where we do have a high channel load. Having digipeaters
and home stations ID'ing with WIDE5-5 and above do cause interference in
the DFW area even though not intended. I, for one, don't care to see a
Midland or Roswell digi show up on RF in the DFW area. Point being:
just because your area has a low channel load doesn't mean that 2 or
three digis away isn't a completely different story.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Satellite Orientation
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Mon, 23 Feb 2004 18:03:43 -0500
X-Message-Number: 22
To help users visualize the orientation of small Satellites and how it
changes during a pass, I prepared a WEB page with projections of the
satelite vectors across the sky.
http://web.usna.navy.mil/~bruninga/attitudes.html
For what its worth...
Bob, WB4APR
----------------------------------------------------------------------
Subject: Re: Wider paths than Wide2-2
From: Frank - KG6JVE <kg6jve@pasadena.net>
Date: Mon, 23 Feb 2004 14:56:48 -0800 (PST)
X-Message-Number: 23
We see the same thing in the Los Angeles area. I can frequently see
stations from Utah. LA area is very well loaded. And the areas that are
wide open have set paths much wider than WIDE2-2.
Frank
On Mon, 23 Feb 2004, AE5PL Lists wrote:
>Maybe not, but your packets from west Texas and NM quite often come into
>the DFW area where we do have a high channel load. Having digipeaters
>and home stations ID'ing with WIDE5-5 and above do cause interference in
>the DFW area even though not intended. I, for one, don't care to see a
----------------------------------------------------------------------
Subject: Re: Wider paths than Wide2-2
From: Earl Needham <needhame1@yucca.net>
Date: Mon, 23 Feb 2004 16:09:38 -0700
X-Message-Number: 24
At 03:11 PM 2/23/2004, AE5PL Lists wrote:
>Maybe not, but your packets from west Texas and NM quite often come into
>the DFW area where we do have a high channel load.
Not to be rude, but can you send me a sample packet from my station? MELROZ
has been down for a while now, and I can barely reach BLKWTR "sometimes",
so am on the TCP/IP feed more than RF.
Thanks,
Earl
Earl Needham, KD5XB, Clovis, New Mexico DM84jk
KD5XB-2>APW251,PCSAT-1%:=3425.83N/10313.55W-PHG7150/WinAPRS 2.5.1
-EARL_CLOVIS -251-<630>
SETI@Home: 11366WU/7.37yrs
----------------------------------------------------------------------
Subject: Re: Wider paths than Wide2-2
From: Mark Cheavens <mcheavens@usa.net>
Date: Mon, 23 Feb 2004 18:13:02 -0600
X-Message-Number: 25
The problem is usually in the morning and it is from the "normal" band
openings.
Over the Christmas holidays one morning I had LOTS of packets from South
Florida with a path of Wide3-3... At my I-Gate in SW Colorado! Some of the
packets were relay, wide, wide or Trace3-3. The path was South Florida,
West Texas, Durango.
The ONLY solution to all the problem is smart digipeaters! Change the path
on the fly by using the originators position location!
These were 2k miles plus.
Mark Cheavens
KC5EVE
At 04:09 PM 2/23/2004 -0700, Earl Needham wrote:
>At 03:11 PM 2/23/2004, AE5PL Lists wrote:
>>Maybe not, but your packets from west Texas and NM quite often come into
>>the DFW area where we do have a high channel load.
>
>Not to be rude, but can you send me a sample packet from my
>station? MELROZ has been down for a while now, and I can barely reach
>BLKWTR "sometimes", so am on the TCP/IP feed more than RF.
>
>Thanks,
>Earl
---
END OF DIGEST
Read previous mail | Read next mail
| |
