Minimize STP-S26

STP-S26 (Space Test Program-S26)

Overview    Launch   STP-SIV   STPSat-2   Sensor Complement   Mission Status    References

STP-S26 is a USAF (United States Air Force) mission within the DoD STP (Space Test Program) managed at the Space Development and Test Wing (SDTW), Kirtland Air Force Base, NM, USA. The mission was designated "S26" to correspond to the 26th small launch vehicle mission in STP's 40+year history of flying DoD space experiments.

STP-S26 extends previous standard interface development efforts, implementing a number of capabilities aimed at enabling responsive access to space for small experimental satellites and payloads. The STP-S26 Minotaur-IV launch vehicle is configured in a Multi-Payload Adaptor configuration which includes the following features: 1) 2)

MPA (Multi-Payload Adaptor), which was developed by Orbital Sciences Corporation for STP to launch up to four ESPA-class satellites on the Minotaur-IV.

• Provisions for the inclusion of up to four P-PODs (Poly-Picosat Orbital Deployers) to be mounted on the stage 4 avionics cylinder.

• A dual orbit capability provided by the HAPS (Hydrazine Auxiliary Propulsion System). The design provides volume and mass for four additional payloads attached to the HAPS avionics cylinder.

The mission will launch four ESPA-class satellites, manifested on the MPA, and three cubesats into LEO (Low Earth Orbit). One of the four ESPA [EELV (Evolved Expendable Launch Vehicle) Secondary Payload Adapter] satellites is STPSat-2, the primary payload of STP-S26, representing the first STP-SIV (Space Test Program-Standard Interface Vehicle) mission.

STP implemented a flexible, responsive "dual path" process for a late satellite manifest change. The goal is to delay the final manifest decision as late as possible while minimizing risk. 3)

STP_S26_Auto10

Figure 1: Schematic view of the fully loaded ESPA stack (image credit: AFRL)

 

Launch: STP-S26 was launched on Nov. 20, 2010 (UTC) on a Minotaur-IV expandable launch vehicle of OSC (Orbital Sciences Corporation) with HAPS (Hydrazine Auxiliary Propulsion System) capability. The launch site was KLC (Kodiak Launch Complex) on Kodiak Island, Alaska under a contract with AAC (Alaska Aerospace Corporation). The primary payload on the STP-S26 mission was STPSat-2, the first spacecraft in the DoD STP-SIV ( Space Test Program-Standard Interface Vehicle) program managed by the Space Development and Test Wing at Kirtland Air Force Base, Albuquerque, N.M. 4) 5) 6) 7)

This launch is also the result of an NSF (National Science Foundation) program, the objective is to develop and fly CubeSat-based science missions for space weather and atmospheric research.

The STP-S26 mission demonstrated a new capability for Minotaur-IV, called MPP (Multiple Payload Platform). The MPP enables the deployment of up to 12 small satellites, consisting of four ESPA-class satellites, four smaller secondary satellites (up to 11 cubic feet each), and four P-POD carriers.

The following secondary payloads were part of the STP-S26 mission (all secondary payloads are documented in a separate file on the eoPortal):

• FalconSat-5 of USAFA (US Air Force Academy) at Colorado Springs, CO. FalconSat-5 has a mass of 161 kg.

• FASTSat-HSV (Fast, Affordable, Science and Technology Satellite-Huntsville), AL Corporation, developed by NASA/MSFC, VCSI (Von Braun Center for Science and Innovation), and Dynetics. FASTSat will be flying a total of six instruments, three of NASA and three of DoD The mass of FASTSat is 180 kg.

• O/OREOS (Organism/ORganic Exposure to Orbital Stresses), a NASA/ARC nanosatellite mission of 5.2 kg mass (triple CubeSat). 8)

• FASTRAC-1, -2, a nanosatellite pair of UTA (University of Texas, Austin) with a total mass of 54 kg.

• RAX (Radio Aurora Explorer), a triple CubeSat mission (3 kg) of NSF (National Science Foundation) - a CubeSat-based Ground-to-Space Bistatic Radar Experiment — Radio Aurora Explorer, developed by a team comprised of University of Michigan at Ann Arbor, MI and SRI International, Menlo Park, CA.

Orbit: Circular orbit, altitude = 650 km, inclination = 72o, with an orbital period of 97.7 minutes.

The STP-S26 mission delivered four ESPA-class satellites and two nanosatellites to a 650 km circular orbit at 72o inclination. The HAPS (Hydrazine Auxiliary Propulsion System) delivered two ballast masses to a secondary orbit as high as possible with a goal of 1200 km (circular), demonstrating the dual orbit capability of the Minotaur IV launch vehicle.

The ESPA-class satellites attach to the launch vehicle via the MPP (Multiple Payload Platform) and deployed using the PSC (Planetary Systems Corporation) Mark II Motorized Lightbands (MLB). The two cubesats deployed from P-PODs (Poly-Picosatellite Orbital Deployers) attached to the either side of the Stage 4 Orion-38 motor.

STP_S26_AutoF

Figure 2: Illustration of the deployed motorized lightband (image credit: AFRL, Ref. 6)

Deployment sequence:

• As the primary spacecraft on the S26 mission, STPSat-2 deploys first to minimize its risk of collision with other spacecraft.

• After one full orbit, the spacecraft must be > 800 m apart.

• The spacecraft must deploy in order of the highest to the lowest ?V in each direction, to ensure they would continue to move away from each other throughout their orbits.

Examining the deployment sequence meeting all ground rules lead the S26 program office to select the following deployment sequence, where +V indicates the direction of launch vehicle motion (see Figure 3):

1) STPSat-2 in the +V direction

2) RAX in the –V direction

3) O/OREOS in the –V direction

4) FASTSat-HSV (including NanoSail-D2) in the -V direction

5) FalconSat-5 in the –V direction

6) FASTRAC (2 nanosatellites) in the –V direction.

This separation order is keeping approximately 0.05 m/s ?V difference between any pair of spacecraft to ensure all spacecraft will be at least 800 m apart after one full orbit.

STP_S26_AutoE

Figure 3: Schematic view of the STP-S26 primary orbit separation sequence (image credit: AFRL, Ref. 1)

STP_S26_AutoD

Figure 4: The four largest satellites on the STP-S26 mission are bolted to the payload dispenser (image credit: OSC, Ref. 4)

Legend to Figure 4: STPSat-2 (left most), FASTRAC-1/-2 (front), FalconSat-5 (right most), and FASTSat (back) are visible in this image.

STP_S26_AutoC

Figure 5: Mission profile of STP-S26 (image credit: AFRL, Ref. 6)

The STP-S26 deployments were successful in the sense that the satellites continued to separate from one another after deployment. TLEs (Two Line Element) sets for each of the spacecraft a few days following the deployments were used to determine the relative drift rate between the satellites and from this the difference in their deployment ?Vs. However, there was a wider than expected difference in the ?Vs of consecutive deployments (Ref. 6).

 


 

STP-SIV (Space Test Program - Standard Interface Vehicle)

A fundamental goal of the DoD Space Test Program Standard Interface Vehicle (STP-SIV) is to enable more responsive and reliable access to space for small payloads. The objective of the STP-SIV concept is to utilize standardized interfaces between the spacecraft bus and payload as well as between the complete space vehicle and launch vehicle. Standardized interfaces encourage repeatable development and integration processes and enable staff to preserve and utilize lessons learned. A key aspect of this approach is a reusable spacecraft bus design which increases the return on investment in nonrecurring engineering and allows for shared ground support equipment between vehicles. A repeated spacecraft bus design also facilitates uniform quality control standards and offers leverage for bulk hardware purchase savings.

Standardization of the spacecraft-to-launch-vehicle interface is achieved by constraining interface features to allow for repeatable design and testing across missions. The STP-SIV overall mass and volume is constrained to 180 kg and an envelope of 60.9 cm x 71.1 cm x 96.5 cm to permit launches on an ESPA (EELV Secondary Payload Adapter), shown in Figure 6, and small launch vehicles including Pegasus and Minotaur class vehicles. 9)

STP_S26_AutoB

Figure 6: Concept drawing of the ESPA secondary payload envelope (image credit: AFRL)

In 2006, BATC (Ball Aerospace Technology Company) of Boulder, CO, and Comtech AeroAstro of Ashburn, VA, were given a contract to build up to six small standard satellites for SMC/TEL (Space and Missile Systems Center / Space and Missile Test Evaluation Directorate) at Kirtland Air Force Base, Albuquerque, NM.

In this arrangement, Comtech AeroAstro is responsible for supplying the spacecraft bus as well as providing integration, launch and mission operation support. As prime contractor, BATC is responsible for the overall system including the standard payload interface design, payload integration, space vehicle environmental testing, and launch and mission support. 10) 11) 12)

STP-SIV missions are considered ideal for scientific, technology development, and risk reduction payloads. Each vehicle accommodates up to four independent payloads, is designed to operate over a wide range of LEO orbits, and is compatible with a variety of small launch vehicles. The potential to share the spacecraft and launch provides an opportunity for the cost effective access to space for a variety of payloads. 13) 14) 15)

Spacecraft capabilities

Orbital altitude range, orbit inclination

400 - 850 km, 0o - 98.8o

Launch mass

? 180 kg (ESPA driven),

Spacecraft volume

? 60.9 cm x 71.1 cm x 96.5 cm

Launch vehicle compatibility

Delta-4 ESPA, Atlas-5 ESPA, Minotaur-1, Minotaur-4,
Pegasus, and Falcon-1

Spacecraft lifetime

13 months

Reliability @ 7 months after launch

0.90

Spacecraft stabilization method

- 3-axis
- Attitude knowledge: 0.03o 3? (goal 0.02o 3?)
- Attitude control: 0.1o 3? (goal 0.03o 3?)

Pointing modes

Nadir, sun pointing (short duration), inertial, safe

Bus voltage

28 V ±6

RF communications

- L-band uplink, S-band downlink (encrypted, SGLS compatible)
- Data rates: 2 kbit/s uplink, 2 Mbit/s downlink
- Onboard storage capacity: 16 Gbit

Payload accommodation (total)

Payload mass, volume

? 70 kg, 0.14 m3

Payload orbit average power

100 W

Payload FOR (Field of Regard)

Unobstructed hemispherical field of view

Number of payloads

Up to four

Payload data handling

Up to 2.0 Mbit/s from each payload

Payload digital command/data interface

RS-422 provides real-time & high rate (synchronous and UART-selectable) data, command, 8 input and 8 output bi-level discretes per payload

Payload analog data interface

8 analog channels per payload for health and status

Payload heat rejection

100 W

Table 1: Overview of requirements envelope for the STP-SIV bus concept

The SDTW (Space Development & Test Wing) of SMC (Space and Missile Systems Center) is the entity that "develops, tests, and evaluates the Air Force space systems, executes advanced space development and demonstration projects, and rapidly transitions capabilities to the warfighter". SDTW is the operator of such missions as: STPSat-1, Orbital Express, TacSat-2, and NASA's CloudSat. 16) 17) 18)

In Oct. 2007, the CDR (Critical Design Review) was completed. On Jan. 7, 2009, CAA (Comtech AeroAstro Inc.) delivered the first STP-SIV spacecraft bus to BATC.

In Oct. 2009, BATC has successfully completed a comprehensive pre-shipment review for STPSat-2. 19)

STP_S26_AutoA

Figure 7: Standard bus concept of STPSat-2 (STP-SIV), image credit: Comtec AeroAstro Inc. (Ref. 13)

STP_S26_Auto9

Figure 8: Conceptual view of the basic STP-SIV spacecraft design (image credit: SDTW, BATC, AeroAstro)

Spacecraft:

STP-SIV defines a standard in the sense of an interface between spacecraft and payload and an interface between spacecraft and launch vehicle. The STP-SIV bus design supports the program goal of a low-risk bus by using flight-proven components, a simple structural design, and significant design and software reuse from prior missions. The design balances a low-cost and low-risk approach with significant spacecraft capability and flexibility. Table 1 highlights the threshold requirements and performance goal characteristics for the spacecraft.

The SIV (Standard Interface Vehicle) concept is considered a recurrent bus with adaptable interfaces to accommodate a range of payloads. The spacecraft will accommodate one to four payloads with a total up to 60 kg and 100 W orbit average power mounted to an external PIM (Payload Interface Module). The PIM is separable; it may be integrated in parallel with the bus to support accelerated launch schedules and reduce technical risk.

STP_S26_Auto8

Figure 9: Schematic of STP-SIV bus and PIM to accommodate a range of payloads (image credit: SDTW, BATC)

STP_S26_Auto7

Figure 10: Schematic view of the STP-SIV external interfaces (image credit: SDTW, BATC, AeroAstro)

STP_S26_Auto6

Figure 11: View of the STP-SIV spacecraft bus and allowable PIM (green) envelope (image credit: SDTW, BATC)

The payloads mount to the spacecraft using a standard payload mechanical interface shown in Figure 12. The payloads mount to the PIP (Payload Interface Plate) using fasteners and holes on 2.54 cm centers. The PIM provides a total payload volume of 0.14 m3, a box of size: 66.80 cm x 49.40 cm x 44.95 cm. The allowable payload envelope in the launch configuration is shown in Figure 11.The payloads will be mounted ‘on-top' of the bus and must fit within this volume for launch. Once the spacecraft is on orbit and deploys the solar arrays, the payloads may deploy elements as necessary to perform their missions. All deployed elements shall remain above (+ZPL) the payload interface plane (Ref. 16).

STP_S26_Auto5

Figure 12: The PIP with the payload coordinates provides a standard mounting grid (image credit: SDTW, BATC)

The payloads are provided an unobstructed field of view of 2 steradian, oriented towards the +ZPL (nadir) axis and originating at the payload interface plane. Additionally, the payloads are provided a 2? steradian unobstructed field of view towards the +XPL (velocity direction until seasonal yaw flip), originating 55 cm from the leading edge of the PIP in the +XPL direction. This provides nearly 3? steradians of unobstructed views for the payloads.

Power interface: During normal mission operations, the S/C provides a minimum 100 W orbit average power (OAP) to the payload suite. This power is allocated between the different payloads on each mission. If the total power draw for all payloads exceeds 100 W, it may be necessary to duty cycle the payload operations to reduce the payload suite power consumption to within the capability of the S/C. Each payload is provided three switched power feeds. Each power feed provides unregulated 28±6 VDC from the S/C. The S/C provides over-current protection on each power line provided to the payload.
The EPS (Electrical Power Subsystem) consists of 2 fixed/deployed solar arrays with ATJ (Advanced Triple Junction) GaAs solar cells (one array is gimballed). The Li-ion battery has a capacity of 30 Ah.

Data interface: The IAU (Integrated Avionics Unit) functions as the main data and command interface between the payloads. All payload command, data collection, and data storage is via the PIB (Payload Interface Board) which resides within the IAU. The PIB provides each payload one data port which consists of a 62 pin high density dHDD connector on the payload module. All payload commands and collection of high rate data, real-time data, analogs and discretes is through the single 62 pin data port. All payload data (high rate and real-time) is polled and ingested in a "round robin" scheme ensuring that no payload can monopolize the bus. Both the payload high rate and real-time data are time-stamped at the time of receipt.

The PIB ingests the payload high rate mission data, encapsulates this data in a CCSDS (Consultative Committee for Space Data Systems) compliant CADU (Channel Assess Data Unit) format and stores the formatted CADU for subsequent transmission to the ground. All high rate data is transferred via either an asynchronous UART (Universal Asynchronous Receiver/Transmitter) EIA-422 link or a synchronous EIA (Electronic Industry Alliance) compliant RS-422 link. The choice of synchronous or asynchronous data transfer method is selectable for each PL and is fixed prior to launch. The total high data rate available is 2 Mbit/s shared amongst all the payloads. The PIB provides a total mass memory storage of 8 Gbit of EDAC validated memory space. The memory is shared amongst all 4 payloads for high rate, real-time and stored state of health data (Ref. 16).

STP_S26_Auto4

Figure 13: PIB system block diagram illustrating the standard data interface (image credit: SDTW, BATC)

STP_S26_Auto3

Figure 14: Artist's view of the STP-SIV integrated with ESPA ring (image credit: Comtech AeroAstro)

Spacecraft to AFSCN interface: The interface between STP-SIV and ground facilities is controlled by two documents; an ICD (Interface Control Document) and the Standardized Interface Specification for the AFSCN (Air Force Satellite Control Network), SIS-000502C. SIS-000502 defines the types of service provided by the AFSCN and the design requirements for the SV radio frequency (RF) system.

The ICD describes the specific characteristics employed by the space vehicle RF system to show compliance with these requirements. This includes defining the exact operating frequency, subcarrier frequencies, modulation scheme, etc. Telecom frequencies have been selected and pre-approved by the relevant licensing organization for use on future SIVs. This eliminates risk of the sometime time-consuming approval process and enables transponder production to proceed without interruption. With predetermined frequencies, a transponder or full SIV could be produced and "on the shelf" for deployment in a responsive space application since there is no uncertainty in the mission telecom frequency and no risk of changes. 20) 21)

STPSat-2 mission operations are performed at the Research, Development, Test & Evaluation (RDT&E) Support Complex (RSC) at Kirtland AFB, NM.

 

STP_S26_Auto2

Figure 15: Ground segment interface definition of the STP-SIV (image credit: SDTW)

 


 

STPSat-2 (Space Test Program Satellite-2)

STPSat-2 is the first spacecraft within the STP-SIV program and the prime payload on the STP-26 mission (Note: STPSat-2 is commonly also referred to as STP-SIV). STPSat-2 has a mass of 137 kg and accommodates two SERB (Space Experiment Review Board) experiments.

Comtech AeroAstro's role is to design, build, and integrate the SIV bus under subcontract to prime integrator Ball Aerospace. The first SIV bus, for the STPSat-2 mission, was delivered to Ball in December 2008 (Ref.14).

STP_S26_Auto1

Figure 16: Photo of the STPSat-2 spacecraft (image credit: BATC)

STP_S26_Auto0

Figure 17: Photo of the deployed STPSat-2 spacecraft (image credit: BATC)

RF communications: The STP-SIV RF system is based on a single string L3 COM CXS-810C transponder. Use of the SGLS (Space Ground Link Subsystem) transponder consisting of a command/ranging receiver with embedded decryptor and power converter and a telemetry/ranging transmitter with embedded encryptor and power converter. The ground system architecture is shown in Figure 15.

 


 

Sensor complement of STPSat-2: (SPEX, ODTML)

SPEX (Space Phenomenology Experiment):

The objective is to demonstrate the suitability of sensors in the space environment.

ODTML (Ocean Data Telemetry Microsat Link):

ODTML, a next generation data collection system, is provided by ONR (Office of Naval Research). The objective is to collect data from sea-based buoys and to transmit the information back to a ground station. Current methods of obtaining data from these terminals (i.e., Service Argos and airborne platforms) are considered costly, time consuming, and/or inefficient. - ODTML is flown on TacSat-3, launched on May 19, 2009. 22) 23) 24)

ODTML is a transponder concept developed and demonstrated by Praxis Inc. of Alexandria, VA. It uses COTS (Commercial-off-the-Shelf) technologies to improve the data collection and dissemination process for remote sensors. Some capabilities of ODTML are:

• ODTML uses a two-way delay-tolerant messaging capability to provide 'Internet-like' services on global basis to support ocean platform monitoring and provide near real time situational data to web-based maps and other data analysis systems.

• ODTML uses higher bandwidths and lower power than the current Argos DCS (Data Collection System)

- > 50 kbit per node per day

- < 0.1 Joule per bit transmitted.

The ODTML network system consists of the following elements:

1) "Smart sensor nodes," each containing an RF terminal, which collect the sensor data and communicate with the satellite payload. These smart sensor nodes are mounted on the sensor platforms, e.g., free-floating buoys or UGS (Unattended Ground Sensors).

2) Spacecraft Communications Payload (SCP), a microsatellite-mounted payload serving as a "router in the sky."

3) Portable ground stations, acting as gateways to transfer the sensor data from the RF link to the Internet.

4) The Internet, as the communication conduit between the users and the ocean and ground-based observing platforms.

 

STPSat-2 mission status:

• 2015: According to the WMO OSCAR website, theSPTSat-2 spacecraft of DoD is operational as of 2015. 25)

• The STPSat-2 spacecraft and the three payloads continue to operate nominally in 2012. Ball Aerospace & Technologies Corp. will provide an additional year of support for the STPSat-2 spacecraft, following completion of the initial experimental mission requirements that ended successfully on Jan. 31, 2012. 26)

The operational mission for STPSat-2, which launched on Nov. 19, 2010, has been extended for an additional year. Under contract to the SD at Kirtland Air Force Base, Ball Aerospace will continue to provide space vehicle support to the satellite through Feb. 1, 2013.

• The MMSOC-GSA (Multi-Mission Satellite Operations Center - Ground System Architecture) of SMC/SDTC is providing on-orbit operations for STPSat-2. 27)

 


1) Holly Borowski, Kenneth Reese, Mike Motola, "Responsive Access to Space: Space Test Program Mission S26," Proceedings of the 2010 IEEE Aerospace Conference, Big Sky, MT, USA, March 6-13, 2010

2) Richard Murphy, "Department of Defense Space Test Program," URL: http://ppmo.arc.nasa.gov/media/STP_for_PPMO.pdf

3) David A. Kaufman, Michael Pierce, Michael Katz, Kenneth Reese, "STP-SIV: Real World Responsiveness of Spacecraft Interface Standardization," Reinventing Space Conference, May 2-5, 2011, Los Angeles, CA, USA, paper: AIAA-RS-2011-1003, URL: http://www.responsivespace.com/Papers/RS2011/SESSIONS/SESSION%20I
/1003_KAUFMAN/1003P.pdf

4) http://www.orbiter-forum.com/showthread.php?p=219924

5) "Ball Aerospace Ships STPSat-2 To Kodiak Launch Complex," Space Daily, Aug. 3, 2010, URL: http://www.spacedaily.com/reports/Ball_Aerospace_Ships_STPSat_2_To_Kodiak
_Launch_Complex_999.html

6) Dana Rand, Rachel Derbis, Austin Eickman, Robert Wilcox, Joseph Bartsch, Maria Elena Foster, Sabrina Herrin, "Multi-Payload Integration Lessons Learned from Space Test Program Mission S26," Proceedings of the 25th Annual AIAA/USU Conference on Small Satellites, Logan, UT, USA, Aug. 8-11, 2011, paper: SSC11-II-1

7) "STS-S26 Stage Set," MilsatMagazine, September/October 2010, URL: http://www.akaerospace.com/docs/Milsat%20Magazine%20STP-S26%20Article.pdf

8) John W. Hines, "Nanosatellite Missions in the NASA-Ames Small Spacecraft Division," Fifth Annual CubeSat Developer's Workshop, April 11, 2008, Moffett Field, CA, URL: http://mstl.atl.calpoly.edu/~bklofas/Presentations/DevelopersWorkshop2008/session6/5-NASA_Ames-John_Hines.pdf

9) Thomas D. Chavez, Mark J. Barrera, Matthew H. Kanter, "Operational Satellite Concepts for ESPA Rideshare," Proceedings of the 2007 IEEE Aerospace Conference, Big Sky, MT, March 3-10, 2007

10) "STPSat-2/STP-SIV," URL: http://www.aeroastro.com/index.php/current-programs/stpsat-2-stp-siv

11) http://www.wikicover.com/Standard_Interface_Vehicle

12) J. H. Eraker, "Technology Tools for Space Weather Advancement," The Space Weather Enterprise Forum, May 19-20,, 2009, Washington DC, USA, URL: http://www.ofcm.gov/swef/2009/Presentations/Session%205%20Presentations/s05-03_Space%20Weather%20Economic%20Forum.pdf

13) Steven W. Schenk, Stanley O. Kennedy Jr., "ISET Compliant Modular Multi-Mission Space Vehicle Design Feasibility for Rapid Response," 7th Responsive Space Conference, April 27–30, 2009, Los Angeles, CA, USA, paper: RS7-2009-3002, URL: http://www.responsivespace.com/Papers/RS7/SESSIONS/Session%20III/3002_Schenk/3002C.pdf

14) "STPSat-2/STP-SIV," URL: http://www.aeroastro.com/index.php/current-programs/stpsat-2-stp-siv

15) Nicholas Merski, Kenneth Reese, Michael Pierce, David Kaufman, "Space Test Program Standard Interface Vehicle Lessons Learned: An Interim Assessment of Government and Contractor Progress Towards Development of a Standard, Affordable ESPA-Class Spacecraft Product Line," Proceedings of the 2010 IEEE Aerospace Conference, Big Sky, MT, USA, March 6-13, 2010

16) Chris Badgett, Mike Marlow, Hallie Walden, Mike Pierce, "Payload Design Criteria for the DoD Space Test Program Standard Interface Vehicle," AIAA-RS6-2008-5006, 6th Responsive Space Conference, April 28 to May 1, 2008, Los Angeles, CA, USA, URL: http://www.responsivespace.com/Papers/RS6/SESSIONS/SESSION%20VI/5006_MARLOW/5006P.pdf

17) Mike Marlow, "Payload Design Criteria for the DoD Space Test Program Standard Interface Vehicle (STP-SIV)," 6th Responsive Space Conference, April 28 to May 1, 2008, Los Angeles, CA, USA, URL: http://www.responsivespace.com/Papers/RS6/SESSIONS/SESSION%20VI/5006_MARLOW/5006C.pdf

18) Christopher Badgett, Nicholas Merski, Michael Hurley, Paul Jaffe, Hallie Walden, Alan Lopez, Michael Pierce, David Kaufman, "STP-SIV and ORS ISET Spacecraft-To-Payload Interface Standards," Proceedings of the 2009 IEEE Aerospace Conference, Big Sky, MT, USA, March 7-14, 2009

19) "BALL CRP: Ball Aerospace Completes STPSat-2 Satellite Pre-Shipment Review," Oct. 13, 2009, URL: http://www.4-traders.com/BALL-CRP-11863/news/BALL-CRP-Ball-Aerospace-Completes-STPSat-2-Satellite-Pre-Shipment-Review-13260280/

20) Michael Pierce, David Kaufman, Kenneth Reese, "STP-SIV: Lessons Learned Through the First Two Standard Interface Vehicles," Proceedings of the 25th Annual AIAA/USU Conference on Small Satellites, Logan, UT, USA, Aug. 8-11, 2011, paper SSC11-III-7

21) Michael Pierce, David Kaufman, David Acton, Kenneth Reese, "STP-SIV: Lessons Leanned Through the First Two Standard Interface Vehicles," Proceedings of the 2012 IEEE Aerospace Conference, Big Sky Montana, USA, March 3-10, 2012

22) Bob McCoy , "Space Segment for Global Autonomous Sensors," Distributed Arrays of Small Instruments (DASI) Workshop 8 June 2004, URL: http://download.hao.ucar.edu/oldpub/ganglu/DASI/McCoy_DASI.ppt

23) "Ocean Data Telemetry Microsat Link (ODTML)," PRAXIS, URL: http://www.pxi.com/project_odtml.php

24) R. Jack Chapman, Joseph A. Hauser, "Ocean Data Telemetry Microsat Link (ODTML)," 2008, URL: http://www.dtic.mil/cgi-bin/GetTRDoc?Location=U2&doc=GetTRDoc.pdf&AD=ADA533972

25) "Satellite: STPSat-2," WMO OSCAR, January 9, 2015, URL: http://www.wmo-sat.info/oscar/satellites/view/543

26) Roz Brown, "Ball Aerospace's STPSat-2 Completes Experimental Mission," BATC News Release, April 12, 2012, URL: http://www.ballaerospace.com/page.jsp?page=30&id=466

27) Tiffany Morgan, "Multi-Mission Satellite Operations Center - Ground System Architecture (MMSOC GSA)," Feb. 29, 2012, URL: http://csse.usc.edu/gsaw/gsaw2012/s11a/morgan.pdf
 


The information compiled and edited in this article was provided by Herbert J. Kramer from his documentation of: "Observation of the Earth and Its Environment: Survey of Missions and Sensors" (Springer Verlag) as well as many other sources after the publication of the 4th edition in 2002. - Comments and corrections to this article are always welcome for further updates (herb.kramer@gmx.net).

Overview     Launch   STP-SIV   STPSat-2   Sensor Complement   Mission Status    References    Back to top