[sarex] AO - 10 problem - the best solution in my opinion.

["Murray Peterson" <promise@xxxxxxxxxxx>]

Hi Daniel,
    The best information I recieved on this was from Steven Bienvenu, or at
least his information was the easiest for me to understand.

    What I did which solved this problem (in the absence of updated attitude
information) was to delete the lines from the file which specified the
attitude, but I left the other information there such as the beacon
frequency etc. which would not be out of date. I deleted all the lines under
the heading of [Attitude] including the actual heading line.

Here is Steve's explanation.

----- Original Message -----
From: Steven N. Bienvenu <bienvenu@softdisk.com>
To: Murray Peterson <promise@ihug.com.au>
Sent: Saturday, August 28, 1999 1:27 PM
Subject: Re: [sarex] WinOrbit keeps telling me that AO-10 is out of date?


> Hi Murray,
>
> I had the same problem.  The solution was to delete AO-10's attitude
> file, which was out of date and so generating that message.
>
> >From WinOrbit's help file for "Squint":
> -----------------------------------------
> Files - *.ATT
>
> A Windows "INI-style" file giving the current spacecraft attitudes for
> squint angle calculations.  Must be manually edited (using Notepad, for
> example).  The file name must match the spacecraft name EXACTLY (e.g.
> for "AO-10", use AO-10.ATT, for "AO10", use AO10.ATT).  The only
> exception is that a "/" in the spacecraft name (e.g. RS-12/13) will be
> replaced by an underscore (RS-12_13.ATT).  Any spacecraft for which a
> file is not found will be assumed to have its antennas pointing straight
> down (Microsat fashion - one rotation per orbit.)
>
> Since the attitude of controllable spacecraft changes periodically,
> there is a provision to set an expiration date.  If the attitude data is
> older than this date, you get a warning each time WinOrbit
>  runs, to remind you to get an update.  The expiration date must be in
> the numerical epoch format: YYDDD.FFF.
> This file is also used to provide frequency and other configuration
> information for the various transponders and beacons.  In the future,
> antenna configurations may be included, as well as solar cell locations
> and the nature of the satellite stabilization system.
>
> Sample files are included with winorbxx.zip: AO-10.ATT, DO-17.ATT, etc.
> Since AO-10 is no longer under ground control, the numbers in the latter
> file are estimates and may not be up to date.
> Optional file.
>
> Sample File Content
>
> [Attitude]                               ******    These are
> Alat = 0                                 ******    the lines
> Alon = 180                            ******    I
> Expiration = 96001.0             ******    deleted!
>
> [Beacon]
> BeaconFreq = 145.825
>
> [Transponder]
> ModeInfo = Mode B
> UplinkFreq = 435.155
> DownlinkFreq = 145.825
> TransponderInverting = true
>
>
> All fields are optional.  Headings (in "[]") must precede the
> corresponding fields if they exist, however.  The ModeInfo field may
> contain up to 64 characters, including punctuation.
>
> ---------------------------
>
> Hope this helps.
>
> 73,
>
> Steve  W5ZA   Shreveport, La., USA
>

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