CubeSat vs. Science Instrument Complexity

Slides:



Advertisements
Similar presentations
What is Hardware? Hardware is the physical parts of the computer system – the parts that you can touch and see. A motherboard, a CPU, a keyboard and a.
Advertisements

Page 1 Aalborg University Communication system for the AAUSAT-II Communication System for the AAUSAT-II Kresten K. Sørensen Department.
Overview of the SMAP Science Data Manager (SDM) Ed Benowitz SMAP FSW Developer NASA/Jet Propulsion Laboratory Caltech Copyright.
University of Kansas EPS of KUTEsat Pathfinder Leon S. Searl April 5, 2006 AE256 Satellite Electrical Power Systems.
Introduction to Space Systems and Spacecraft Design Space Systems Design Power Systems Design -I.
EEE440 Modern Communication Systems Satellite Systems.
The Solar Tracker. Solar Tracking Project Team Members: –Cristian Ruvalcaba –Ken Seal –David Clark –Mark McKinley –Richard DeJarnatt.
Simulating A Satellite CSGC Mission Operations Team Cameron HatcherJames Burkert Brandon BobianAleks Jarosz.
Mission Expectations As Planned: –Full end-to-end test of Akoya-Bandit imaging and dedicated comm subsystems –Take, store, and transmit images over 900MHz.
Instrument TrainingIDPU - 1 UCB, Dec 6, 2006 THEMIS INSTRUMENT TRAINING IDPU.
MAVEN CDR May 23-25, 2011 Particles and Fields Package Pre-Environmental Review May , 2012 Flight Software Peter R. Harvey Mars Atmosphere and Volatile.
The NASA Ames PhoneSat Project Mike Safyan DCC 2011, Baltimore 9/16/11.
Solar Probe Plus FIELDS ICU/FSW Peter R. Harvey Dorothy Gordon –ICU Will Rachelson – FSW Dec 1, 2012.
The Pursuit for Efficient S/C Design The Stanford Small Sat Challenge: –Learn system engineering processes –Design, build, test, and fly a CubeSat project.
Launching, Orbital Effects & Satellite Subsystems
Team Balloon Satellite II Multi-Disciplinary Senior Design CSEN 4201 Level II Mid-Term Report 17 October 2003 Mentor: Tony Kim.
AMSAT Fox-1 Overview AMSAT Engineering Team 2011 Space Symposium.
Command and Data Handling (C&DH)
THE AVENGERS Measuring Atmospheric Ozone gases. General  The primary goal of the ITO sensor project is to measure the concentration of Ozone (O 3 ) as.
Data Acquisition Networks DM Additional Information DM
Reference: Ian Sommerville, Chap 15  Systems which monitor and control their environment.  Sometimes associated with hardware devices ◦ Sensors: Collect.
By P.Pranavi Beyond Night Sky. 1957TILL DATE Beyond Night Sky.
Space Operations as a Guide for a Real-World Scheduling Competition Eduardo Romero Marcelo Oglietti
Test-as-You Fly SpaceWire for Solar Probe Plus
Flight Software Overview
Computer Systems. Bits Computers represent information as patterns of bits A bit (binary digit) is either 0 or 1 –binary  “two states” true and false,
Final Version Kequan Luu May 13-17, 2002 Micro-Arcsecond Imaging Mission, Pathfinder (MAXIM-PF) Flight Software.
Basic Satellite Communication (3) Components of Communications Satellite Dr. Joseph N. Pelton.
5 June 2002DOM Main Board Engineering Requirements Review 1 DOM Main Board Software Engineering Requirements Review June 5, 2002 LBNL Chuck McParland.
Characteristics of remote sensing satellites. Satellites generally vary in their architecture Usually remote sensing satellites are having two plateforms.
GoetzPre-PDR Peer Review October 2013 FIELDS Time Domain Sampler Peer Review Keith Goetz University of Minnesota 1.
HarveyFIELDS iCDR – Flight Software Solar Probe Plus FIELDS DCB Flight Software Design Peter Harvey University of California 1.
TRIO-CINEMA 1 UCB, 2/08/2010 Mission Design Dave Curtis UCB/SSL Space Sciences Laboratory University of California, Berkeley.
GLAST Large Area Telescope LAT Flight Software System Checkout TRR FSW Overview Sergio Maldonado FSW Test Team Lead Stanford Linear Accelerator Center.
ARISSat-1 Critical Design Review Orlando, Feb 15, 2010 Maximum Peak Power Point Tracker (MPPT) John Charais / Jerry Zdenek
THEMIS Instrument CDR 1 UCB, April 20, 2004 ESA & SST (ETC) Interface Board Critical Design Review Robert Abiad University of California - Berkeley.
COMPUTER HARDWARE & SOFTWARE INTRODUCTION TO LIBRARY & INFORMATION SCIENCES (5501) WORKSHOP SPRING 2013 By: Huma Malik Librarian, Preston University, Islamabad.
Computer Storage. What is Primary Storage? ● Primary storage is computer memory that is directly accessible to the CPU of a computer without the use of.
TRIO-CINEMA 1 UCB, 2/08/2010 FSW & Operations Winter Summary Seyoung Yoon KHU EE Team.
Benefits of a Virtual SIL
Simulation-to-Flight 1 Additional Resources:
USNA Standard CubeSat Bus USNA-P1 CubeSat (USNA-14)
INSTRUMENT DATA PROCESSING UNIT (IDPU) REQUIREMENTS
cFE FSW at APL & FSW Reusability
Fault Protection Techniques in JPL Spacecraft
Telemetry system The telemetry, tracking, and command (TT&C) subsystem performs several routine functions abroad a spacecraft. The telemetry or "telemetering"
ACS UC Berkeley Space Sciences Laboratory
CINEMA Orbit/Attitude? (looking down from top toward earth)
A Requirements Case Study of JUNO-JADE and SO-HIS
Integrating CCSDS Electronic Data Sheets into Flight Software
William Stallings Computer Organization and Architecture 8th Edition
CubeSat: The Wee Space Box.
William Stallings Computer Organization and Architecture 7th Edition
Colorado Space Grant Consortium
William Stallings Computer Organization and Architecture 8th Edition
BIC 10503: COMPUTER ARCHITECTURE
SLAC DOE Program Review
Launch and On-orbit Checkout
Deep Neural Networks for Onboard Intelligence
Chapter 2: Operating-System Structures
Mark Suder
IlliniSat-3 Power Board
William Stallings Computer Organization and Architecture 8th Edition
EagleSat 2 – Mission and Development Overview
Command and Data Handling
Observation and Checkout Modes (1) - Introduction -
Chapter 2: Operating-System Structures
Project Management Unit #2
5. Conclusions and future work
Presentation transcript:

CubeSat vs. Science Instrument Complexity Chad Loeffler This is a non-ITAR presentation, for public release and reproduction from FSW website.

Topics Introduction Processor Boards and Software Operations Fault Management Testing Stakes Of Destruction Conclusion This is a non-ITAR presentation, for public release and reproduction from FSW website.

Introduction Are “low-budget” CubeSats more complex than science instruments? Are they more similar or more different than expected? Two instruments are compared to two satellites: SO-HIS (science instrument) JUNO-JADE (science instrument) CUSP (CubeSat) CYGNSS (SmallSat) This is a non-ITAR presentation, for public release and reproduction from FSW website.

Processor Boards and Software JUNO-JADE (science instrument) 4 MB SRAM, 0.5 MB EEPROM, 24 MHz CPU SO-HIS (science instrument) 16 MB SRAM, 2 MB MRAM, 25 MHz and 50 MHz CPU CUSP (CubeSat) 4 MB SRAM, 2 MB MRAM, 4 GB FLASH, 50 MHz CPU CYGNSS (SmallSat) 4 MB SRAM, 4 MB MRAM, 4 GB FLASH, 25 MHz CPU This is a non-ITAR presentation, for public release and reproduction from FSW website.

Operations Science Instruments Receive commands and send telemetry Perform fault management and detection Collect and process science data, including use of high-voltage Operations Planning only has to handle reactions to thruster firings and orbit change maneuvers, not how to accomplish them Operations Planning only has to focus on data production to mass memory, not on storage and downlink to ground Usually no heater control This is a non-ITAR presentation, for public release and reproduction from FSW website.

Operations CubeSats and SmallSats Control radio for uplink and downlink Process commands and telemetry Perform fault management and detection Perform thruster firings and orbit change maneuvers Perform ADCS pointing and stability Maintain heater control for all components Maintain power levels and battery charging Store all data in mass memory, handle partitioning and downlink This is a non-ITAR presentation, for public release and reproduction from FSW website.

Fault Management Science Instruments Isolate faults to lowest level If fault is contained completely within a single sensor, but has multiple sensors, then can remain in science mode with unaffected sensors For off-nominal but not critically dangerous faults, when isolation of a component is not possible, then stay in Safe Mode No high voltage No science data collection No power to sensors For critical or dangerous faults, send Power-Off request to spacecraft This is a non-ITAR presentation, for public release and reproduction from FSW website.

Fault Management CubeSats and SmallSats “Fail Operational” instead of “Fail Safe” Most components, except for the payload, are critical and must remain operational, even if only in a minimal capacity Communications Radio Power System ADCS (Attitude Determination and Control System) and Thrusters Faults usually result in payload instruments being powered off “Safe Mode” means Sun-pointing instead of Earth-pointing This is a non-ITAR presentation, for public release and reproduction from FSW website.

Testing and Integration Science Instruments Test with a single spacecraft interface simulator or emulator Minimal external interfaces, either to the spacecraft or component between instrument and spacecraft Can have multiple internal interfaces, possibly with different protocols Sensors and detectors go through science calibration beam testing This is a non-ITAR presentation, for public release and reproduction from FSW website.

Testing and Integration CubeSats and SmallSats Test with multiple instrument interface simulators or emulators Test with multiple spacecraft component interface simulators or emulators Many interfaces Each payload instrument ADCS (Attitude Determination and Control System) and Thrusters Power System Communications Radio Each interface may have different software or hardware protocols This is a non-ITAR presentation, for public release and reproduction from FSW website.

Stakes Of Destruction Science Instruments Overwrite non-volatile memory with junk data and have no software to run Improperly use high-voltage and cause loss of science capability in sensors and detectors Low-voltage short-circuit in main electronics or non-switched component Mass produce too much data and fill up spacecraft mass memory (with caveats) This is a non-ITAR presentation, for public release and reproduction from FSW website.

Stakes Of Destruction Science Instruments A properly isolated science instrument can only end in its own destruction, not impacting the spacecraft or other science instruments Usually draws power from a switched source and has limiting or monitoring on power input Usually limited in mass-memory partition size and cannot overwrite other instruments buffers Can only cause mission end if not completely isolated from spacecraft and other science instruments, sharing power circuits or memory partitions This is a non-ITAR presentation, for public release and reproduction from FSW website.

Stakes Of Destruction CubeSats and SmallSats Failure to deploy solar panel arrays and start battery charging Failure to de-tumble and stop spinning Enable maximum power draw and point away from sun Fire thrusters too long or too little and change attitude or orbit Overwrite non-volatile memory with junk data and have no software to run Low-voltage short-circuit in main electronics or non-switched component This is a non-ITAR presentation, for public release and reproduction from FSW website.

Stakes Of Destruction CubeSats and SmallSats Unrecoverable faults in hardware and software can lead to mission end, either in loss of spacecraft or loss of payload This is a non-ITAR presentation, for public release and reproduction from FSW website.

Conclusion Stakes are higher for the CubeSat: loss of mission vs loss of single instrument. Complexity of operations, fault management, and testing is higher for the CubeSat. FSW processing needs are similar, such that similar or common processing board architectures can be used. This is a non-ITAR presentation, for public release and reproduction from FSW website.