Section Title

1
Section Title
New HorizonsShedding Light On Frontier Worlds
Ralph Instrument Critical Design ReviewAug 5
6, 2003

• Presenter Name
• Presenter Program Role
• 303 939-XXXX
• e-address_at_ball.com

2
(No Transcript)
3
Presentation Outline

• Low-Speed Telemetry
• High-Speed Telemetry
• Estimated Memory Usage
• Timing Simulations
• Reviews
• Test Plan
• Independent Verification and Validation
• Development Status
• Longevity
• Outstanding Issues
• Summary

• Requirements
• Design
• Development Environment
• Operating Modes
• Timing (Tasks)
• Turn On Operation
• MVIC Operation
• LEISA Operation
• Target Motion Rate
• Command Handling
• RALPH Commands
• Uploads

4
Requirements

• Software Requirements Specification
  05310-05-SRS-01, Revision 0, dated June 2003
• Objectives
• Describe the context within which RALPH firmware
  (RALPHFW) must operate
• List the requirements for RALPHFW
• Derived from
• RALPH Instrument Specification, RIS TBD
• Spacecraft to RALPH ICD, 7399-9201
• RALPH DE ICD, Ball Document 574835
• RALPH Software Development Plan,05310-05-SDP-01
  (SDP)
• RALPH Command and Data Handling Control Board
  Specification, TBD
• RALPH command and telemetry spreadsheets

5
Design

• Software Design Specification 05310-05-SDS-01,
  Draft Revision, in progress
• Objectives
• Describe software architecture of RALPHFW
• Describe the hierarchy of RALPHFW modules
• Describe the data required for each module
• Describe the external visible functions for each
  module
• Derived from
• 05310-05-SRS-01

6
Development Environment

• KEIL uVision 2 V2.31 Embedded C IDE
• CVS Configuration Management

7
Operating Modes 1/2
State Diagram for RALPHFW
8
Operating Modes 2/2
9
Acquire State Timing (Tasks - 1 PPS period)
10
Checkout State Timing (Tasks - 1 PPS period)
11
Turn On Operation

• S/C receives SC_RALPH_POWER ON command to power
  RALPH A or RALPH B side on
• Approximately one minute from time between when
  RALPH is turned on and when it can accept
  commands
• S/C receives SC_RALPH_RELAY_BUS ON and executes
  it
• RALPH receives RALPH_SIDESEL_RELAY command to
  fire side select relays
• S/C receives SC_RALPH_RELAY_BUS OFF and executes
  it
• 4 commands are needed to start RALPH

12
MVIC Operation

• RALPH receives RALPH_SET_RELAY MVIC_TDI_COLOR
  telecommand
• RALPH fires group relay 1 off and group relays 2
  and 3 on sequentially with approximately 100 ms
  between firings.
• S/C receives SC_RALPH_RELAY_BUS ON and executes
  it
• S/C receives SC_RALPH_RELAY_BUS OFF and executes
  it
• RALPH receives RALPH_MVIC_TDI_COLOR telecommand
• RALPH uses target motion rate value and
  observation table to calculate TDI rate parameter
• RALPH CDH commands DE side by passing
  RALPH_MVIC_TDI_COLOR opcode and TDI rate
  information
• Observation takes place over some period of time
• S/C receives SC_RALPH_RELAY_BUS ON and executes
  it
• RALPH receives RALPH_IDLE telecommand to end this
  observation
• RALPH fires group relays individually to turn off
  with approximately 100 ms between firings.
• S/C receives SC_RALPH_RELAY_BUS OFF and executes
  it
• Ready for next observation

13
LEISA Operation

• RALPH receives RALPH_LEISA_SUB telecommand to
  start an observation
• RALPH uses current target motion rate value to
  correct Frame rate parameter
• RALPH CDH commands DE side by passing mode and
  parameter information
• RALPH CDH instructs DE to start observation
• Observation takes place over some period of time
• RALPH receives RALPH_IDLE_NO_RELAY telecommand
  to end observation.
• Ready for next observation

14
Target Motion Rate Equation 1/3

• RATEDE the final calculated value that goes to
  DE electronics
• ScaleDE a scaling factor to put the 20us based
  counter into equivalent 10us based counts (TDI
  Rate) or 1ms based counts (Frame Rate).
• ScalePIX the Pixel Scale which is a unique
  constant for each detector (MVIC, LEISA).
• DECNT The correction factor for the counter
  value passed from DE.
• TMRSC the Target Motion Rate received from the
  S/C.
• TMRCOR a TMR offset in radians/sec that is
  uploaded from the ground to compensate for the
  TMR value in the middle of the observation

15
Target Motion Rate Timing 2/3
16
Target Motion Rate Flowchart 3/3
17
Command Handling

• Commands enter the instrument through dual,
  redundant RS-422 ports, A and B sides
• RALPH shall determine which side to use depending
  on which dual, redundant, 1 PPS input is active
• Valid NH commands have an ITF wrapper for
  synchronize and command type identification,
  whether time message or telecommand
• Time messages for RALPH contain the timestamp, a
  memory dump handshake bit, TMRSC, and the TMRCOR
• Telecommands are one of the following
• RALPH-specific commands
• Memory dump request
• Memory load

18
RALPH Commands

• RALPH telecommands have two distinct formats
• an 8-bit opcode and a 16-bit parameter
• an 8-bit opcode and three 32-bit floating point
  values
• All telecommands are detailed in command
  spreadsheets included in 05310-05-SRS-01 as
  appendices.
• Commands

• 16-bit Parameter Type
• MVIC Calibration, LEISA Calibration, Idle,
  Abort, No Operation, Side Select Relay, No Relay,
  Set Relay, Set State

32-bit Parameter Type MVIC Normal Science LEISA
Normal Science
19
Uploads

• Code and table uploads will be performed using
  the memory load command.
• Uploads can occur in the CHECKOUT or INITIAL
  state to either RAM or EEPROM.
• Upload command rate is 128 bytes per second
  maximum
• Each upload command is validated individually
  with a checksum
• Each upload commands goes to scratch area of RAM
• To be written to its destination, the complete
  image in scratch RAM must be validated

20
Low-Speed Telemetry

• Telemetry details documented in telemetry
  spreadsheets in 05310-05-SRS-01
• Two main categories
• Non-packetized
• Instrument state always output at 1 Hz
  immediately follows ITF header. Instrument state
  contains information for S/C autonomy. It also
  contains information that allows S/C to assess
  the general status (mode, key voltages,
  temperatures) of RALPH without delving into
  packetized data
• Packetized (implies contained within CCSDS
  packet)
• Housekeeping
• Messages
• Memory Dump

21
High-Speed Telemetry

• A. LEISA Format (256 x 256 pixels x 1.5
  bytes/pixel 98304 bytes)
• 1)LEISA Raw Mode
• 2)LEISA Subtracted Mode
• 3)LEISA Calibration Mode
• B. MVIC Panchromatic TDI (Time-Delay
  Integration) Format (5024 pixels x 1.5
  bytes/pixel 7536 bytes)
• 1)Panchromatic TDI Mode
• 2)Panchromatic TDI Calibration Mode
• C. MVIC Panchromatic TDI Binning Format
  (1672 pixels/line x 1.5 bytes/pixel x 2 lines
  5016 bytes)
• 1)Panchromatic TDI Binning Mode (one
  mode only)
• D. MVIC Color TDI Format (5024 pixels x 1.5
  bytes/color x 4 colors/pixel 30144 bytes)
• 1)Color TDI Mode
• 2)Color TDI Calibration Mode
• E. MVIC Frame Format (5024 pixels x 1.5
  bytes/pixel 7536 bytes)
• 1)Frame mode
• 2)Calibration Mode

22
Estimated Memory Usage

• Memory usage for science acquisition and
  telemetry generation (so excludes safety checks
  and command processing)
• PROM
• Code TBD KB out of 32 KB (TBD)
• EEPROM
• Code TBD
• External Code RAM
• Code TBD
• Internal Data RAM
• TBD bytes out of 256 bytes (TBD)
• External Data RAM
• tbd bytes for science and telemetry variables
• Total TBD bytes out of TBD bytes (TBD)

23
Timing Simulations

• Time usage for worst case conditions in one
  one-second period
• 80C51 clock is running at 4.9152 Mhz (TBR)
• ACQUIRE State
• Performing RateDE calculation, with range error
  (produces maximum message).
• Outputting instrument state, housekeeping, and
  message packets
• Results
• Telemetry generation (gathering and formatting
  data for output)
• TBD ms
• Data movement to UART register
• TBD ms
• RateDE calculation
• TBD ms
• Total
• TBD ms out of one second (TBD)

24
Reviews

• Requirements Review
• Review of the Software Requirements Specification
• Software requirements review held on 30 June
  2003. IDRR 05310-05-TBD
• Peer Reviews
• Peer Design Review
• Occurs prior to the Software Design review and is
  conducted by members of the software design team.
• Code Walkthrough
• Occurs after coding of a CSU and is conducted by
  members of the software team and SQA
• ATP Review
• Occurs after integration testing and is conducted
  by members of the software team.

25
Test Plan

• A review of test procedures shall be performed
  prior to testing
• Module Level
• Testing is performed on a simulator running in a
  PC
• Tests are of individual standalone modules using
  drivers and stubs
• Module test procedure (05310-05-SMTP-01)
• Integrated Level
• Testing of integrated software
• White box testing would occur here for
  verifying software behavior that requires probing
  the board
• Entire acceptance test procedure
  (05310-05-SATP-01)

26
Independent Verification and Validation

• RALPH software is categorized as Limited
• Limited entails that the Software Requirements
  Specification and Acceptance Test Procedure will
  be reviewed by NASA IVV
• The following documents will be (TBR) submitted
  to the IVV analyst for RALPH
• Spacecraft to RALPH ICD, 7399-9201
• RALPH Software Development Plan,05310-05-SDP-01
  (SDP)
• RALPH Software Requirements Specification,0531-05-
  SRS-01 (SRS)
• RALPH command and telemetry spreadsheets

27
Development Status

• Software Development Plan completed July 2003
• Software Requirements Specification will be
  completed July 2003
• Command and Telemetry Spreadsheets completed
• Software prototype implemented to estimate
  hardware resource usage and simulate timing

28
Longevity

• Two PCs, both with CD writers, are required for
  the project one for software development and
  the other for EGSE
• The original CDs for the Keil 8051 embedded
  software development environment and the
  operating system will be archived with SwRI
  document control
• The entire directory structure for files for
  flight software development and EGSE will be
  written to CD and archived with SwRI document
  control. Setup notes for configuring the system
  shall be written and stored on CD as well
• Both PCs shall be configured to be identical so
  that they are interchangeable for software
  development or EGSE
• Both PCs shall not be used on any other project
• Any updates to software shall be archived
• At least every 5 years, the PCs will be upgraded
  to ensure that the EGSE software and FSW
  development environment continue to function.

29
Summary

• Command / telemetry spreadsheets completed
• Software Development Plan target date TBD
• Software Requirements Specification target
  7/18/2003
• Prototype Software Model executed for calculating
  resource timing (TBR)