OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
CX2SA  > SATDIG   08.10.11 21:16l 87 Lines 3229 Bytes #999 (0) @ WW
BID : AMSATBB6557
Read: GUEST
Subj: AMSAT-BB-digest V6 557
Path: IZ3LSV<IK2XDE<ON4HU<SR1BSZ<OK0NBR<PY1AYH<PY1AYH<CX2SA
Sent: 111008/1903Z @:CX2SA.LAV.URY.SA #:31240 [Minas] FBB7.00e $:AMSATBB6557
From: CX2SA@CX2SA.LAV.URY.SA
To  : SATDIG@WW

Today's Topics:

   1. Re: 5500 rotor problem (Floyd Rodgers)
   2. Re: 5500 rotor problem DUH (Jeff KB2M)
   3. oscar 17 (jerry keeton)


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

Message: 1
Date: Sat, 08 Oct 2011 11:40:26 -0500
From: Floyd Rodgers <kc5qbc@xxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: 5500 rotor problem
Message-ID: <4E907CFA.7060703@xxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

The 450 is a 360 degree system vs the 5500 is a 450 degree system, or at
least that is what the yaesu website says. I wish it were a direct
interchange, but the top casting is different. I have a 5500 that took
some wind damage and them some weeks later took a tree down hit. Got
fairly lucky, in that I only bent some elements on the antenna in the
second event. The rotor was previously damaged from the high wind event.
In that event I got 80+mph and a flying 10ft dish impact. Guess that's
what broke the azmith.


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

Message: 2
Date: Sat, 8 Oct 2011 12:49:22 -0400
From: "Jeff KB2M" <kb2m@xxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: 5500 rotor problem DUH
Message-ID: <00bd01cc85da$3ba251c0$b2e6f540$@xxx>
Content-Type: text/plain;	charset="us-ascii"

I was getting ready to take my rotor down and dissemble, but decided to give
it another test through the cable. I found that it started working. Upon
further examination I found that both the Azimuth and the Elevation cables
were somehow severely stretched and were both intermittent at that one spot
in the both cables. I ended up cutting a 3 foot section out of each rotor
cable and splicing back together. I have no idea how this just manifested
itself. I did have some major construction projects going on, new house
built, old house demolished, 25 by 50 by 20 foot septic system hole dug. All
this within 5 foot of my satellite array ! But after all of this it hooked
up plug and play to the new house. Very strange, that the cable problem just
showed up, almost a year later. But all is once again good in kb2m satellite
operations again. I should be back on the air this evening :-)
 Thanks to all the good debugging suggestions, I have filed them away, also
Drew thanks for the tip on the motor compatibility with the 5500 and 450. I
was going to sell the 450 rotor, but will now keep for a spare..

73 Jeff kb2m




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

Message: 3
Date: Sat, 8 Oct 2011 13:08:34 -0500
From: "jerry keeton" <jkboxk@xxxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] oscar 17
Message-ID: <5F44CFD6957B4C478F8DA32F59D1CA5E@xxxxxxx>
Content-Type: text/plain;	charset="iso-8859-1"

I heard the packets also , checked the sats path and found NO-44 was passing
. Don't remember the time , but a strong signal for NO-44 .

Jerry WB5LHD

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

_______________________________________________
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 6, Issue 557
****************************************


Read previous mail | Read next mail


 25.10.2024 10:29:07lGo back Go up