[Date Prev][Date Next][Thread Prev][Thread Next] - [Date Index][Thread Index][Author Index]

Re: Re: 147.585 during Leonids

Good Evening Tim et al:  The leonid coordinated frequency 147.585 is also
used as a DX packet cluster station in central SC.  I alternate between
145.79 and 147.585 (depending on local traffic on 147.585) with my KLM sat
antennas pointed NE, N, NW and W from SC.  I saw no visuals nor did I get
any screen prints last night.  I thought the Nov/QST article was very
helpful in setting up. Things were dead at my QTH.  My power out was about
150watts with my antennas elevated 20 degrees.  I will try again Thursday
evening.  Good luck to all the meteor scatter/aprs folks.  Al

----- Original Message -----
From: Tim Cunningham <tim_cunningham@mindspring.com>
To: APRS Special Interest Group <aprssig@tapr.org>;
<aprs@lists.monterey.edu>; VHF reflector <vhf@w6yx.stanford.edu>
Cc: <amsat-bb@AMSAT.Org>
Sent: Thursday, November 18, 1999 3:14 PM
Subject: Re: [amsat-bb] Re: 147.585 during Leonids

> So far I have received conformation from 2 stations on receiving my
> APRS beacons last night via Leonids Meteor Scatter.  Stations reporting
> the reception were from Texas and North Dakota.  The stations that
> received my signal reported they were using omni-directional antennas.
> Signal to noise ratio is certainly a major issue along with many other
> factors when attempting this type of communication via FM transmission.
> I was unable to decode any packets from this end, except for those within
> 100 miles.  The best thing about APRS is that it is automated so you do
> lose any sleep or that is the theory.  You turn on the system, let it run,
> and
> hope you see some magic appear on the map when you wake in the
> morning.  Of course, this is the wishful thinking mode.  It really takes
> more
> work and understanding to make successful contacts since there is no
> immediate feedback.
> I was transmitting approximately 35.27 dBw using the following:
> Ant = M2 2MCP22 (RHCP)
> Radio = Yaesu FT-736R (147.585 MHz FM)
> TNC = Paccom TNC-200
> S/W = APRSdos version 844
> Amp = 300W
> This is basically what it took for some distant stations using
> omni-directional
> antennas on the receiving end.  The real question is where did I have my
> antenna pointed.  The answer is at the horizon to maximize distance. I
> failed
> to document where and when I moved my antennas this morning to correlate
> the reception reports.  That will be a lesson learned for the next Meteor
> Shower
> with software driving the antennas and logging the direction and time.
> what
> I need, another project to work on...  ;-)
> I learned that I am still learning...
> 73's,
> Tim - N8DEU
> Huntsville, AL
> -----Original Message-----
> From: Clifford Buttschardt <cbuttsch@slonet.org>
> To: VHF reflector <vhf@w6yx.stanford.edu>; Emil Pocock
> <pocock@ecsuc.ctstateu.edu>; Dave Smith <drs6@pge.com>;
> aprs@lists.monterey.edu <aprs@lists.monterey.edu>
> Cc: amsat-bb@AMSAT.Org <amsat-bb@AMSAT.Org>; wb7dhc@nwlink.com
> <wb7dhc@nwlink.com>
> Date: Thursday, November 18, 1999 12:58 PM
> Subject: [amsat-bb] Re: 147.585 during Leonids
> >I am grossly disappointed in the APRS results so far!  Signals are
> >coming in but the signal to noise ratio required to cause APRS to print
> >just too large!  A short check on 144.39 confirms the ability to print
> >with big signals.  From 0200 to 0400 PST visual meteors were outstanding!
> >Quite a show.  SSB voice remains effective however.  Cliff K7RR, CM95ni
> >
> >
> >
> >----
> >Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
> >To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
> ----
> Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
> To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org

Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org