Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Space Comms”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

30 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Use of Data Comm by Flight Crew to Conduct Interval Management Operations to Parallel Dependent Runways

The Interval Management (IM) concept is being developed as a method to maintain or increase high traffic density airport arrival throughput while allowing aircraft to conduct near idle thrust descents. The Interval Management with Spacing to Parallel Dependent Runways (IMSPiDR1) experiment at NASA Langley Research Center used 24 commercial pilots to examine IM procedures to conduct parallel dependent runway arrival operations while maintaining safe but efficient intervals behind the preceding aircraft. The use of IM procedures during these operations requires a lengthy and complex clearance from Air Traffic Control (ATC) to the participating aircraft, thereby making the use of Controller Pilot Data Link Communications (CPDLC) highly desirable as the communication method. The use of CPDLC reduces the need for voice transmissions between controllers and flight crew, and enables automated transfer of IM clearance elements into flight management systems or other aircraft avionics. The result is reduced crew workload and an increase in the efficiency of crew procedures. This paper focuses on the subset of data collected related to the use of CPDLC for IM operations into a busy airport. Overall, the experiment and results were very successful, with the mean time under 43 seconds for the flight crew to load the clearance into the IM spacing tool, review the calculated speed, and respond to ATC. An overall mean rating of Moderately Agree was given when the crews were asked if the use of CPDLC was operationally acceptable as simulated in this experiment. Approximately half of the flight crew reported the use of CPDLC below 10,000 for IM operations was unacceptable, with 83% reporting below 5000 was unacceptable. Also described are proposed modifications to the IM operations that may reduce CPDLC Respond time to less than 30 seconds and should significantly reduce the complexity of crew procedures, as well as follow-on research issues for operational use of CPDLC during IM operations.

Baxley, Brian T.↗
NASA NTRS2016

My Internship at NASA

My name is Isaac Lopez and I am a junior at the University of Houston majoring in Mechanical Engineering Technology. I will be completing my first tour at the NASA-Johnson Space Center ("JSC") as a Mechanical Engineer within the Human Interfaces Branch. Throughout my tour, I was given the opportunity to work on multiple projects that have expanded my knowledge and interest in acoustics and engineering design. One of the projects I worked on at JSC consisted of doing acoustic simulation of the EVA comm. cap. While working on the comm. cap headset, my main duty consisted of simulating the acoustics of the headset to find a solution to the condensing water that can accumulate and block the acoustic tube, causing attenuation or complete loss of audio in one ear for an astronaut using the EVA. For this project, I had to create a Creo model of the comm. cap so that I would be able to import it into Comsol for acoustic simulation. I also had the opportunity to design a portable and lightweight beam degrader for the EEE Parts and Radiation team. With the help of Creo, I was able to make a CAD design and put together a small working prototype for the radiation team to demonstrate the capabilities that the beam degrader had. In addition to these projects, JSC allowed me to work closely on projects with other interns. I had the opportunity to help another intern with his acoustic diverter, intended to improve the sound quality in Node 1 of the ISS. During this project, I helped with some of the acoustic testing inside the anechoic chamber as well as helping record data during testing at the ISS mock up. During the course of my first tour, I was able to learn and continually improve on my CAD drafting skills. With each project I worked on, I acquired new ways to create and improve various designs with various constraints. Furthermore, I also had the opportunity to work with electrical engineers and learn about the electronic components that would provide control of the beam degrader functions. I was able to take the knowledge, skills and designs I had acquired during my tour at JSC (such as Finite Element Analysis) and apply them to my work on the Comsol Multiphysics software for acoustics simulation. I was also able to use it to do some stress analysis on a proposed design for a proposed Habitat structure. My time at JSC has been invaluable as it helped me grow and more fully-comprehend my major as well as spark an interest in acoustics and how much it relates to mechanical engineering. This internship has taught me that engineering is much more than a profession - it is embedded in our daily lives as a puzzle that requires critical thinking as an everyday challenge that makes life more interesting.

Lopez, Isaac↗
NASA NTRS2018

Orion Optical Navigation Progress Toward Exploration: Mission 1

Optical navigation of human spacecraft was proposed on Gemini and implemented successfully on Apollo as a means of autonomously operating the vehicle in the event of lost communication with controllers on Earth. It shares a history with the "method of lunar distances" that was used in the 18th century and gained some notoriety after its use by Captain James Cook during his 1768 Pacific voyage of the HMS Endeavor. The Orion emergency return system utilizing optical navigation has matured in design over the last several years, and is currently undergoing the final implementation and test phase in preparation for Exploration Mission 1 (EM-1) in 2019. The software development is being worked as a Government Furnished Equipment (GFE) project delivered as an application within the Core Flight Software of the Orion camera controller module. The mathematical formulation behind the initial ellipse fit in the image processing is detailed in Christian. The non-linear least squares refinement then follows the technique of Mortari as an estimation process of the planetary limb using the sigmoid function. The Orion optical navigation system uses a body fixed camera, a decision that was driven by mass and mechanism constraints. The general concept of operations involves a 2-hour pass once every 24 hours, with passes specifically placed before all maneuvers to supply accurate navigation information to guidance and targeting. The pass lengths are limited by thermal constraints on the vehicle since the OpNav attitude generally deviates from the thermally stable tail-to-sun attitude maintained during the rest of the orbit coast phase. Calibration is scheduled prior to every pass due to the unknown nature of thermal effects on the lens distortion and the mounting platform deformations between the camera and star trackers. The calibration technique is described in detail by Christian, et al. and simultaneously estimates the Brown-Conrady coefficients and the Star Tracker/Camera interlock angles. Accurate attitude information is provided by the star trackers during each pass. Figure 1 shows the various phases of lunar return navigation when the vehicle is in autonomous operation with lost ground communication. The midcourse maneuvers are placed to control the entry interface conditions to the desired corridor for safe landing. The general form of optical navigation on Orion is where still images of the Moon or Earth are processed to find the apparent angular diameter and centroid in the camera focal plane. This raw data is transformed into range and bearing angle measurements using planetary data and precise star tracker inertial attitude. The measurements are then sent to the main flight computer's Kalman filter to update the onboard state vector. The images are, of course, collected over an arc to converge the state and estimate velocity. The same basic technique was used by Apollo to satisfy loss-of-comm, but Apollo used manual crew sightings with a vehicle-integral sextant instead of autonomously processing optical imagery. The software development is past its Critical Design Review, and is progressing through test and certification for human rating. In support of this, a hardware-in-the-loop test rig was developed in the Johnson Space Center Electro-Optics Lab to exercise the OpNav system prior to integrated testing on the Orion vehicle. Figure 2 shows the rig, which the test team has dubbed OCILOT (Orion Camera In the Loop Optical Testbed). Analysis performed to date shows a delivery that satisfies an allowable entry corridor as shown in Figure 3.

Holt, Greg N.↗
NASA NTRSDate not supplied

Assessment of the State of Communication Delay Research in Preparation for Missions Beyond Low Earth Orbit

NASA’s mission-operations paradigm, established during Project Mercury and minimally evolving through the Apollo Program, Space Shuttle Program, and ISS missions, has primarily depended on real-time support from a ground team of experts. This ground team has served as the safety net for crewed spaceflight missions over the past 60 years, managing the combined state of the mission, vehicle, and crew. However, this operational paradigm, which has seen little change in its Human-Systems Integration Architecture (HSIA), will face challenges during long-duration exploration missions beyond low Earth orbit. Lunar missions may experience one-way communication latencies ranging from 3 to 14 seconds, while Mars missions will encounter up to a 44-minute round-trip latency at a maximum distance from Earth. Communication delays negatively impact the behavioral health and performance of individuals and crews operating across the multi-team space-to-ground system. Previous research indicates that increased isolation and the challenges posed by delayed communication lead to heightened stress, frustration, adverse behavioral symptoms, and reduced individual performance. NASA has investigated the nature and effectiveness of managing this shift in complex operations since early 2000, but additional research is necessary to assess the issues associated with communication latencies and identify effective countermeasures. This work aimed to examine the evidence from 20 years of research on comm delays. We systematically reviewed the past 20 years of communication delay literature, focusing on how this research aligns with relevant, high-priority needs in the HSIA, Team, and BMed Risks. This type of panoramic review has not been done since 2013; a current, aggregated picture of what has been studied and how is needed to inform additional studies and mitigation development. Additional perspectives were gained from interviews with the research participants, operations experts, and communication delay researchers. Results from this effort will help characterize the risk posed by communication latency for upcoming Artemis missions and point toward potential mitigations. The final results will be presented. For the literature review, we formed a search term seed set drawing from languages used in two papers representative of the previous state of knowledge and supplemented it with additional search terms. We conducted literature searches on Google Scholar, PubMed, and Web of Science and searched NASA project archives for output from NASA-sponsored research. This search yielded 150 papers, of which 48 were relevant. SME interviews provided perspective on key communication delay issues and concerns and what is being worked on to mitigate those issues. Preliminary results of the literature review have been presented. Final results to be presented include the results of the literature review and findings from the interviews.

literature review↗
NASA NTRS1995

Aeronautical Satellite Data Link System (SDLS) for high-density air-traffic areas

The European Space Agency has recently commissioned a study to investigate the feasibility of a low-cost aeronautical Satellite Data Link System (SDLS) to provide for the needs of Air Traffic Services, i.e. safety related communications over continental areas with high air-traffic density. This study is placed in today's context which sees the first generation of Aeronautical Mobile Satellite System (AMSS) being gradually but restrictively put into service in oceanic airspaces with low air-traffic density. This paper first discusses the case of ATS dedicated versus mixed (ATS and commercial) Comms service provision and identifies the specific ATS comms requirements context. Specific emphasis is put on the ICAO (International Civil Aviation Organization) standardization framework for both the ATN (Aeronautical Telecommunication Network) and the SSR (Secondary Surveillance Radar) Mode S specific services. An architectural system and network design for a future SDLS is then proposed, such as to meet the ATS comms requirements within the realm of existing technologies. To minimize development risk and cost, consideration is given to re-use the ESA-developed Land Mobile Communication Technology, known as MSBN (Mobile Satellite Business Network) featuring distinct subnetworks. It is particularly suited to an ATM (Air Traffic Management) decentralized architecture made of independent ATC (Air Traffic Control) Centers. Finally the study follow-on phase is introduced, which is intended to cover system design and development leading to a demonstration program, as a first step towards proposals for international standardization and acceptance.

Alain Delrieu↗
NASA NTRS1989

Petite Amateur Navy Satellite (PANSAT)

The Naval Postgraduate School's (NPS) Space Systems Academic Group (SSAG) is designing and developing a small communications satellite for launch aboard the shuttle as a complex autonomous payload (CAP). The objectives of PANSAT are three-fold. First, PANSAT will provide an ideal educational tool for the officer students at NPS supporting Space Systems Engineering and Space Systems Operations with hands-on hardware development. Second, the satellite will provide digital store-and-forward communications, or packet radio, for the amateur radio community. The third objective is to provide a low-cost, space-based platform for small experiments. PANSAT will be launched from the shuttle at a nominal altitude of 200 n.m. and an inclination of at least 37 degrees. The satellite weight is 150 lbs. Since there is no attitude control, eight dipole whip antennas will be used to provide isotropic ground coverage for communications. FM digital communications will be used with up-link and down-link on a single frequency in the amateur band of 437.25 MHz. A maximum 50 kHz of bandwidth is envisioned for the satellite. The expected lifetime of the satellite is 1 1/2 to 2 years before atmospheric reentry. The PANSAT design consists of the following: communications subsystem (COMM); computer, or data processor and sequencer (DP&S); power subsystem; structure subsystem; and experiment payload.

Sakoda, D.↗
NASA NTRSDate not supplied

Rapid Spacecraft Payload Development: In-Orbit Demonstration of Flight Software Reuse, Scalability, and Dependability

As space mission design trends towards shared, multi-mission platforms and high-performance onboard computing architectures, the number of spacecraft launched into operation is also steadily rising. Through ridesharing, spacecraft miniaturization, and other cost-reduction measures, the barriers to space are lowering, resulting in compounded growth in the amount of flight software being deployed. To meet the needs of both the growing quantity and evolving nature of spacecraft, flight software design must accordingly adapt to support more efficient development, solutions to computational resource-sharing, and software reusability. This paper focuses on a software payload demonstrating several core technologies that improve the state-of-the-art in these identified areas. Launched into low-earth orbit in January 2022, our software payload was conceived, designed, and delivered in a span of merely two months. It was developed on top of the NASA core Flight System (cFS) framework and the Distributed Spacecraft Autonomy (DSA) Comm cFS application, which translates cFS software bus messages across a Data Distribution Service (DDS) network. The flight software, packaged in Linux container images, was deployed as one of 18 flight applications managed through the Unibap SpaceCloud Framework. The applications were run on a Unibap iX5-102 radiation-tolerant payload computer, hosted on the D-Orbit SCV-004 spacecraft as part of an ESA-sponsored in-orbit technology test. Our payload, referred to as the DSA D-Orbit software, demonstrates the reusability of the DSA Comm app in a substantially different context and purpose as its original mission. Comm’s original design goal was to reliably distribute messages between spacecraft swarms of arbitrary size and dynamic network topology. However, we leverage this same functionality to introduce redundancy and opportunistic parallel data processing in the context of a representative onboard image processing workload. This adaptive mission architecture was enabled in part by the SpaceCloud Framework’s use of container virtualization as the payload integration interface. By using a base container image with common high-level language runtimes and libraries, we were able to rapidly design, develop, and validate our image processing application without many of the technological barriers common to flight software development. We present details the goals, approach, results, and lessons learned through this technology demonstration experiment and contextualize those observations against present and future challenges in spacecraft software development.

computer programming↗
NASA NTRS2011

Trajectory Assessment and Modification Tools for Next Generation Air Traffic Management Operations

This paper reviews three Next Generation Air Transportation System (NextGen) based high fidelity air traffic control human-in-the-loop (HITL) simulations, with a focus on the expected requirement of enhanced automated trajectory assessment and modification tools to support future air traffic flow management (ATFM) planning positions. The simulations were conducted at the National Aeronautics and Space Administration (NASA) Ames Research Centers Airspace Operations Laboratory (AOL) in 2009 and 2010. The test airspace for all three simulations assumed the mid-term NextGenEn-Route high altitude environment utilizing high altitude sectors from the Kansas City and Memphis Air Route Traffic Control Centers. Trajectory assessment, modification and coordination decision support tools were developed at the AOL in order to perform future ATFM tasks. Overall tool usage results and user acceptability ratings were collected across three areas of NextGen operatoins to evaluate the tools. In addition to the usefulness and usability feedback, feasibility issues, benefits, and future requirements were also addressed. Overall, the tool sets were rated very useful and usable, and many elements of the tools received high scores and were used frequently and successfully. Tool utilization results in all three HITLs showed both user and system benefits including better airspace throughput, reduced controller workload, and highly effective communication protocols in both full Data Comm and mixed-equipage environments.

Brasil, Connie↗
NASA NTRS2016

NEEMO 18-20: Analog Testing for Mitigation of Communication Latency During Human Space Exploration

NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission-like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014-2015, NEEMO's 18-20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of communication latencies on operations concepts, timelines, and tasks were studied. METHODS: Twelve subjects (4 per mission) were weighed out to simulate near-zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth-based science team (ST) to provide input and direction during exploration activities. Exploration traverses were preplanned based on precursor data. Subjects completed science-related tasks including pre-sampling surveys, geologic-based sampling, and marine-based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were designed to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One-way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, ST assimilation time (defined as time available for ST to discuss data/imagery after data acquisition). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high-fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for pre-sampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across communication latencies and can be done with minimal crew idle time. Imagery and contextual information from the EVA crew that is transmitted real-time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide meaningful feedback and instruction to the crew regarding sampling priorities, additional tasks, and changes to the EVA timeline. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency.

Chappell, Steven P.↗
NASA NTRS2016

Analog Testing of Operations Concepts for Mitigation of Communication Latency During Human Space Exploration

OBJECTIVES: NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission‐like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014‐2015, NEEMO's 18‐20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of varying operations concepts and tasks type and complexity on representative communication latencies associated with Mars missions were studied. METHODS: 12 subjects (4 per mission) were weighed out to simulate near‐zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth‐based science backroom team (SBT) to provide input and direction during exploration activities. Exploration traverses were planned in advance based on precursor data collected. Subjects completed science‐related tasks including presampling surveys, geologic‐based sampling, and marine‐based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One‐way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, SBT assimilation time (defined as time available for SBT to discuss data/imagery after it has been collected, in addition to the time taken to watch imagery streaming over latency). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high‐fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for presampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across long communication latencies and can be done with minimal crew idle time. Imagery and information from the EVA crew that is transmitted real‐time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide further instructions to the crew from a SBT on sampling priorities, additional tasks, and changes to the plan. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency. Autonomous crew planning tools can be effective at modifying existing plans if the objectives and constraints are clearly defined.

Chappell, Steven P.↗
NASA NTRS2020

Design and Implementation of a Scenario Development Process for a 2040 Trajectory-Based Operations Simulation

The National Aeronautics and Space Administration (NASA) is supporting research to transition from a legacy, air traffic management (ATM) system to Trajectory-Based Operations (TBO) environment targeting the 2035-2045 timeframe by creating simulation scenarios for current and future studies. TBO in the National Airspace System (NAS) focuses on modernizing the current operating paradigm to increase efficiency, predictability, resilience, and flexibility while migrating toward greater operational autonomy across the airspace. These simulation scenarios offer a wide dissemination and use of system-level constraints and aircraft state/intent data, routine use of data communications to request complex trajectory modifications and to receive clearances, and aircraft that are flying on 4-D trajectories with flexibility when desired, but structure where required. This report describes the end-to-end development of scenarios for the NASA Langley Research Center simulation environment to represent a 2040 Trajectory-Based Operations airspace for air transport operations research.

Trajectory-Based Operations↗
NASA NTRSDate not supplied

A Notional Artemis Lunar Surface Exploration Package (ArLSEP) based on the Gandalf Staff Platform

Introduction: The Artemis program is planning to deliver crew and cargo to the lunar surface, but there is no current package for supporting lunar in-struments and experiments similar to the Apollo Lunar Surface Exploration Package (ALSEP). This abstract provides a possible concept for such a package using the Gandalf Staff Platform as a common core. Gandalf Staff: The Gandalf Staff is an early prototype system developed over FY’21/FY’22 using NASA Science Technology Mission Directorate (STMD) Center Information Fund (CIF) grants to de-sign, build and test “proof-of-concept” components. These components include a 24v battery powered monopole that powers a suite of subsystems, including a Graphical User Interface (GUI) for crew, surface voice and data communications, Lunar Search and Rescue (LunaSAR) navigation and communications, LiDAR, field site external lighting, 360-degree camera, and a geothermal instrument for measuring sub-surface temperature gradient. The staff can be carried independently by an Extra-Vehicular Activity (EVA) astronaut, or can be mounted into a tripod for “hands free” support at a surface site being investigated. The staff can be attached to an external solar array and power storage system for long-duration operations. [1,2] ALSEP: An ASLEP flew on each mission Apollo 12 to Apollo 17. For Apollo 11, a simplified packaged called the Early Apollo Scientific Experiments Pack-age (EASEP) was flown. Each package included a “Central Station” that provided the power and communications connected to a variety of instruments and sensors. The power was provided by a Radioisotope Thermoelectric Generator (RTG) fueled by Plutoni-um-238 generating 70 watts of power (initially, decayed over time) [3]. The communications system provide for direct to Earth data transfer from the lunar surface. Each pack-age was stowed externally in the Lunar Module (LM) Scientific Equipment (SEQ) bay with a mass up to 163 kg (Apollo 17). The crew unloaded the ALSEP from the LM and deployed the instruments on the lunar surface. Although designed to operate for only 1 year, many sites operated for up to 8 years successfully [4]. The Active Seismic Experiment (ASE) included 3 geophones for detecting seismic waves created by mortars and thumpers deployed by the crew. Other active experiments measured the lunar atmosphere, the heat flow in the subsurface, the lunar gravity and potential gravity waves, the lunar magnetic field, the solar wind and plasma interactions in cislunar space. Passive experiments included collectors for dust and cosmic rays, and retroreflectors for precise measurements of distance using a laser from Earth. The ALSEP program continues to generate insights into lunar formation and evolution. ArLSEP Concepts: The lunar surface science package for the Artemis program will hopefully exceed the capability of the ALSEP. There are multiple issues for discussion leading to the design of a new ArLSEP, needing requirements definition from the science community, NASA mission architecture, and NASA budget planners. 1. Delivery Mechanism Two possible projects currently provide capability to deliver scientific cargo to the lunar surface: 1) the Commercial Lunar Payload Services (CLPS) [5] and the Human Landing System (HLS) [6, 7]. Each project is controlled by a different organization within NASA and budgeted with different criteria although both support lunar exploration. The HLS system delivers crew (and potentially cargo) to human landing sites. If an ArLSEP is “predeployed” to such a site, the design must include power (either from the vehicle or independently) to keep the electronics functioning until deployed by the crew. If an ArLSEP is delivered on a vehicle after the crew is present on the lunar surface, safety protocols require adequate distance from the humans for impact from descent propelled sur-face regolith ejecta. This distance can not exceed the capability of the crew to walk (if no rover) to the vehicle for ArLSEP deployment. 2. Overall Guidelines The general design of ArLSEP will likely follow the ALSEP with a common system for communications and power; however, significant architecture differences between Apollo and Artemis exist. Power: The RTG will not be available for early Artemis missions nor likely follow-on Lunar Exploration Transportation Services (LETS) missions [8]. Thus, ArLSEP power must be supplied by solar arrays with sufficient battery capability to “keep alive” necessary electronics during any lunar surface eclipse period. Communication: The Artemis program is developing a series of communications satellites for lunar orbit to provide surface transmission of data and voice to Earth. Called “LunaNET”, this network is component useful for ArLSEP since south polar locations may not always have direct “line-of-sight” to Earth [9]. 3. Concept of Operations (ConOps) The general ConOps for ArLSEP is to deliver the package to lunar surface before the crew arrives, and then have the crew deploy the package after some period of time. This requires coordinated design (for power systems) and launch window (for schedule) on both the cargo and crew missions. Once the ArLSEP is deployed, it will operate autonomously for a number of years. It should be designed to be EVA compatible for crew maintenance and upgrade. 4. Notional Design (for discussion purpose only) The landing site near the South Pole is expected to have no eclipse cycle exceeding 5 days, so the “keep alive” power is 144 hours (6 days to include margin). A 12v ArLSEP will use rechargeable LiFePO4 cells, which are common in the Electric Vehicle (EV) industry. With a current of 5 amps and a 125 watt system, the mass is about 90kg. The comm. system and structure adds another 10kg, thus the “Central Station” is approximately 100kg. The solar power is collected on four arrays (each 2m above the surface), and the entire ArLSEP is designed to stow in a 2m x 1m x 1m volume. The experiment and instrument design will vary for each installation and add mass to the total (although they are expected to fit within the 2m3 volume). Seismic wave generation will likely not be provided with mortars, thus an electric “thumper” will be required. Active instruments such as imaging systems and sensing instruments will benefit from the additional power and communication capability provided by ArLSEP. Passive systems such as retroreflectors, witness plates, and cosmic dust collectors can be added to either the landing vehicle and/or the ArLSEP. With repeated HLS missions to the same human site, the ArLSEP can be expanded and easily maintained for long duration science collection on the lunar surface.

ALSEP↗