| |
ZL3AI > APRDIG 08.06.03 11:06l 144 Lines 5002 Bytes #999 (0) @ WW
BID : 1448-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jun 03, 5/5
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<VK7AX<VK3AC<ZL2BAU<ZL3VML
Sent: 030607/1337Z @:ZL3VML.#80.NZL.OC #:1871 [Chch-NZ] FBB7.00i $:1448-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: PCsat<=>PCSAT2 joint sat test success.
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 3 Jun 2003 20:19:09 -0400 (EDT)
X-Message-Number: 35
On Tue, 3 Jun 2003, Miller Scott Contr 30SCS/FTI wrote:
>Bob, what does this get us? Is it just to extend the effective footprint?
It also doubles the access times (2 are better than one).
>Do you have any analysis of how often the birds will be able to hear each
>other? I just did a quick check and it looks like ISS's footprint is about
>1,000 miles less than PCSAT, but it's still about 2,700 miles. ISS has an
>orbital inclination of about 51 degrees - will PCSAT ever see it from the
>poles?
We did this once before with ISS on orbit. Many people got double hops
in. Furtherst was over 1100 miles I think...
>Maybe I'll run a quick scenario in STK to show access opportunities. I'd
>make a nice animation, but I think my license for the visualization module
>has expired.
The joint opportunities are all over the place as the orbits precess.
Sometimes they intersect for brief ones, and sometimes they overlay each
other for long periods...
But PCsat will be all but dead by the time PCSATA2 gets up there in Jan.
Bob
----------------------------------------------------------------------
Subject: AEA PK-80 TNC
From: "Tom Bethel" <tom@coralwave.com>
Date: Tue, 3 Jun 2003 21:08:44 -0400
X-Message-Number: 36
Does anyone know how to set the terminal dipswitch on this TNC?
Probably best to use 9600?
Is it 8 N 1 ?
Can't find the manual.
It talks to the terminal at 300 baud now.
Thanks
Tom N1GN
----------------------------------------------------------------------
Subject: Re: Questions to the group
From: Rich Garcia <k4gps@bellsouth.net>
Date: 03 Jun 2003 21:12:52 -0400
X-Message-Number: 37
True, the GPS is probably 4800 baud while the TNC is usually 9600. I
often set my dumb tracker TNC to 4800 so I don't goof up a year down the
road when I connect the PC to it again. Are you changing the settings?
Looks obvious but obvious things are not that obvious when frustration
sets in.
Rich
On Tue, 2003-06-03 at 18:12, Dave Thege wrote:
>Did you ck the baud rate? That will cause a tnc to not talk to your
>computer.
>Dave N0XBN
----------------------------------------------------------------------
Subject: Re: Air emergency?]
From: "Dakota Summerhawk" <dakotas@dotorg.org>
Date: Tue, 3 Jun 2003 19:18:01 -0600
X-Message-Number: 38
Maybe its just the Firefighter side of me talking here but if you ARE alone,
then putting your life on the line is nothing more than inviting disaster as
you become a victim as well, we were taught that you should ALWAYS call for
back up in the event that you are alone. If your hurt in the process then
what good does it do? Setting an emergency beacon if you have NO other means
then of course then set it, but if you have the capability to reach someone
OTHER than APRS emergency beacon then do it. My point is try ALL other means
of communications BEFORE setting a emergency beacon.
Dakota
----------------------------------------------------------------------
Subject: RE: AEA PK-80 TNC
From: <BobDonnell@arkalmus.com>
Date: Tue, 3 Jun 2003 18:50:51 -0700
X-Message-Number: 39
Hi Tom, and all
The PK-80 is a true TNC-2 clone - I think all that was added was some
filtering to keep the FCC at bay.
Dip switches 1-5 select the terminal baud rate. Switches 6-8 select the
on-air baud rate. I'm betting that right now you have switch 1 and
switch 6 on. Turning off switch 1 and turning on switch 5 should have
you set up at 9600 bauds, unless that TNC has been modified. All of
this is based on imperfect memory, though. I used to support those when
I worked at AEA, but it's been almost 10 years since I've done that job.
Also, if I recall right, with the standard firmware, the TNC came up in
7E1 communications - but if you can see the signon banner at 300 baud,
you can check - the AWLEN and PAR commands tell you the number of bits
and the parity, respectively. Be aware that your TNC might not
successfully communicate at 9600 bauds. TAPR's design used sections of
an LM-324 op-amp to handle RS-232 signals, and the slew rate
specification for those parts is at or below that slew rate required for
reliable 9600 baud communications. The LM-324 can be successfully be
replaced with a TL074 or TL084 (pin for pin replacement) and these parts
have a much higher slew rate.
Hope that helps!
73, Bob, KD7NM
ex AEA customer support tech
>-----Original Message-----
>From: bounce-aprssig-17768@lists.tapr.org
>[mailto:bounce-aprssig-17768@lists.tapr.org]On Behalf Of Tom Bethel
>Sent: Tuesday, June 03, 2003 6:09 PM
>To: TAPR APRS Special Interest Group
>Subject: [aprssig] AEA PK-80 TNC
>
>Does anyone know how to set the terminal dipswitch on this TNC?
>Probably best to use 9600?
>Is it 8 N 1 ?
>Can't find the manual.
>It talks to the terminal at 300 baud now.
>
>Thanks
>
>Tom N1GN
---
END OF DIGEST
Read previous mail | Read next mail
| |
