# MidSTAR-1 > Mediated Wiki article. Canonical URL: https://mediated.wiki/source/MidSTAR-1 > Markdown URL: https://mediated.wiki/source/MidSTAR-1.md > Source: https://en.wikipedia.org/wiki/MidSTAR-1 > Source revision: 1337136880 > License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/) This article needs more citations. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "MidSTAR-1" – news · newspapers · books · scholar · JSTOR (August 2023) (Learn how and when to remove this message) MidSTAR-1 **MidSTAR-1** is an artificial [satellite](/source/Satellite) produced by the [United States Naval Academy](/source/United_States_Naval_Academy) [Small Satellite Program](/source/Small_Satellite_Program_(United_States_Naval_Academy)). It was sponsored by the [United States Department of Defense](/source/United_States_Department_of_Defense) (DoD) [Space Test Program](/source/Space_Test_Program) (STP), and was launched on March 9, 2007 at 03:10 UTC, aboard an [Atlas V](/source/Atlas_V) [expendable launch vehicle](/source/Expendable_launch_vehicle) from [Cape Canaveral Air Force Station](/source/Cape_Canaveral_Air_Force_Station). MidSTAR-1 flew along with [FalconSat 3](/source/FalconSat_3), [STPSat 1](https://en.wikipedia.org/w/index.php?title=STPSat_1&action=edit&redlink=1), and [CFESat](/source/CFESat) as secondary payloads; the primary payload was [Orbital Express](/source/Orbital_Express).[1] ## MidSTAR-1 Mission (USNA-5) MidSTAR-1 Mission Patch MidSTAR is a general-purpose satellite bus capable of supporting a variety of space missions by easily accommodating a wide range of space experiments and instruments. The integration of the experiments with the satellite bus must be accomplished with minimal changes to the satellite bus design. MidSTAR is intended to be a relatively low-cost, quick response platform accommodating small payloads approved by the DoD Space Experiments Review Board (SERB) and awaiting launch through STP. MidSTAR is designed for use on the [EELV Secondary Payload Adapter](/source/EELV_Secondary_Payload_Adapter) (ESPA) Ring developed by [Air Force Research Laboratory](/source/Air_Force_Research_Laboratory) (AFRL) for placement on [Delta IV](/source/Delta_IV) or [Atlas V](/source/Atlas_V) expendable launch vehicles. MidSTAR is a Class D spacecraft, produced at minimum cost with a correspondingly higher technical risk in production and operation. It is intentionally simple in design and rugged in construction, using commercial off-the-shelf “plug-and-play” components to the greatest extent possible. Component development and circuit-board level design are accomplished only when necessary.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] MidSTAR-1 is the first implementation of the design. It was commissioned by STP to carry the Internet Communications Satellite (ICSat) Experiment for SSP and the [Configurable Fault Tolerant Processor (CFTP)](/source/Configurable_Fault_Tolerant_Processor_(CFTP)) Experiment for [Naval Postgraduate School](/source/Naval_Postgraduate_School) (NPS). In addition, MidSTAR-1 carries the Nano Chem Sensor Unit (NCSU) for the [National Aeronautics and Space Administration](/source/National_Aeronautics_and_Space_Administration) (NASA) [Ames Research Center](/source/Ames_Research_Center); Eclipse, built by Eclipse Energy Systems, Inc. for NASA [Goddard Space Flight Center](/source/Goddard_Space_Flight_Center) (GSFC); and the Micro Dosimeter Instrument (MiDN), sponsored by the [National Space Biomedical Research Institute](/source/National_Space_Biomedical_Research_Institute) (NSBRI) and built by the USNA Department of Aerospace Engineering. The mission is intended to last two years.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] ## Mission architecture The MidSTAR-1 mission included a single spacecraft under the command and control of a single satellite ground station (SGS) located at the [United States Naval Academy](/source/United_States_Naval_Academy), Annapolis, Maryland. The ground station forwarded downlinked data files to the principal investigators via the Internet. The launch segment for MidSTAR-1 utilized an [Atlas V](/source/Atlas_V) launch vehicle through the [Space Test Program](/source/Space_Test_Program), placing the satellite in a [circular orbit](/source/Circular_orbit) at 496 km altitude, 46 degrees inclination. The satellite used an uplink at 1.767 GHz with an [intermediate frequency](/source/Intermediate_frequency) (IF) of 435 MHz, and a 2.20226 GHz downlink. By utilizing [Gaussian Minimum-Shift Keying](/source/GMSK) [modulation](/source/Modulation),[2] communications with the satellite were achieved at 68.4 [kbit](/source/Kilobit)/s or higher data rate. The satellite also used [open source software](/source/Open_source_software) based on the [Linux](/source/Linux) [operating system](/source/Operating_system). MidSTAR-1 had no attitude control or determination and no active thermal control. The craft had a mass of 118 kg.[3] One hundred percent success was defined as the successful launch and operation of the satellite with full support for the two primary experiments for two years. Fifty percent success was the successful launch and operation of the satellite with: Full support of one primary experiment for two years; Full support of both primary experiments for one year; or, partial support of both primary experiments for two years. Thirty-three percent success was successful launch of the satellite and full operation of the satellite bus with partial support of any combination of primary and secondary payloads for any length of time.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] ## Mission log This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2011) (Learn how and when to remove this message) 9 March 2007: MidSTAR-1 flew as part of the [STP-1](https://en.wikipedia.org/w/index.php?title=STP-1&action=edit&redlink=1) mission on a United Launch Alliance Atlas V from [Cape Canaveral](/source/Cape_Canaveral) Air Force Station. Liftoff occurred at 0310 [UTC](/source/UTC); spacecraft separation occurred at 0332 UTC. [USNA SGS](https://en.wikipedia.org/w/index.php?title=USNA_SGS&action=edit&redlink=1) successfully acquired communications with the spacecraft during the first pass over Annapolis [MD](/source/Maryland) at 0459 UTC. The spacecraft was operating nominally in [safe mode](/source/Safe_mode_(spacecraft)).[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] 21 March 2007: [CFTP](/source/Configurable_Fault_Tolerant_Processor) turned on at 2217 UTC to add 6 W continuous to the electrical power system load and thus lessen charging stress on the batteries. 28 March 2007: [MiDN](https://en.wikipedia.org/w/index.php?title=MiDN&action=edit&redlink=1) turned on at approximately 2400 UTC. Spacecraft stopped responding to all ground commands subsequent to this pass. 4 April 2007: First use of *[firecode reset](https://en.wikipedia.org/w/index.php?title=Firecode_reset&action=edit&redlink=1)* of spacecraft at approximately 2130 UTC. This command toggles the reset switch on the MIP-405 processor and reboots the operating system. This reset returned the CFTP and MiDN experiments to *off* and cleared all command buffers. At 2324 UTC the spacecraft responded to a *transmitter on* command. Telemetry confirmed that the reboot was successful. 5 April 2007: CFTP and MiDN turned back on. 6 April 2007: Selective download of MiDN files retrieved 71 files of 92 [bytes](/source/Byte) each which were delivered to the Principal Investigator (PI). This was the first successful retrieval of science data from the spacecraft. With this milestone, MidSTAR-1 satisfied the criteria of 33% mission success. 26 May 2007: NCSU turned on at approximately 1900 [Z](/source/Zulu_Time). 29 May 2007: First data package delivered to [NCSU](/source/NCSU) PI. All four experiments are on and delivering data to the PIs. 18 June 2007: NASA press release announces success of NCSU. 5 September 2007: Spacecraft computer froze as a result of unknown influences, most likely radiation-induced upsets. This happened while the spacecraft was in full sun and with the power drains (30 W) on to prevent battery overcharging. Without the computer to cycle the drains off, the spacecraft remained in a continuous negative net power configuration which eventually drained the batteries. When the battery voltage dropped below 8 V, the electronic switches for the drains defaulted to off, returning the spacecraft to positive net power and allowing the batteries to recharge. 7 September 2007: Once the batteries recharged sufficiently, the computer restarted successfully. Restart occurred 48 hours after the initial event. No telemetry from the spacecraft or any experiment is available for that 48-hour period. Telemetry indicates that normal operation resumed, but all experiments were left off pending post-event analysis and the development of a plan to bring them back online. 12 September 2007: CFTP restarted. 21 September 2007: MiDN restarted. April 2009: Contact with MidSTAR-1 lost. Spacecraft ceased transmitting and failed to respond to ground command. Anomaly attributed to failure of battery packs. MidSTAR-1 declared non-operational. MidSTAR-1 fully supported all onboard experiments for two full years, fulfilling the 100% success criteria.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] 17 August 2023: the satellite decayed from orbit.[4] ## Structure The MidSTAR-1 frame is an [octagonal](/source/Octagon) structure 32.5["](/source/Inch) along the long axis, including separation system, and 21.2"x21.2" measured side-to-side in cross-section. The deployment mechanism is mounted on the negative x face. The positive x face is reserved for externally mounted experiments. Of the 38" along the x-axis allowed in the [ESPA](/source/ESPA) envelope, 2-4" are reserved for the deployment mechanism (15-in motorized lightband manufactured by Planetary Systems, Inc.), and 4-6" are reserved for external experiments. The frame length is 30". All eight sides of the spacecraft are covered with solar cells in order to maximize the power available. Eight dipole antennas are mounted on the four faces of the spacecraft which "cut the corners" of the ESPA envelope and are therefore positioned within the ESPA envelope rather than coincident with the envelope surface. The remaining sides are mounted with remove-before-flight eyeholes for lifting and transport during ground support. MidSTAR-1 has three interior shelves which provide area inside the satellite for mounting of components and payloads. Their locations are determined by the dimensions of the payloads and components. These can be varied in future implementations of the MidSTAR model, if necessary, as long as the structure remains within the [center of gravity](/source/Center_of_gravity) requirements. The load-bearing structure of the octagon consists of the top and bottom decks, connected at the eight corners by stringers. The side panels of the spacecraft are 1/8" aluminum panels mounted to the stringers with #10 [bolts](/source/Bolt_(fastener)).[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] ## Command and Data Handling (C&DH) The mission of the Command and Data Handling System (C&DH) is to receive and execute commands; collect, store, and transmit house-keeping data; and support the onboard payloads. The flight computer is designed to control the satellite and manage telemetry and experiment data for a minimum of two years. The C&DH system consists of a custom-modified [MIP405-3X](https://en.wikipedia.org/w/index.php?title=MIP405-3X&action=edit&redlink=1) single board computer which included (i) 133 MHz PowerPC processor; (ii) 128 [MB](/source/Megabyte) [ECC](/source/ECC_memory); (iii) 4 RS-232 asynchronous serial ports; (iv) 1 Ethernet Port; (v) a PC/104 bus; (vi) a PC/104+ bus; and, (vi) a 202-D384-X Disc on Chip providing 384 MB of secondary storage. The computer board is supported by an ESCC-104 Synchronous Serial Card with 2 synchronous serial ports, and an [EMM-8M-XT](https://en.wikipedia.org/w/index.php?title=EMM-8M-XT&action=edit&redlink=1) [Serial Expansion Card](https://en.wikipedia.org/w/index.php?title=Serial_Expansion_Card&action=edit&redlink=1) with 8 [RS-232](/source/RS-232)/422/485 asynchronous serial ports and 8 digital I/O channels. A modified I0485 data acquisition board provides 22 [analog](/source/Analog_signal) [telemetry](/source/Telemetry) channels and 32 digital I/O channels. The decision to use the PowerPC based MIP405 over an x86 based board was based solely on the low power consumption of the board combined with the feature set. The choice was limited to x86, PowerPC, and [ARM](/source/ARM_architecture) processor architectures because of a program decision to use the Linux operating system. The MIP405 integrates Ethernet, serial ports, and Disk-on-Chip interface on a single board while providing 128 MB of ECC memory and a powerful processor for under 2 watts. The closest x86 based system with comparable features found consumed 5 watts of power.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] The M-Systems Disk-on-Chip was chosen because it was the *de facto* standard flash memory harddisk replacement. Flash memory was chosen over a traditional hard disk to increase reliability and reduce power. The 384 MB version was chosen to provide the storage required for the operating system and still maintain adequate margin. The Diamond Systems Emerald-MM-8 was chosen for the asynchronous serial board based on its innate flexibility with any of the 8 ports capable of being configured as RS-232, RS-422, RS-485. RMV's IO485 data acquisition and control board was chosen for the distributed telemetry system because of built-in support for daisy chaining and handling a large number of boards. The integrated expandability is fundamental to addressing future telemetry issues in later versions of the MidSTAR line.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] The C&DH uses the [Linux](/source/Linux) operating system with a 2.4 series kernel. To create an open software architecture the [IP protocol stack](https://en.wikipedia.org/w/index.php?title=IP_protocol_stack&action=edit&redlink=1) was chosen to provide inter process, intra-satellite, and satellite-ground communications. This allowed programs created at different facilities on different hardware to be integrated with minimum difficulty.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] All internal and external communications use internet protocols. TCP is used for all internal satellite communications; UDP or MDP is used on the uplink and downlink.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] ## See also - [Spaceflight portal](https://en.wikipedia.org/wiki/Portal:Spaceflight) - [USNA MidSTAR Program](/source/USNA_MidSTAR_Program) - [eoPortal describes MidSTAR-1](https://web.archive.org/web/20070315210402/http://directory.eoportal.org/pres_MidSTAR1MidshipmenSpaceTechnologyApplicationsResearch1.html) ## References 1. **[^](#cite_ref-1)** ["Historic launch puts six satellites into orbit at once"](https://web.archive.org/web/20240726063613/https://www.kirtland.af.mil/News/Article-Display/Article/390510/historic-launch-puts-six-satellites-into-orbit-at-once/). *Kirtland Air Force Base*. Archived from [the original](https://www.kirtland.af.mil/News/Article-Display/Article/390510/historic-launch-puts-six-satellites-into-orbit-at-once/) on 2024-07-26. Retrieved 2025-11-15. 1. **[^](#cite_ref-2)** ["MidSTAR Communications"](https://web.archive.org/web/20040929142613/http://cadigweb.ew.usna.edu/~midstar/index.php?sect=comms&subsect=req). Archived from [the original](http://cadigweb.ew.usna.edu/~midstar/index.php?sect=comms&subsect=req) on 29 September 2004. 1. **[^](#cite_ref-3)** ["NASA - NSSDCA - Spacecraft - Details"](https://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=2007-006B). *nssdc.gsfc.nasa.gov*. Retrieved 2023-11-30. 1. **[^](#cite_ref-4)** ["MIDSTAR 1"](https://www.n2yo.com/satellite/?s=30773#results). *N2YO.com*. 17 August 2023. Retrieved 19 August 2023. v t e ← 2006 Orbital launches in 2007 2008 → January Cartosat-2, SRE-1, Lapan-TUBsat, Pehuensat-1 Progress M-59 NSS-8 February Beidou-1D THEMIS A, THEMIS B, THEMIS C, THEMIS D, THEMIS E IGS Radar 2, IGS Optical 3V March ASTRO, CFESat, FalconSAT-3, MidSTAR-1, NEXTSat, STPSat-1 Skynet 5A, INSAT-4B April Soyuz TMA-10 Anik F3 Hai Yang 1B Compass-M1 EgyptSat 1, Saudisat-3, SaudiComsat-3, SaudiComsat-4, SaudiComsat-5, SaudiComsat-6, SaudiComsat-7, CP-3, CP-4, CAPE-1, Libertad 1, AeroCube 2, CSTB-1, MAST AGILE, AAM NFIRE AIM May Astra 1L, Galaxy 17 Progress M-60 NigComSat-1 Yaogan 2, Zheda PiXing 1 Globalstar 65, Globalstar 69, Globalstar 71, Globalstar 72 Sinosat-3 June Kosmos 2427 COSMO-1 STS-117 (ITS S3/4) Ofek-7 TerraSAR-X USA-194 Genesis II Kosmos 2428 July SAR-Lupe 2 Zhongxing 6B DirecTV-10 August Progress M-61 Phoenix STS-118 (ITS S5, SpaceHab LSM) Spaceway-3, BSAT-3a September INSAT-4CR JCSAT-11 Kosmos 2429 Kaguya (Okina, Ouna) Foton-M No.3, YES2 WorldView-1 CBERS-2B Dawn October Intelsat 11, Optus D2 Soyuz TMA-11 USA-195 USA-196 Globalstar 66, Globalstar 67, Globalstar 78, Globalstar 70 Kosmos 2430 STS-120 (Harmony) Chang'e 1 Kosmos 2431, Kosmos 2432, Kosmos 2433 November SAR-Lupe 3, Rubin-7 USA-197 Yaogan 3 Skynet 5B, Star One C1 Sirius 4 December Globus-1M No.11L COSMO-2 USA-198 Radarsat-2 USA-199 Horizons-2, Rascom-QAF 1 Progress M-62 Kosmos 2434, Kosmos 2435, Kosmos 2436 Launches are separated by dots ( • ), payloads by commas ( , ), multiple names for the same satellite by slashes ( / ). Crewed flights are underlined. Launch failures are marked with the † sign. Payloads deployed from other spacecraft are (enclosed in parentheses). --- Adapted from the Wikipedia article [MidSTAR-1](https://en.wikipedia.org/wiki/MidSTAR-1) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/MidSTAR-1?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.