| |
CX2SA > SATDIG 02.07.05 15:31l 208 Lines 8767 Bytes #999 (0) @ WW
BID : 5240_CX2SA
Read: GUEST
Subj: AMSAT-BB-digest V2004 #774 7/7
Path: DB0FHN<DB0RGB<DB0MRW<DB0PV<DB0AAB<F6KFT<LX0PAC<ON0LGE<ON0DXC<WA7V<
CX2SA
Sent: 050702/0330Z @:CX2SA.LAV.URY.SA #:5240 [Minas] FBB7.00e $:5240_CX2SA
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Message: 16
Date: Fri, 1 Jul 2005 20:47:08 -0400
From: "Edward J. Polack" <epolack@earthlink.net>
Subject: RE: [amsat-bb] K4HTA satellite experience.
Very nice experience! Ed N8EQJ
- -----Original Message-----
From: owner-AMSAT-BB@amsat.org [mailto:owner-AMSAT-BB@amsat.org] On
Behalf Of Iain McFadyen
Sent: Thursday, June 30, 2005 11:46 PM
To: amsat-bb@amsat.org
Subject: [amsat-bb] K4HTA satellite experience.
K4HTA is the Vienna Wireless Society (Vienna, Virginia, USA).
Some 8 weeks ago, during the 'show and tell' portion of our local club
meeting, I stood up and announced that a new satellite had been launched
from India (VO-52). Someone at the back of the room shouted "...Looks
like
we've found our Satellite station captain for Field Day!!"
Protesting loudly didn't change the situation: But a whole slew of
volunteers approached me and loaned me an FT-847, Arrow,
Yaesu5500/GS232,
and various other components of a satellite station. I enjoy a
challenge...
In the last few weeks, I have had eight satellite contacts on VO-52 and
FO-29, with a couple of attempts on AO-51 (V/U) and SO-50. These
contacts
were made from the balcony of my 12th floor condo in McLean, VA. I have
a
clear semi-circular outlook centred on NNW.
So it was with some trepidation, that I packed up all the kit into the
truck and disappeared off in the direction of the Field Day site. We
substituted a 5ele+5-ele cross-Yagi on 145 with a RHCP phasing harness,
and
an 11-turn helix on 435 for Field Day. (These wouldn't fit on the
balcony!!).
We completed the station setup almost on time, but just missed the
first
satellite pass of Field Day (VO-52 at 1800UTC, on a 3degree elevation
pass
to the West).
I had already pre-selected VO-52, FO-29, SO-50, AO-7, AO-27, and ISS in
the
Satscape screen, and told Satscape to automatically track satellites in
range. There were some long periods of inactivity in the schedule for
our
location, so I went in to Satscape and added all the Iridium satellites
to
the selected satellites. The Az/El rotor proceeded to track the Iridium
satellites across the sky, starting at AOS and successfully following
the
predicted paths to LOS. Great!
So, just before FO-29 appeared for its first visible pass at our
location,
I de-selected all the Iridium satellites and waited for the rotor to
start
following FO-29.
Hmmm.... nothing heard at AOS. A quick look out of the window of the
van
(the operating position was in a converted Ford Van), and I was shocked
to
see that though the Satscape program was predicting the satellite to be
at
051 degrees azimuth and 4 degrees elevation, but the rotor and antennas
were
pointing at 051 degrees and 45degrees!!!
Quickly put the system in manual, forced the elevation down to 4
degrees,
and completed our Club's first Field Day satellite contact in almost a
decade (last sat contact was using HF!)
I re-enabled the Iridium satellites in the selection list and the rotor
continued to behave itself perfectly. I disabled Iridium and waited for
the
next useable Amateur satellite pass: Can't remember but I think it was
SO-50. It tracked SO-50 successfully though no successful contact.
Here comes FO-29 again: Oh no! The Az/El mount is again pointing at a
ridiculously high elevation compared to the predicted pointing
information.
I rebooted everything: The PCs, Satscape, the GS232, the 5500
controller,
and waited for the next pass. Success! Now the array was successfully
tracking correctly!
FO-29 proved to be difficult to get any more contacts. So I switched
over
to VO-52, and made the second Field Day contact on VO-52. Oh so easy!
The
UHF-up/VHF-down frequency relationship makes things so much easier: The
VHF-up/UHF-down configuration causes us problems with spurious (3rd
harmonic
or thereabouts) from the VHF transmitter.
Every time the ISS flew within range a whole group of listened on
*every*
ISS pass to see if there was any voice activity. All passes observed
here
were packet only on 145.800. I'm puzzled by those people reporting
successful FIeld Day voice contacts. Was there voice activity on a
different
frequency?
Strange co-incidence, but all our Field Day contacts by satellite were
with
stations in MN! Thanks to all those who helped us complete this
challenging
task!
Iain KI4HLV Satellite station Captain: K4HTA. FM18jw Fairfax County,
Virginia, USA.
- ----
Sent via amsat-bb@amsat.org. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
- ----
Sent via amsat-bb@amsat.org. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
------------------------------
Message: 17
Date: Fri, 1 Jul 2005 21:16:54 -0500
From: "George Henry" <ka3hsw@earthlink.net>
Subject: Re: [amsat-bb] 2005 Field Day Fun on the Satellites ( l o n g )
- ----- Original Message -----
From: "John P. Toscano" <tosca005@tc.umn.edu>
To: <amsat-bb@amsat.org>
Sent: Wednesday, June 29, 2005 11:40 PM
Subject: [amsat-bb] 2005 Field Day Fun on the Satellites ( l o n g )
(much snippage...)
> More planning: satellite passes. In the past, I had used either Predict
> or STS-Plus for real-time tracking on my old Pentium laptop running
> Windows 95. That laptop is history, my current laptop is a Pentium III
> running Windows 2000, and I could not get either program to run on it!
> Ouch. Though I haven't given up on them yet, I didn't have time to figure
> out the solution to the problems by Field Day.
There are instructions on Dave Ransom's STS-Plus page for setting it up to
run under Win 2K. See www.dransom.com/stsplus.html & scroll down, or
download from ftp.dransom.com/stsplus/stswin2k.zip . There are also a
number of free or shareware programs for download from the AMSAT web site
which will work under Win 2K, and Erich Eichmann (DK1TB) has made a demo
version of his wonderful SatPC32 program available which is only very
slightly "crippled" compared to the registered version.
>
> So how did we do?
>
> I was modestly successful on AO-7, but there were a number of Mode A
> passes, and I had no 10M antenna to work those with. I seemed to struggle
> a bit to match my uplink and downlink frequencies, but there were usually
> plenty of stations that I could hear clearly in the passband on the Mode B
> passes.
For several Field Days now, I have used a simple 10M dipole made from 1/2"
copper water pipe screwed to a chunk of 2x4 with a couple of U-bolts to
clamp it to a 1-1/2" mast, with great success. Knocks down to
next-to-nothing for transport. Had a matching one for 15M before RS-12/13
went silent....
>
> I was not at all successful on FO-29. This was a bit of a surprise to me,
> since I have worked it quite a few times from home, with the same radio,
> plus preamps and power amps as needed, plus un-butchered antennas that do
> not elevate. Passband activity seemed light, signals to me were weak, and
> I never managed to hear my own echoes during any of the passes. It does
> seem to be true that mode V/U is harder to operate than mode U/V, at least
> with my limited experience.
>
Hmmmm... I had success on all 6 phone birds. Got AO-27 first, then I forget
what order the rest came in. My final count was 14 Q's, most on AO-7,
FO-29, and VO-52. Spent a while talking to myself on one mode-A pass of
AO-7 before someone else showed up and answered me. V/S on AO-51 was neat.
Great signals, although very congested, and there were some very rude
operators who couldn't seem to let any 2 stations complete an exchange
without throwing their calls and reports over top of them... Heard the ISS
on voice on 2 passes, but no luck. Audio on downlink was very low, and
packet bursts kept covering his voice... I suspect that he did not
disconnect the TNC.
I really would like to see the ARRL adopt AMSAT's one-QSO-per-FM-satellite
rule, but so far they have refused. Maybe the control teams need to present
a unified front to the League, and then they'll finally get it.............
George, KA3HSW
- ----
Sent via amsat-bb@amsat.org. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
------------------------------
End of AMSAT-BB-digest V2004 #774
*********************************
----
Sent via amsat-bb@amsat.org. Opinions expressed are those of the authors.
Not an AMSAT member? Join now to support the amateur satellite program!
To unsubscribe, send "unsubscribe amsat-bb-digest" to Majordomo@amsat.org
Read previous mail | Read next mail
| |