| |
CX2SA > SATDIG 30.04.10 20:18l 157 Lines 5172 Bytes #999 (0) @ WW
BID : AMSATBB5195
Read: GUEST
Subj: AMSAT-BB-digest V5 195
Path: IZ3LSV<IK2XDE<DB0RES<ON0AR<HS1LMV<CX2SA
Sent: 100430/1907Z @:CX2SA.LAV.URY.SA #:56747 [Minas] FBB7.00e $:AMSATBB5195
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Today's Topics:
1. Re: Space Debris: (Phil Karn)
2. Re: SatPC32 and SDX won't talk (Larry Gerhardstein)
3. Re: usb to serial adapter woes (Larry Gerhardstein)
4. Out of the Office (Martha)
----------------------------------------------------------------------
Message: 1
Date: Thu, 29 Apr 2010 16:21:16 -0700
From: Phil Karn <karn@xxxxxxxx.xxx>
Subject: [amsat-bb] Re: Space Debris:
To: w3hf@xxxx.xxx
Cc: amsat-bb@xxxxx.xxx
Message-ID: <4BDA146C.7070907@xxxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Stephen Melachrinos wrote:
> were a major hazard to everyone, themselves included. So they must
> have allocated more resources to the problem, as this is a massive
> undertaking. (Note that some reports say that the US has about 20,000
> objects that are tracked and cataloged. In theory, this means
> propagating the ephemeris of all of these for some number of days and
> comparing all possible combinations across the ti! me period of the
> analysis.)
Computers are cheap, so actually propagating the ephemerides of those
objects is the easy part.
The hard part is that the published elements are simply not accurate
enough to reliably predict collisions -- or give sufficient reassurances
that a collision won't occur.
TS Kelso has written some stuff about this on his website. See
http://www.celestrak.com/events/collision/
He's been doing his own conflict predicts for some time. He shows many
close approaches that never result in a collision. Yet he did not rate a
Iridium 33/Cosmos 2251 collision as especially probable before it
happened because the TLE numbers simply aren't accurate enough.
------------------------------
Message: 2
Date: Thu, 29 Apr 2010 22:28:41 -0600
From: Larry Gerhardstein <gerhardstein@xxxxxxx.xxx>
Subject: [amsat-bb] Re: SatPC32 and SDX won't talk
To: amsat-bb@xxxxx.xxx
Cc: Erich Eichmann <erich.eichmann@xxxxxxxx.xx>
Message-ID: <4BDA5C79.3030900@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I applied the suggested fix to get the Speech SDX. That worked, but on
the computer in question, I do not have sound coming from my speakers.
I'm working with the vendor on that.
But there are more troubles with my set setup and I will detail those in
separate postings.
Larry W7IN
------
Hello Larry,
>> I suppose you run V. 12.8 or 12.8a.
>>
>>> From the list in menu "Rotor Setup" choose the item "Yaesu GS-232".
>>> Save the
>>>
>> change with the upper "Save" button and restart SatPC32.
>>
>>
------------------------------
Message: 3
Date: Thu, 29 Apr 2010 22:40:09 -0600
From: Larry Gerhardstein <gerhardstein@xxxxxxx.xxx>
Subject: [amsat-bb] Re: usb to serial adapter woes
To: gerhardstein@xxxxxxx.xxxx kq6ea@xxxxxxx.xxx
Cc: amsat-bb@xxxxx.xxx
Message-ID: <4BDA5F29.9090401@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Problem reported in this thread solved. Bought and installed two
optical isolators. One in ICOM serial line and one in GS232/G5500
serial line. Rotor position now reading correctly, but there was one
more issue. Cables that I believed to be straight through were not;
they were null modem. Should have used an ohm meter right away. Tests
of pins 2 and 3 at both ends proved what the cables really were.
A warning: two null modem cables back-to-back to not make a straight
through cable.
But there still are more problems with my sat system, which I will
discuss in further posts.
Larry W7IN
On 4/15/2010 6:41 PM, Larry Gerhardstein wrote:
> Jim, et. al., Thanks for the advice. However, after installing the
> USA-49WG and driver install for Windows 7 with help from Tripp Lite
> technical support, my system still does the same thing. I plug the
> serial cables to both rotor and transceiver digital interfaces and then
> to the 49WG and the same thing happens. Azimuth meter drops to zero and
> there is no control. Further it is now working worse than before, as I
> have neither control of rotor or transceiver. If measure the voltage
> between metal shields of the two cables, there is about 2 volts there.
> It sure looks like a ground loop, but where and how. I have no idea at
> this point. In 56 years a ham operator, I've never run into anything
> like this. Maybe RS232 isolators would fix this??? Seems like overkill.
>
> Larry W7IN
>
------------------------------
Message: 4
Date: Fri, 30 Apr 2010 14:52:01 -0400
From: Martha <martha@xxxxx.xxx>
Subject: [amsat-bb] Out of the Office
To: AMSAT BB <amsat-bb@xxxxx.xxx>, Board of Directors <bod@xxxxx.xxx>
Message-ID:
<z2p956751cf1004301152qfd750b90ndc54ca6532dd2e56@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1
I will be out of the office today starting at 3:00 PM.
--
73- Martha
------------------------------
_______________________________________________
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 5, Issue 195
****************************************
Read previous mail | Read next mail
| |
