| |
ZL3AI > APRDIG 14.03.03 09:26l 145 Lines 5051 Bytes #999 (0) @ WW
BID : 1016-ZL3AI
Read: GUEST
Subj: TAPR Digest, Mar 10, 1/1
Path: DB0FHN<DB0RGB<DB0FSG<DB0ZKA<DB0GPP<DB0LX<DB0RBS<DB0SWR<DB0MW<DB0IDN<
DB0AIS<DB0ZDF<DB0GE<LX0PAC<LX0HST<HA3PG<VK3AVE<VK6HGR<ZL2BAU<ZL3VML
Sent: 030313/0953Z @:ZL3VML.#80.NZL.OC #:61604 [Chch-NZ] FBB7.00i $:1016-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, March 10, 2003.
1. Re: Packet error problem
2. RE: APRS everywhere in USA.
3. Re: Packet error problem
4. RE: APRS everywhere in USA.
----------------------------------------------------------------------
Subject: Re: Packet error problem
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 10 Mar 2003 09:31:23 -0500 (EST)
X-Message-Number: 1
On Sun, 9 Mar 2003, Earl Needham wrote:
>
>I have a neighbor who occasionally operates APRS, and using AGWPE and
>WinAPRS at my end, his position packets look like this:
>
>XXXXXX>APW246,RELAY,WIDE:@090514z3443.40N/10322.78W-110/000/ -246-<530>
>
>Obviously, there is something wrong with the packet, and it won't display
>in WinAPRS. The little boxes shown above are actually spades (like in
>cards) when they show up.
WinAPRS is apparently configured to send Ctrl E's to the "TNC" and those
are causing the problem. Ctrl E's are the signal for causing PACCOM and
some other TNC's to output GPS data. SIMly reconfigure your WinAPRS not
to do that and it should work...
Bob
----------------------------------------------------------------------
Subject: RE: APRS everywhere in USA.
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 10 Mar 2003 09:34:42 -0500 (EST)
X-Message-Number: 2
On Sun, 9 Mar 2003, Phil Pacier, AD6NH wrote:
>On 03/08/03, "Bob Bruninga <bruninga@usna.edu>" wrote:
>
>>Sure,
>>Yes, whenever you are out of range of the terrestrial system, just QSY
>>your radio to 145.825 and you will get in when PCSAT flies over... with no
>>change in settings..
>
>But still listen to 144.39 for the downlink, correct? Xmit on 145.825 and
>listen on 144.39?
No, PCSAT has two independent digipeaters. One operates simplex on
145.825 and the other operates with a downlink on 144.39 and an
unpublished uplink for special events, travelers, or test purposes...
Bob
----------------------------------------------------------------------
Subject: Re: Packet error problem
From: Earl Needham <needhame@yucca.net>
Date: Mon, 10 Mar 2003 08:53:33 -0700
X-Message-Number: 3
At 09:31 AM 3/10/2003 -0500, Bob Bruninga wrote:
>On Sun, 9 Mar 2003, Earl Needham wrote:
>>I have a neighbor who occasionally operates APRS, and using AGWPE and
>>WinAPRS at my end, his position packets look like this:
>>
>>XXXXXX>APW246,RELAY,WIDE:@090514z3443.40N/10322.78W-110/000/
>-246-<530>
>>
>>Obviously, there is something wrong with the packet, and it won't display
>>in WinAPRS. The little boxes shown above are actually spades (like in
>>cards) when they show up.
>
>WinAPRS is apparently configured to send Ctrl E's to the "TNC" and those
>are causing the problem. Ctrl E's are the signal for causing PACCOM and
>some other TNC's to output GPS data. SIMly reconfigure your WinAPRS not
>to do that and it should work...
Well, I WOULD, but I don't have access to my neighbors equipment...
Also, it's odd, but when I stopped using AGWPE and instead
connected directly to the TNC, the problem went away.
7 3
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: 10480WU/6.84yrs!
Spambot Bait:
root@localhost
postmaster@localhost
admin@localhost
abuse@localhost
spam@primenet.com
abuse@[127.0.0.1]
postmaster@[127.0.0.1]
root@[127.0.0.1]
admin@[127.0.0.1]
billing@[127.0.0.1]
----------------------------------------------------------------------
Subject: RE: APRS everywhere in USA.
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 10 Mar 2003 18:16:52 -0000
X-Message-Number: 4
I tried PCSat for the first time over the weekend, but my results weren't so
good. I managed to get in on three separate passes, with a total of five
packets making it back down to the APRS-IS. However, I wasn't ever able to
copy the downlink myself. I was using a KPC-3 and an old Yaesu FT-203R with
a 1/4 wave ground plane vertical on the roof with maybe 30 feet of low-loss
RG-8. The TNC and radio are in the garage with the server rack, so I wasn't
able to monitor the received audio directly, but I was also listening with a
Pro-79 scanner and MFJ-1714 1/2 wave vertical. During one pass on Saturday,
I could hear the downlink, but it was too weak for the KPC-3 to pick up. I
tried running AGWPE with the scanner, but it locked up due to a software
conflict and by the time I got it sorted out the pass was over.
Any suggestions? My primary suspect is the cheesy 1/4 wave - I threw it
together one day from an SO-239 connector and some steel rod - but it works
pretty well for terrestrial use.
And while we're on the subject, can anyone recommend a good FM/SSB 2M base
unit with good computer control capabilities? I don't care if it's totally
faceless as long as it's got a good computer interface. Preferably one
suited to a server environment - i.e., not a Windows user interface with no
programmatic access.
Scott, N1VG
---
END OF DIGEST
Read previous mail | Read next mail
| |
