| |
CX2SA > SATDIG 27.12.10 21:03l 376 Lines 12235 Bytes #999 (0) @ WW
BID : AMSATBB5513
Read: GUEST
Subj: AMSAT-BB-digest V5 513
Path: IZ3LSV<IK2XDE<IR2UBX<IW8PGT<CX2SA
Sent: 101227/2002Z @:CX2SA.LAV.URY.SA #:41804 [Minas] FBB7.00e $:AMSATBB5513
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Today's Topics:
1. First Satellite QSO AO-27 (John M. Belstner)
2. AO-51 update 26 Dec 2010 2115utc (Mark L. Hammond)
3. DM31 QSLs to the post office...
(Patrick STODDARD (WD9EWK/VA7EWK))
4. FS: FT736R and accessories (Rm2642@xxx.xxxx
5. Sacramento and L.A (Michael Chen)
6. Re: O/OREOS TLE errors ? (Ryan Caron)
7. Re: true tle (Philippe Van houte)
8. High resolution serial antenna tracking protocol?
(Richard Ferryman)
9. Re: High resolution serial antenna tracking protocol?
(Paul Williamson)
----------------------------------------------------------------------
Message: 1
Date: Sun, 26 Dec 2010 13:17:44 -0800 (PST)
From: "John M. Belstner" <jbelstner@xxxxx.xxx>
Subject: [amsat-bb] First Satellite QSO AO-27
To: amsat-bb@xxxxx.xxx
Message-ID: <552188.15493.qm@xxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Congratulations to Steve KC4SW on his first Satellite QSO on AO-27 today.
Too bad I must also apologize for all the poor operating behavior on the FM
Birds. Its not normally this bad.
John Belstner W9EN
Valley Center, CA DM13le
------------------------------
Message: 2
Date: Sun, 26 Dec 2010 16:36:08 -0500
From: "Mark L. Hammond" <marklhammond@xxxxx.xxx>
Subject: [amsat-bb] AO-51 update 26 Dec 2010 2115utc
To: amsat-bb@xxxxx.xxx
Message-ID: <nxcB1f00456cfur05xcBr2@xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
Hi All,
This afternoon the power management function of AO-51 was turned ON, in
anticipation of eclipses in just a few days. You might see the transmitter
power levels go UP and DOWN a bit as the battery voltage changes. We'll
make some adjustments and tweaks to keep it from going UP and DOWN too
often--but it's the way it's gonna work. In a few weeks we expect
transmitter(s) to be OFF while in eclipse and ON when in the sun.
Expect adjustments and various power management schemes from now until the
end of February when we'll again see full sunlight for a brief period (few
short months as I recall). We'll do our best to keep you informed via the
BBS and the AO-51 webpage.
On behalf of the Command Team,
Mark L. Hammond [N8MH]
------------------------------
Message: 3
Date: Sun, 26 Dec 2010 21:52:14 -0800 (PST)
From: "Patrick STODDARD \(WD9EWK/VA7EWK\)" <amsat-bb@xxxxxx.xxx>
Subject: [amsat-bb] DM31 QSLs to the post office...
To: amsat-bb@xxxxx.xxx
Message-ID: <327928.15829.qm@xxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Hi!
After returning home earlier this afternoon, I printed and wrote
out the QSL cards from my DM31 trip to southern Arizona just over
a week ago (18 December). All of those cards will go to the post
office tomorrow morning. These cards will have a different Arizona
license plate on them; I'm not much of an artist, but I can at
least mix things up with the large variety of license plates issued
by the state of Arizona. :-)
I hope everyone had a good Christmas. Happy 2011 to all, and 73!
Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/
------------------------------
Message: 4
Date: Mon, 27 Dec 2010 08:53:49 -0500 (EST)
From: Rm2642@xxx.xxx
Subject: [amsat-bb] FS: FT736R and accessories
To: amsat-bb@xxxxx.xxx
Message-ID: <5ec31.6e318d3a.3a49f46d@xxx.xxx>
Content-Type: text/plain; charset="US-ASCII"
Offering my FT736R with accessories first to the satellite community
before placing them on eBay.
Detailed photos of everything at n6paa.org.
Please reply off list.
Thanks
ron
n6paa
------------------------------
Message: 5
Date: Mon, 27 Dec 2010 07:08:28 -0800
From: Michael Chen <michael.bd5rv@xxxxx.xxx>
Subject: [amsat-bb] Sacramento and L.A
To: amsat-bb <amsat-bb@xxxxx.xxx>
Message-ID:
<AANLkTikMUHetqgoseyDQg8LUNG0iuipx3dHnhn3YBeQu@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1
Hey, guys,
I will be in Sacramento today to 29th and then L.A till Jan. 5. It
will be great to meet some amsat guys in these areas. Leave me a
message or call (317)716-6818.
Michael Chen, BD5RV/4
AMSAT-China: http://www.camsat.cn
-----------------------------------
Twitter: ?http://twitter.com/bd5rv
Email: ? michael.bd5rv@xxxxx.xxx
MSN: ? ?bd5rv@xxxxx.xxx
Skype: ?michael-bd5rv
------------------------------
Message: 6
Date: Sun, 26 Dec 2010 11:29:28 -0800
From: Ryan Caron <rcaron@xxxxx.xxx>
Subject: [amsat-bb] Re: O/OREOS TLE errors ?
To: pa3guo@xxxxx.xxx
Cc: amsat-bb@xxxxx.xxxx PA3GUO <pa3guo@xxxxxxx.xx>
Message-ID: <4D179798.5030409@xxxxx.xxx>
Content-Type: text/plain; charset="utf-8"
Hank (and the -bb)
Attached is the spreadsheet previously mentioned spreadsheet to fix TLEs
checksums. I've rewritten it since what I was using was still a tedious
operation and I didn't want to distribute that to the community. This
should be much better, though you still need to remove any leading
spaces in the lines.
It appears that O/OREOS' TLEs on their website are OK now, possibly
because SpaceTrack is publishing now. My apologies for not getting this
out sooner; we'll have to wait for the next launch to try this out.
During the fog-of-war in the days after launch, I find there are often
multiple TLEs for the same satellite. In this case I like to change the
IDs so I can have them all loaded in GPredict simultaneously. This
spreadsheet will verify that the IDs are the same for both lines, and of
course regenerate the checksums.
This spreadsheet was created with OpenOffice 3.2.1, and I've exported it
to Excel and checked it with MS Office XP and appears to work fine.
Please let me know if there are any problems.
Happy holidays and 73,
Ryan KB1LKI
On 11/30/10 11:33 AM, PA3GUO wrote:
> Hi Ryan
>
> Thanks a lot for your detailed reply.
>
> Would you be so kind to share that spreadsheet (XLS?) with me ?
> In the coming days I really need (well, would higly appreciate) to
> have working TLEs - especially also for Nanosail.
>
> Best of course would be if the O/OREOS/Nanasail team could fix this prior
> to posting them on the web :-)
>
> Thanks
> Henk
>
>
> ---- Ryan Caron<rcaron@xxxxx.xxx> schreef:
>> The O/OREOS TLEs consistently do not have valid checksums (last digit of
>> each line). I submitted a comment about this on their website but I have
>> not heard back. The correct checksums are 2& 3, and not the 6& 5 that
>> is listed.
>>
>> If, by the time you read this, the posted TLEs are not 6& 5, then the
>> TLEs have been updated and you'll have to generate new checksums. The
>> formula is a sum of all numerical characters on the line, including the
>> line number, treating minus signs as a one and everything else (letters,
>> +, spaces) as a 0. Then take modulus 10 of the sum (i.e. last digit of
>> the sum). Look it up on wikipedia for more details.
>>
>> I've made a spreadsheet to fix this, but it is still a manual operation
>> for me (got to write a script at some point). Some programs disregard
>> the the checksum, which is why HRD& the website still work and your
>> tracking tool doesn't. Predict/GPredict, my tools of choice, require
>> valid checksums, making proper TLEs a pet peeve of mine. I don't know
>> what NOVA's up to.
>>
>> In terms of "swarm spread" (i.e. how small delta-V between spacecraft
>> that shared the same ride, which in this case is just done by compressed
>> springs, translates into spatial differences), 35 minutes of separation
>> is pretty high for just 10 days after launch. With all the latest TLEs
>> from the three websites, I show O/OREOS being 3.5 minutes ahead of RAX,
>> and RAX being a 1.33 minutes ahead of FAST1/2.
>>
>> Ryan, KB1LKI
>>
>> On 11/30/10 4:54 AM, amsat-bb-request@xxxxx.xxx wrote:
>>> ------------------------------
>>>
>>> Message: 4
>>> Date: Mon, 29 Nov 2010 22:55:16 +0100
>>> From: PA3GUO<pa3guo@xxxxxxx.xx>
>>> Subject: [amsat-bb] O/OREOS TLE errors ?
>>> To:amsat-bb@xxxxx.xxx
>>> Message-ID:<19767175.1291067716437.JavaMail.root@xxxxxxxx.xxxxxx.xx>
>>> Content-Type: text/plain; charset=utf-8
>>>
>>> Dear all,
>>>
>>> I keep on having troubles with the O/OREOS kepler sets.
>>> RAX and the others are fine.
>>>
>>> With todays version (as from the O/OREOS dashboard on the web)
>>> - NOVA gives O/OREOS just a bit behind RAX
>>> - HamRadioDeluxe give O/OREOS 35 minutes behind RAX
>>> - The O/OREOS web (dashboard graphic) shows O/OREOS 35 minutes behind RAX
>>> - My private antenna tracking tool does not recognize the keplerset of
O/OREOS
>>>
>>> Anyone else has experienced this (and maybe even a solution) ?
>>> Henk
>>> --
>>> Henk, PA3GUO
>>>
>
> --
> Henk, PA3GUO
>
------------------------------
Message: 7
Date: Sun, 26 Dec 2010 10:19:11 +0100
From: "Philippe Van houte" <Philippe.Vanhoute@xxxxxx.xx>
Subject: [amsat-bb] Re: true tle
To: "N. Mahdinejad" <n.mahdinejad@xxxxx.xxx>, "Amsat-BB"
<amsat-bb@xxxxx.xxx>
Message-ID: <9E67E0EB4F44482380DAC23010BD5AD6@xxxxxxxx>
Content-Type: text/plain; charset="Windows-1252"
Hi
Check the date of the elements.
Very easy
By example :
10307.21104525 is the day 307 of year 2010.
Philippe
on5pv
----- Original Message -----
From: "N. Mahdinejad" <n.mahdinejad@xxxxx.xxx>
To: "Amsat-BB" <amsat-bb@xxxxx.xxx>
Sent: Sunday, December 26, 2010 9:47 AM
Subject: [amsat-bb] true tle
Dears.
Merry Christmas. I wish all of you have happy holidays.
I have question about true tle of amsat satellites.
There is one set of TLE in celestrak and one in each satellite webpage
in amsat . those are different from in clestrak.
Which of these TLE are true that I can use in unitrak for tracking?
My tracking predictions in following two pages are different. I don?t know
why?
http://www.amsat.org/amsat-new/tools/predict/index.php
http://www.amsat.org/amsatnew/satellites/satInfo.php?satID=116&retURL=/satelli
tes/status.php
Any help would be gratefully appreciated.
Best Regards.
_______________________________________________
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
------------------------------------------------------------------------------
--
Ce message entrant est certifi? sans virus connu.
Analyse effectu?e par AVG - www.avg.fr
Version: 9.0.872 / Base de donn?es virale: 271.1.1/3337 - Date: 12/25/10
00:59:00
------------------------------
Message: 8
Date: Mon, 27 Dec 2010 11:01:54 -0000
From: "Richard Ferryman" <g4bbh@xxxxxxxxxx.xxx>
Subject: [amsat-bb] High resolution serial antenna tracking protocol?
To: <amsat-bb@xxxxx.xxx>
Message-ID: <4C52F09091C24F1391A24F74152B9F23@xxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
I have been working on an antenna tracking system using a very heavy duty
CCTV pan and tilt head which uses large stepper motors. I have built a new
control system that accepts Yaesu serial data commands from SatPC32 and
drives the stepper motors to the correct position. The Yaesu protocol only
works in whole degrees. Does anyone know of a serial protocol that allows
fractional degree or minute data? I know our application doesn't need it
but I would like to test the hardware to it's limit!
Dick G4BBH
------------------------------
Message: 9
Date: Mon, 27 Dec 2010 10:44:56 -0800
From: Paul Williamson <kb5mu@xxxxx.xxx>
Subject: [amsat-bb] Re: High resolution serial antenna tracking
protocol?
To: "Richard Ferryman" <g4bbh@xxxxxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Message-ID: <a06240802c93e8e9eab78@xxxx.xxx.x.xx>
Content-Type: text/plain; charset="us-ascii"
At 11:01 AM +0000 12/27/10, Richard Ferryman wrote:
> Does anyone know of a serial protocol that allows fractional degree or
minute data?
EasyComm specifies azimuth and elevation to 0.1 degree.
There's a copy of that protocol spec here:
http://www.mustbeart.com/software/easycomm.txt
73 -Paul
kb5mu@xxxxx.xxx
------------------------------
_______________________________________________
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 513
****************************************
Read previous mail | Read next mail
| |
