\documentclass[11pt]{article}
%\documentstyle[11pt]{article}

\usepackage{lscape}

\topmargin -0.75truein
\oddsidemargin -0.4truein
\textheight 9.25truein
\textwidth 6.7truein
\hbadness=10001
\hfuzz=200pt


\begin{document}
%\input dspace12.tex
%\input pstricks.tex
%\input psfig
\newcommand{\be}{\begin{enumerate}}
\newcommand{\ee}{\end{enumerate}}
\newcommand{\bc}{\begin{center}}
\newcommand{\ec}{\end{center}}
\newcommand{\bi}{\begin{itemize}}
\newcommand{\ei}{\end{itemize}}
\newcommand{\bd}{\begin{description}}
\newcommand{\ed}{\end{description}}
\newcommand{\bt}{\begin{tabbing}}
\newcommand{\et}{\end{tabbing}}
\newcommand{\eg}{{\it e.g.~}}
\newcommand{\ie}{{\it i.e.~}}
\newcommand{\ul}{\underline}
\newcommand{\axaf}{{\em AXAF}}
\def\la{\hbox{\rlap{$<$}\lower0.5ex\hbox{$\sim$}\ }}

\large
%\vspace*{-0.5in}
\centerline {\bf 4.28\_V2.2 Flight Software Standard Patch F Optional
Patch G}
		 
\vspace{0.25in}

\normalsize
\noindent{\it Last Revised: \today} \\
\noindent{\bf Filename: sw\_stdfoptg} \\

\noindent {\bf BRIEF FUNCTIONAL DESCRIPTION:} \\
\normalsize

This procedure loads the standard F patches and five optional G patches.
The changes from sw\_stdeoptf consist of one standard patch.
The text describing the changes in the patches in this procedure
are included below the italic note: \\

{\it  The set of standard release F patches is loaded into a
common address space so that each optional patch can 
be loaded independently of the others, provided the load order defined
in the patch combination certification is maintained.

Patches eventhist, ctireport1, and ctireport2 require that smtimedlookup is also loaded;

 The ACIS Flight SW team recommends that the optional patches be loaded
together with the standard patches; therefore this procedure first
removes any patches which may have been installed and then proceeds to
load the standard patches followed by the optional patches.

This procedure loads
``standard Rev. F'' and optional patches from
``optional Rev. G''.  Refer to the release notes for standard patches,
optional patches, and patch combination certification (see references 
below). \\}
 
Revision C of the buscrash2 patch has been included in this standard load,
to address the Trickle Bias Anomaly. \\


{\bf This procedure will change the flight software version from 50 to
version 53. Ground software should be changed to reflect the version
change once this procedure is executed.}
 
The FOT should implement the loading of the patches (steps 3.1 through 
step 8.1) as six realtime command loads in order to maximize the uplink
efficiency.  The command system should be configured with a blocking
factor of 90 and a minimum time delay of 3~s.\\

The following procedure loads the Standard F and smtimedlookup / cc3x3 / 
eventhist / compress~all / txings optional set of patches into the ACIS
instrument, and dumps the load to the ground for verification. It then
executes a warm boot and loads and starts DEA housekeeping. \\

This procedure implements the following basic operations:
\be
\item 
Confirm the current state of ACIS by verifying BEP HW and SW LEDs
\item
Reset the contents of the patch list to remove any existing patches,
dump the contents of the patch list to verify that the list is empty
\item
Load the ``standard Rev. F'' patch load
\item 
Load the smtimedlookup patch (part of ``optional Rev. G'')
\item
Load the cc3x3 patch (part of ``optional Rev. G'')
\item
Load the eventhist patch (part of ``optional Rev. G'')
\item 
Load the compressall patch (part of the ``optional Rev. G'')
\item 
Load the txings patch (part of the ``optional Rev. G'')
\item
Load the patch load version number (53)
\item
Dump the contents of the patch list to verify the load
\item
Warm boot the BEP to activate the new load and verify proper BEP boot
\item 
Start the DEA housekeeping and verify proper reporting
\ee


Refer to the Standard Patch Release Notes, for MIT 36-58010  Rev. G
and MIT 36-58032.32 Rev C, for a detailed description of the effects of this patch load.  \\

The telemetry verifiers for the procedure will be:
\be
\item
ACIS Ops will confirm the current status of the BEP
\item
A command echo for the reset patch list command
\item
A command echo for the 1st dumpPatchlist command
\item
A single bepReadReply packet for the 1st empty dump
\item
A series of command echoes for the addPatch commands. The SOT will
verify that each Result field of each commandEcho packet has a value
of 1. 
\item
A command echo for the dumpPatchlist command
\item
A series of bepReadReply packets for the dump command
\item
A comparison of the dumped patchlist to expected values.
\item
A bepStartupMessage packet with a modified ``version == 53'' field.
\item
A verification of the focal plane temperatures once the housekeeping has started.
\ee

ACIS flight software personnel will review the contents of the various
dumps after the procedure has been run. \\

\vspace{0.15in}
\normalsize
\noindent {\bf ASSUMED INSTRUMENT STATE:} \\
\normalsize
This assumes that DPA-A and/or DPA-B is on and the flight SW is running on either BEP-A or BEP-B. \\


%\vspace{0.25in}
\normalsize
\noindent {\bf SPECIAL INITIAL CONDITIONS:} \\
\normalsize
The OCC command system must be configured with ``Minimum Time Delay of
3~s'' and a ``Blocking Factor'' of 90.\\
Spacecraft telemetry should be in Format 2 when the patches are loaded
in order to ensure that all command verifiers can be included in the
telemetry stream.\\

%\newpage 

%\vspace{0.25in}
\normalsize
\noindent {\bf OPERATIONAL CONSTRAINTS/CAUTIONS:} \\
\normalsize
In order to avoid truncating a dump, each dumpPatchlist command
must be followed by at least a 30 second delay.

After successfully uplinking patches and rebooting the BEP, two other
items are needed:
\begin{itemize}
\item Reset the focal plane temperature to the desired value
\item Reload the parameters for the threshold crossings patch.
\end{itemize}

\vspace{0.15in}
\normalsize
\noindent {\bf CONTINGENCY PLANS:} \\
In case of a problem that may arise during the procedure, the
following contingencies may be followed:
\be
\item
If there is a failure to confirm a telemetry verifier, ACIS flight
software personnel will visually determine, via bi-levels, if the 
ACIS FIFO needs to
be cleared.  If it does, the FIFO will be cleared via Step 13.  
If the FIFO did not need to be cleared, ACIS Ops
has the discretion to restart the procedure at 2.1, or to continue on
from this point. \\

Should the FIFO clear procedure be executed and is successful, the
ACIS operator will observe the following responses. First, in PMON,
the operator will see the correct command echo from the stuck command. Next,
also in PMON, the ``Serial Command" column will show ``UNUSED'', and the
``Result Code" column will show ``NO\_HANDLER''.  Lastly, the bilevels
will return to their nominal values. 1STAT7ST  will read 0 indicating
FIFO Empty, and 1STAT6ST will read 1, indicating FIFO Not Full. \\

If the FIFO does not need to be cleared and the problem cannot be
determined, a full ACIS system dump will be executed, using
SOP\_ACIS\_FSW\_DUMP to obtain the ACIS diagnostic information. The
patchlist will be cleared, if necessary, and the present version of
software will continue to run. Should ACIS reboot, however, it will 
revert to Version 11 of the ACIS software.

\item
If there is a failure to confirm the patch list dump (step 10), first
repeat step 10, dumping the 
patch list, to confirm that there wasn't a downlink corruption. If the
list is confirmed, continue to the next step(11), otherwise, restart
from step 2.1 and reload the patches. If SOT cannot confirm telemetry 
verifiers for reasons other than telemetry corruption, run 
SOP\_ACIS\_FSW\_DUMP to obtain the ACIS diagnostic information and then
reload version 50 patches (SOT Procedure 4.27, v. 2.1,
sw\_stdeoptf, FOT SOP\_ACIS\_SW\_STDEOPTF).
\item 
If the warm boot of the BEP fails (step 11), retry the reboot (step
11). If this continues to fail, dump additional information for
diagnostic purposes (SOT Procedure 1.10, v 2.2 sw\_dump, FOT
SOP\_ACIS\_FSW\_DUMP and reload version 50 patches (SOT Procedure 4.27, v. 2.1,
sw\_stdeoptf, FOT SOP\_ACIS\_SW\_STDEOPTF).
\item
If there is a comm loss during the procedure, request a new comm. The
time at which the new comm is needed depends on the point of loss of
signal. The only vulnerability would occur if comm was dropped 
before the complete patch set was loaded (completion of step 8). If
the BEP then rebooted spontaneously, it would return to version 11
flight software.
\ee

\vspace{0.15in}
\normalsize
\noindent {\bf REFERENCES:} \\
\normalsize
\vspace{-0.15in}
\be
\item MIT 36-58010 Rev G (ECO 36-1048) Flight Software Patch Release F,
Optional Release G. 
\item MIT 36-58021.04 Rev H (ECO 36-1049) Flight Software Patch Release
F-G-H Certification. 

\ee

\normalsize
\noindent {\bf CHANGE HISTORY:} \\
\normalsize

{\bf V0.1}
\begin{itemize}
\item Initial version, revised from 4.27\_V2.1 Flight
Software Standard Patch E Optional Patch F.
\end{itemize}

{\bf V1.0}
\begin{itemize}
\item Minor text edits; ready to send to MIT team.
\end{itemize}

{\bf V1.1}
\begin{itemize}
\item Minor text edits.
\end{itemize}

{\bf V2.0}
\begin{itemize}
\item For release to the FOT.
\end{itemize}

{\bf V2.1}
\begin{itemize}
\item Corrected location of comparison image
\end{itemize}

{\bf V2.2}
\begin{itemize}
\item Added cautions about FP temperature setting and txings parameters.
\end{itemize}

\newpage
\vskip 3.0in

This page intentionally left blank
\vskip 3.0in

\newpage

\newcommand{\tablecaptiontext}{ACIS eventhist, cc3x3,
smtimedlookup, compressall, and txings Flight Software Patch Revision F and FIXFIFO command}


\input{sw_stdfoptg.tab}

\end{document}




