OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
CX2SA  > SATDIG   30.01.09 23:12l 383 Lines 12623 Bytes #999 (0) @ WW
BID : 5175-CX2SA
Read: GUEST
Subj: AMSAT-BB-digest V4 49
Path: IZ3LSV<IQ3GO<SR1BSZ<SP7MGD<CX2SA
Sent: 090130/2105Z @:CX2SA.LAV.URY.SA #:5175 [Minas] FBB7.00e $:5175-CX2SA
From: CX2SA@CX2SA.LAV.URY.SA
To  : SATDIG@WW


Today's Topics:

1. Re: homebrew Loop yagi (John B. Stephensen)
2.  ISS Packet Mode 145.825 (Tony)
3.  ISS and APRS with a TT3+ ? (racer5039)
4. Re: AO-51 s-band (Greg D.)
5. Delfi-C3 / DO-64 status update January 30th 2009	10:00	UTC
(Dave Aitch)
6. Delfi-C3 / DO-64 status update January 30th 2009	1128/1141
UTC (Dave Aitch)
7. Re: Delfi-C3 / DO-64 status update January 30th	20091128/1141
UTC (Alan P. Biddle)
8. Re: homebrew Loop yagi (Glen Zook)
9. Re: homebrew Loop yagi (Nigel Gunn G8IFF/W8IFF)
10. Re: ISS and APRS with a TT3+ ? (Robert Bruninga)


----------------------------------------------------------------------

Message: 1
Date: Thu, 29 Jan 2009 21:29:20 -0000
From: "John B. Stephensen" <kd6ozh@xxxxxxx.xxx>
Subject: [amsat-bb] Re: homebrew Loop yagi
To: <w7lrd@xxxxxxx.xxx>, "NW VHF" <PNWVHFS@xxxxxxxxxxxx.xxx>,
	"AMSAT-BB" <AMSAT-BB@xxxxx.xxx>
Message-ID: <260EC4F24A4D4A73A319C93CBF570494@xxxxxxxxxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original

I've have two directive systems loop yagis. The bandwidths are only slightly
wider than yagis with straight elements so dimenional tolerances will be
about the same. They are similar to HF quads. Each element behaves like 2
stacked dipoles with bent ends. The only unforgiving antena is a helix.

73,

John
KD6OZH

----- Original Message -----
From: <w7lrd@xxxxxxx.xxx>
To: "NW VHF" <PNWVHFS@xxxxxxxxxxxx.xxx>; "AMSAT-BB" <AMSAT-BB@xxxxx.xxx>
Sent: Thursday, January 29, 2009 18:25 UTC
Subject: [amsat-bb] homebrew Loop yagi


> Hello
> I am looking for some brain power from anyone who has built loop yagi's.
> I am getting my information from The ARRL Antenna book 20th edition.   The
> book says follow exactly, however.  It calls for alluminum elements 0.0325
> thick, I have copper 0.025 thick.  It calls for 3/4" alluminum boom I have
> 3/4 copper and some 1/2" stainless steel channel.  The feed to the driven
> element is UT-14, I have a  short piece with a SMA already attached, will
> connecting the SMA to a SMA-N adapter be acceptable?  I have seen the
> pretty pictures of Directive Systems antennas
> http://www.directivesystems.com/loopyagi.htm
> Same idea only different parts.  Are these things pretty "forgiving" or
> are the components critical?  Also comparing the loop to a quagi the loop
> widths are 1/4" wide and the quagi used #18 wire, why?  My intent is
> satellites and/or terrestial.  Thanks for the bandwidth.
> 73 Bob W7LRD
> CN87
> AMSAT 28498
>
> --
> "if this were easy, everyone would be doing it"
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb



------------------------------

Message: 2
Date: Thu, 29 Jan 2009 19:49:07 -0500
From: Tony <dxdx@xxxxxxxxx.xxx>
Subject: [amsat-bb]  ISS Packet Mode 145.825
To: amsat-bb@xxxxx.xxx
Message-ID: <AB3170F1083046499F69CC5553C5699F@xxxxxx>
Content-Type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original

ISS still in packet mode (APRS) 145.825...

Tony - K2MO


------------------------------

Message: 3
Date: Thu, 29 Jan 2009 20:58:45 -0600
From: "racer5039" <racer5039@x.xxx>
Subject: [amsat-bb]  ISS and APRS with a TT3+ ?
To: "AMSAT BB" <amsat-bb@xxxxx.xxx>
Message-ID: <BLU102-DAV3711C9156360C8FDEC1BBACC60@xxx.xxx>
Content-Type: text/plain;	charset="iso-8859-1"

Is there a way to set up my TT3+ to send APRS to the ISS ?

Can someone share a setup if there is.
Thanks.

Marv.
N0FJP

------------------------------

Message: 4
Date: Thu, 29 Jan 2009 21:23:59 -0800
From: "Greg D." <ko6th_greg@xxxxxxx.xxx>
Subject: [amsat-bb] Re: AO-51 s-band
To: <apbiddle@xxxxxxx.xxx>, <kelby.davis@xxx.xxx.xxx>,
	<amsat-bb@xxxxx.xxx>
Message-ID: <BLU133-W41A960FE61FEA6A8153522A9C60@xxx.xxx>
Content-Type: text/plain; charset="Windows-1252"


Another factor is that the passes this time aren't favorable in the Western
portion of this country; I have a mode S downlink capability from AO-40's
days, but the bird isn't in view except while I'm off at work or asleep.
Maybe tomorrow evening, it seems like I might get home in time.

Greg  KO6TH


> From: APBIDDLE@xxxxxx.xxx
> To: Kelby.Davis@xxx.xxx.xxxx amsat-bb@xxxxx.xxx
> Date: Thu, 29 Jan 2009 07:35:27 -0600
> Subject: [amsat-bb] Re: AO-51 s-band
>
> Kelby,
>
> Hearing nothing on the mode-S downlink is actually pretty typical.  There
> are only a handful of stations who operate there.  I am not complaining,
> since I am one of those stations, but it would be nice to have some company.
> Excellent mode.  You should be getting a very strong carrier, even if nobody
> is on.  With a modest gain antenna you will get an exceptionally strong
> signal.
>
> This is not a packet configuration, though there is always a chance that
> somebody will decide to try a digital or other mode on an otherwise unused
> pass.  Additionally 9k6 and up does not really have "packet bursts" unlike
> 1200 baud.  It sounds more like while noise, and you sometimes get things
> which can sound like that on the downlink briefly.
>
> Alan
> WA4SCA
>
>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb

_________________________________________________________________
Windows Live?: E-mail. Chat. Share. Get more ways to connect.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_allup_explore_012009

------------------------------

Message: 5
Date: Fri, 30 Jan 2009 10:00:59 -0000
From: "Dave Aitch" <dave@xxxxx.xxx>
Subject: [amsat-bb] Delfi-C3 / DO-64 status update January 30th 2009
	10:00	UTC
To: "'Wouter Jan Ubbels'" <wjubbels@xxxxx.xxx>
Cc: 'AMSAT-BB' <amsat-bb@xxxxx.xxx>
Message-ID: <000b01c982c1$a74a8e70$f5dfab50$@xxx>
Content-Type: text/plain;	charset="us-ascii"

Nothing heard on either downlink frequency.

73, Dave.
IO80SM




------------------------------

Message: 6
Date: Fri, 30 Jan 2009 11:46:09 -0000
From: "Dave Aitch" <dave@xxxxx.xxx>
Subject: [amsat-bb] Delfi-C3 / DO-64 status update January 30th 2009
	1128/1141 UTC
To: "'Wouter Jan Ubbels'" <wjubbels@xxxxx.xxx>
Cc: 'AMSAT-BB' <amsat-bb@xxxxx.xxx>
Message-ID: <001301c982d0$58809500$0981bf00$@xxx>
Content-Type: text/plain;	charset="us-ascii"

Sounding as good as ever.

73, Dave.
IO80SM



------------------------------

Message: 7
Date: Fri, 30 Jan 2009 07:04:20 -0600
From: "Alan P. Biddle" <APBIDDLE@xxxxxx.xxx>
Subject: [amsat-bb] Re: Delfi-C3 / DO-64 status update January 30th
	20091128/1141 UTC
To: "'Dave Aitch'" <dave@xxxxx.xxx>
Cc: 'AMSAT-BB' <amsat-bb@xxxxx.xxx>
Message-ID: <129FD861714C40108FC1533DA0801F91@xxxxxx>
Content-Type: text/plain;	charset="us-ascii"

Indeed it does.  However, the cadence of the data burst is different, and
there were significant periods of no transmissions.  The new version of
RASCAL which will track a wider range is a great help here.

Alan
WA4SCA




------------------------------

Message: 8
Date: Fri, 30 Jan 2009 08:38:37 -0800 (PST)
From: Glen Zook <gzook@xxxxx.xxx>
Subject: [amsat-bb] Re: homebrew Loop yagi
To: NW VHF <PNWVHFS@xxxxxxxxxxxx.xxx>, AMSAT-BB <AMSAT-BB@xxxxx.xxx>,
	w7lrd@xxxxxxx.xxx
Message-ID: <335884.72083.qm@xxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii

There is an article on the North Texas Microwave Society website about
building a 1296 MHz loop yagi.

Go to

http://ntms.org/

Then look at the list of links on the left hand side of the page.  Click on
"Tech Library".  Then choose "The NTMS 1296 Loop Yagi Project - Al Ward -
W5LUA (pdf) 169k".

The link just below that one has some technical measurements.

Glen, K9STH

Website:  http://k9sth.com


--- On Thu, 1/29/09, w7lrd@xxxxxxx.xxx <w7lrd@xxxxxxx.xxx> wrote:

I am looking for some brain power from anyone who has built loop yagi's.  I am
getting my information from The ARRL Antenna book 20th edition.   The book
says follow exactly, however.  It calls for alluminum elements 0.0325 thick, I
have copper 0.025 thick.  It calls for 3/4" alluminum boom I have 3/4 copper
and some 1/2" stainless steel channel.  The feed to the driven element is UT-
14, I have a short piece with a SMA already attached, will connecting the SMA
to a SMA-N adapter be acceptable?  I have seen the pretty pictures of
Directive Systems antennas

http://www.directivesystems.com/loopyagi.htm

Same idea only different parts.  Are these things pretty "forgiving" or are
the components critical?  Also comparing the loop to a quagi the loop widths
are 1/4" wide and the quagi used #18 wire, why?  My intent is satellites
and/or terrestial.  Thanks for the bandwidth.





------------------------------

Message: 9
Date: Fri, 30 Jan 2009 17:00:20 +0000
From: Nigel Gunn G8IFF/W8IFF <nigel@xxxxx.xxx>
Subject: [amsat-bb] Re: homebrew Loop yagi
To: gzook@xxxxx.xxx
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>, NW VHF <PNWVHFS@xxxxxxxxxxxx.xxx>
Message-ID: <49833224.7030007@xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Don't forget the designs in the RSGB Radio Communications Handbook for 23 and
13 cms.


Glen Zook wrote:
> There is an article on the North Texas Microwave Society website about
building a 1296 MHz loop yagi.
>
> Go to
>
> http://ntms.org/
>


------------------------------

Message: 10
Date: Fri, 30 Jan 2009 13:58:20 -0500
From: "Robert Bruninga" <bruninga@xxxx.xxx>
Subject: [amsat-bb] Re: ISS and APRS with a TT3+ ?
To: "'racer5039'" <racer5039@x.xxx>, "'AMSAT BB'" <amsat-bb@xxxxx.xxx>
Message-ID: <550FE5846DE54149B46D2C6358F5E860@xxxxx.xxxx.xxx>
Content-Type: text/plain;	charset="us-ascii"

> Is there a way to set up my TT3+ to send APRS to the ISS ?

Generally, unattended one-way tracking devices are discouraged
from the packet satellites and the ISS to limit uncontrollable
QRM...  Live Operator operations, contacts, messages, and QSO's
are preferred.

There are of course, exceptions, for example, one year we
tracked a Ham driver of a vehicle delivering goods over Ice
rivers in Northern Canada above the arctic circle.  There was a
scientific expedition to Mongolia this year and we wanted to
send along a tiny tracker with WX station attached but could not
get it ready in time.  Then there was the student project of a
remote WX station on a ski-pole in Antarctica, and an Igloo WX
station by an experiment also in the arctic circle..

Then of course are the student experiments that might want to
demonstrate remote environmental data from a remote device (we
ran one for a week 2 years ago at the 5W level) to quantify the
link reliability (1 packet every 2 minutes).

In general, if you think your experiment is suitable, then we
recommend a routine long term packet period using 5W at about
one packet per 2 minutes.  This gives you about 3 good chances
at one packet per pass.  But also include in your packet, some
contact information.  Such as your email address.  Exceptions to
the email requirement could be:

1) if your callsign (on the device using a different SSID) is
also permanently maintaining a presence on APRS somewhere, they
you can be contacted that way, since any APRS message to that
callsign will be delivered to all of your other callsign
stations too.

2)if you maintain a forwarding email address @xxxxx.xxx (for
satellite operations or @xxxx.xxx for terrestrial operations).

PATH: you should use is VIA ARISS, since when PCSAT-1 is
operational (there will be a period in Feb maybe) it also
supports that path, so you get 12 passes a day, not just 6.

Hope that helps.

For more info on APRS via ISS please see:
www.aprs.org/iss-faq.html

And read the User Service Agreement for packet operations via
PCSAT-1.  This applies to PCSAT, but could also apply to packet
operations via the ISS digipeater also on the same channel
145.825.
www.aprs.org/pcsat/contract.txt

We continue to encourage more AX.25 digipeater satellites on
145.825 to serve as a continuing worldwide CQ, Contact and Data
channel for remote operations.

Bob, Wb4APR



------------------------------

_______________________________________________
Sent via amsat-bb@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
http://amsat.org/mailman/listinfo/amsat-bb


End of AMSAT-BB Digest, Vol 4, Issue 49
***************************************


Read previous mail | Read next mail


 07.07.2025 00:00:33lGo back Go up