Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “SCCS”

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.

At least 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Developing a Model Component

The Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI) is responsible for providing simulations to support test and verification of SCCS hardware and software. The Universal Coolant Transporter System (UCTS) was a Space Shuttle Orbiter support piece of the Ground Servicing Equipment (GSE). The initial purpose of the UCTS was to provide two support services to the Space Shuttle Orbiter immediately after landing at the Shuttle Landing Facility. The UCTS is designed with the capability of servicing future space vehicles; including all Space Station Requirements necessary for the MPLM Modules. The Simulation uses GSE Models to stand in for the actual systems to support testing of SCCS systems during their development. As an intern at Kennedy Space Center (KSC), my assignment was to develop a model component for the UCTS. I was given a fluid component (dryer) to model in Simulink. I completed training for UNIX and Simulink. The dryer is a Catch All replaceable core type filter-dryer. The filter-dryer provides maximum protection for the thermostatic expansion valve and solenoid valve from dirt that may be in the system. The filter-dryer also protects the valves from freezing up. I researched fluid dynamics to understand the function of my component. The filter-dryer was modeled by determining affects it has on the pressure and velocity of the system. I used Bernoulli's Equation to calculate the pressure and velocity differential through the dryer. I created my filter-dryer model in Simulink and wrote the test script to test the component. I completed component testing and captured test data. The finalized model was sent for peer review for any improvements. I participated in Simulation meetings and was involved in the subsystem design process and team collaborations. I gained valuable work experience and insight into a career path as an engineer.

Fields, Christina M.↗
NASA NTRS2013

Developing a Model Component

The Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI) is,. responsible for providing simulations to support test and verification of SCCS hardware and software. The Universal Coolant Transporter System (UCTS) is a Space Shuttle Orbiter support piece of the Ground Servicing Equipment (GSE). The purpose of the UCTS is to provide two support services to the Space Shuttle Orbiter immediately after landing at the Shuttle Landing Facility. The Simulation uses GSE Models to stand in for the actual systems to support testing of SCCS systems s:luring their development. As an intern at KSC, my assignment was to develop a model component for the UCTS. I was given a fluid component (drier) to model in Matlab. The drier was a Catch All replaceable core type filter-drier. The filter-drier provides maximum protection for the thermostatic expansion valve and solenoid valve from dirt that may be in the system. The filter-drier also protects the valves from freezing up. I researched fluid dynamics to understand the function of my component. I completed training for UNIX and Simulink to help aid in my assignment. The filter-drier was modeled by determining affects it has on the pressure, velocity and temperature of the system. I used Bernoulli's Equation to calculate the pressure and velocity differential through the dryer. I created my model filter-drier in Simulink and wrote the test script to test the component. I completed component testing and captured test data. The finalized model was sent for peer review for any improvements.

Fields, Christina M.↗
NASA NTRS2013

SMC Message Browser Projects

I work directly with the System Monitoring and Control (SMC) software engineers who develop, test and release custom and commercial software in support of the Kennedy Space Center Spaceport Command and Control System. (SCCS). SMC uses Commercial Off-The-Shelf (COTS) Enterprise Management Systems (EMS) software which provides a centralized subsystem for configuring, monitoring, and controlling SCCS hardware and software used in the Control Rooms. There are multiple projects being worked on using the COTS EMS software. I am currently working with the HP Operations Manager for UNIX (OMU) software which allows Master Console Operators (MCO) to access, view and interpret messages regarding the status of the SCCS hardware and software. The OMU message browser gets cluttered with messages which can make it difficult for the MCO to manage. My main project involves determining ways to reduce the number of messages being displayed in the OMU message browser. I plan to accomplish this task in two different ways: (1) by correlating multiple messages into one single message being displayed and (2) to create policies that will determine the significance of each message and whether or not it needs to be displayed to the MCO. The core idea is to lessen the number of messages being sent to the OMU message browser so the MCO can more effectively use it.

OMU↗
NASA NTRS2014

Upgrading Custom Simulink Library Components for Use in Newer Versions of Matlab

The Spaceport Command and Control System (SCCS) at Kennedy Space Center (KSC) is a control system for monitoring and launching manned launch vehicles. Simulations of ground support equipment (GSE) and the launch vehicle systems are required throughout the life cycle of SCCS to test software, hardware, and procedures to train the launch team. The simulations of the GSE at the launch site in conjunction with off-line processing locations are developed using Simulink, a piece of Commercial Off-The-Shelf (COTS) software. The simulations that are built are then converted into code and ran in a simulation engine called Trick, a Government off-the-shelf (GOTS) piece of software developed by NASA. In the world of hardware and software, it is not uncommon to see the products that are utilized be upgraded and patched or eventually fade away into an obsolete status. In the case of SCCS simulation software, Matlab, a MathWorks product, has released a number of stable versions of Simulink since the deployment of the software on the Development Work Stations in the Linux environment (DWLs). The upgraded versions of Simulink has introduced a number of new tools and resources that, if utilized fully and correctly, will save time and resources during the overall development of the GSE simulation and its correlating documentation. Unfortunately, simply importing the already built simulations into the new Matlab environment will not suffice as it will produce results that may not be expected as they were in the version that is currently being utilized. Thus, an upgrade execution plan was developed and executed to fully upgrade the simulation environment to one of the latest versions of Matlab.

Matlab Simulation↗
NASA NTRS2014

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗
NASA NTRS2018

Spaceport Command and Control System: Network Engineering

The Spaceport Command and Control System (SCCS) project's goal is to facilitate the checkout and launch of NASA's next generation SLS vehicle in order to enable human exploration through deep space. SCCS is made up of complex software that will control and monitor the Space Launch System rocket and Orion spacecraft. Once it is fully developed, SCCS will be a large improvement to previous software since it takes advantage of modern computers and information making it faster and more reliable than the software used previously on the Shuttle program. The software will be tailored to the specific needs of the Space Launch System (SLS) and Orion spacecraft. These three projects will be brought together for the launch of Exploration Mission-1.

Mackh, Katherine↗
NASA NTRS2018

Launch Control System / Spaceport Command and Control

NASA is developing the next generation launch vehicle that will take astronauts further into space than any previous manned vehicle. This project has many facets and one of them, the Spaceport Command and Control System (SCCS), was the primary focus of my work during this internship. A vital ability of SCCS is the communication from the firing rooms to the ground support equipment for the vehicle on the launch pad. During this internship, I was part of the Computer Systems Hardware Team, a group of engineers who handle the computer and networking aspects of the SCCS project. My job was to construct, handle, and test computer and network machines, configurations and cables.

Barbaro, Mark A.↗
NASA NTRS2019

Launch Control System / Spaceport Command and Control System

National Aeronautics and Space Administration (NASA) is currently developing the next generation launch vehicle that will take American astronauts, from American soil, even further into space. Our project for this semester dealt with the Spaceport Command and Control System (SCCS). SCCS provides a means of communication between the Firing Rooms and ground support equipment for the vehicle on the launch pad. For this internship, we became part of the Computer Systems Hardware Team. This team of engineers handle the computer and networking aspects of SCCS. During this internship, we learned about Linux operating systems and network configuration.

Ferrell, Sean P.↗
NASA NTRSDate not supplied

Updated Analysis of the Trash Compaction and Processing System: Water Collected from Trash, Evaluation of the Source Contaminant Control System, and Zotek® F30 Foam Processing

The Trash Compaction and Processing System (TCPS) aims to reduce volume, biologically safen, physically stabilize, manage effluents, and recover resources from astronaut trash in the International Space Station (ISS). At NASA Ames Research Center (ARC), there are two test systems: the Heat Melt Compactor (HMC), which compacts the trash into a tile with temperature and pressure, and the Source Contaminant Control System (SCCS), which is the gas management subsystem aimed to reduce contaminants by converting them into carbon dioxide (CO 2 ) and water (H 2 O) vapor. Both the HMC and SCCS serve as test systems that support TCPS development by conducting risk reduction activities associated with an ISS technology demonstration. In this paper, the risk reduction activities discussed are the testing of different trash models for operational scenarios in the HMC, investigating the water extracted from those trash models, and managing the gaseous effluents from the trash via contaminant conversion through the SCCS. The HMC has undergone several tests of different trash models and cases in which a containment bag is used or not. For the first topic, this paper will analyze the water collected and recovered from these tests and analyze the effect of specific trash containment bags. For the second topic, this paper will individually evaluate the carbon bed and catalytic oxidizer (CatOx) to understand what components the carbon bed removes and what contaminants are converted in the CatOx. For the third and final topic, this paper will discuss Zotek® F30 foam processing in the HMC unit and testing verification in correlation to defined TCPS requirements. A foam model was added to reduce the volume of foam that take up space in the ISS. Overall, this paper is a compilation and an updated analysis of tests conducted in the lab-scale TCPS at ARC within the past year.

TCPS↗
NASA NTRS2017

Launch Control System Software Development System Automation Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This system requires high quality testing that will measure and test the capabilities of the system. For the past two years, the Exploration and Operations Division at Kennedy Space Center (KSC) has assigned a group including interns and full-time engineers to develop automated tests to save the project time and money. The team worked on automating the testing process for the SCCS GUI that would use streamed simulated data from the testing servers to produce data, plots, statuses, etc. to the GUI. The software used to develop automated tests included an automated testing framework and an automation library. The automated testing framework has a tabular-style syntax, which means the functionality of a line of code must have the appropriate number of tabs for the line to function as intended. The header section contains either paths to custom resources or the names of libraries being used. The automation library contains functionality to automate anything that appears on a desired screen with the use of image recognition software to detect and control GUI components. The data section contains any data values strictly created for the current testing file. The body section holds the tests that are being run. The function section can include any number of functions that may be used by the current testing file or any other file that resources it. The resources and body section are required for all test files; the data and function sections can be left empty if the data values and functions being used are from a resourced library or another file. To help equip the automation team with better tools, the Project Lead of the Automated Testing Team, Jason Kapusta, assigned the task to install and train an optical character recognition (OCR) tool to Brandon Echols, a fellow intern, and I. The purpose of the OCR tool is to analyze an image and find the coordinates of any group of text. Some issues that arose while installing the OCR tool included the absence of certain libraries needed to train the tool and an outdated software version. We eventually resolved the issues and successfully installed the OCR tool. Training the tool required many images and different fonts and sizes, but in the end the tool learned to accurately decipher the text in the images and their coordinates. The OCR tool produced a file that contained significant metadata for each section of text, but only the text and coordinates of the text was required for our purpose. The team made a script to parse the information we wanted from the OCR file to a different file that would be used by automation functions within the automated framework. Since a majority of development and testing for the automated test cases for the GUI in question has been done using live simulated data on the workstations at the Launch Control Center (LCC), a large amount of progress has been made. As of this writing, about 60% of all of automated testing has been implemented. Additionally, the OCR tool will help make our automated tests more robust due to the tool's text recognition being highly scalable to different text fonts and text sizes. Soon we will have the whole test system automated, allowing for more full-time engineers working on development projects.

Automation↗
DOE OSTI2022

Trends in HPV- and non-HPV-associated vulvar cancer incidence, United States, 2001–2017

Vulvar cancer incidence has been rising in recent years, possibly due to increasing exposure to human papillomavirus (HPV). We assessed incidence rates of HPV-associated and non-HPV-associated vulvar cancers diagnosed from 2001 to 2017 in the United States (US). Using population-based cancer registry data covering 99% of the US population, incidence rates were calculated and stratified by age, race/ethnicity, stage, geographic region, and histology. The average annual percent change in incidence per year were calculated using joinpoint regression. From 2001 to 2017, the incidence of HPV-associated vulvar cancers increased by 1.2% per year, most notably among women who were aged 50–59 years (2.6%), 60–69 years (2.4%), and ≥ 70 years (0.9%); of White (1.5%) and Black (1.1%) race; diagnosed at an early (1.3%) and late (1.8%) stage; and living in the Midwest (1.9%), Northeast (1.4%), and South (1.2%). Incidence increased each year for HPV-associated histologic subtypes including keratinizing (4.7%), non-keratinizing (6.0%), and basaloid (3.1%) squamous cell carcinomas (SCCs), while decreases were found in warty (2.7%) and microinvasive (5.5%) SCCs. HPV-associated vulvar cancer incidence increased overall and among women aged over 50 years while remaining stable among women younger than 50 years. Furthermore, the overall incidence for non-HPV-associated cancers was stable. Continued surveillance of HPV-associated cancers will allow us to monitor future trends as HPV vaccination coverage increases in the US.

60 APPLIED LIFE SCIENCES↗
DOE OSTI2024

The association between neighborhood obesogenic factors and prostate cancer risk and mortality: the Southern Community Cohort Study

Background: Prostate cancer is one of the leading causes of cancer-related mortality among men in the United States. We examined the role of neighborhood obesogenic attributes on prostate cancer risk and mortality in the Southern Community Cohort Study (SCCS). Methods: From the total of 34,166 SCCS male participants, 28,356 were included in the analysis. We assessed the relationship between neighborhood obesogenic factors [neighborhood socioeconomic status (nSES) and neighborhood obesogenic environment indices including the restaurant environment index, the retail food environment index, parks, recreational facilities, and businesses] and prostate cancer risk and mortality by controlling for individual-level factors using a multivariable Cox proportional hazards model. We further stratified prostate cancer risk analysis by race and body mass index (BMI). Results: Median follow-up time was 133 months [interquartile range (IQR): 103, 152], and the mean age was 51.62 (SD: ± 8.42) years. There were 1,524 (5.37%) prostate cancer diagnoses and 98 (6.43%) prostate cancer deaths during follow-up. Compared to participants residing in the wealthiest quintile, those residing in the poorest quintile had a higher risk of prostate cancer (aHR = 1.32, 95% CI 1.12–1.57, p = 0.001), particularly among non-obese men with a BMI < 30 (aHR = 1.46, 95% CI 1.07–1.98, p = 0.016). The restaurant environment index was associated with a higher prostate cancer risk in overweight (BMI ≥ 25) White men (aHR = 3.37, 95% CI 1.04–10.94, p = 0.043, quintile 1 vs. None). Obese Black individuals without any neighborhood recreational facilities had a 42% higher risk (aHR = 1.42, 95% CI 1.04–1.94, p = 0.026) compared to those with any access. Compared to residents in the wealthiest quintile and most walkable area, those residing within the poorest quintile (aHR = 3.43, 95% CI 1.54–7.64, p = 0.003) or the least walkable area (aHR = 3.45, 95% CI 1.22–9.78, p = 0.020) had a higher risk of prostate cancer death. Conclusion: Living in a lower-nSES area was associated with a higher prostate cancer risk, particularly among Black men. Restaurant and retail food environment indices were also associated with a higher prostate cancer risk, with stronger associations within overweight White individuals. Finally, residing in a low-SES neighborhood or the least walkable areas were associated with a higher risk of prostate cancer mortality.

60 APPLIED LIFE SCIENCES↗
NASA NTRS1984

The development of a microprocessor-controlled linearly-actuated valve assembly

The development of a proportional fluid control valve assembly is presented. This electromechanical system is needed for space applications to replace the current proportional flow controllers. The flow is controlled by a microprocessor system that monitors the control parameters of upstream pressure and requested volumetric flow rate. The microprocessor achieves the proper valve stem displacement by means of a digital linear actuator. A linear displacement sensor is used to measure the valve stem position. This displacement is monitored by the microprocessor system as a feedback signal to close the control loop. With an upstream pressure between 15 and 47 psig, the developed system operates between 779 standard CU cm/sec (SCCS) and 1543 SCCS.

Wall, R. H.↗
NASA NTRS2011

An Evaluation of Ultra-High Pressure Regulator for Robotic Lunar Landing Spacecraft

The Robotic Lunar Lander Development (RLLD) Project Office at NASA Marshall Space Flight Center (MSFC) has studied several lunar surface science mission concepts. These missions focus on spacecraft carrying multiple science instruments and power systems that will allow extended operations on the lunar surface. Initial trade studies of launch vehicle options for these mission concepts indicate that the spacecraft design will be significantly mass-constrained. To minimize mass and facilitate efficient packaging, the notional propulsion system for these landers has a baseline of an ultra-high pressure (10,000 psig) helium pressurization system that has been used on Defense missiles. The qualified regulator is capable of short duration use; however, the hardware has not been previously tested at NASA spacecraft requirements with longer duration. Hence, technical risks exist in using this missile-based propulsion component for spacecraft applications. A 10,000-psig helium pressure regulator test activity is being carried out as part of risk reduction testing for MSFC RLLD project. The goal of the test activity is to assess the feasibility of commercial off-the-shelf ultra-high pressure regulator by testing with a representative flight mission profile. Slam-start, gas blowdown, water expulsion, lock-up, and leak tests are also performed on the regulator to assess performance under various operating conditions. The preliminary test results indicated that the regulator can regulate helium to a stable outlet pressure of 740 psig within the +/- 5% tolerance band and maintain a lock-up pressure less than +5% for all tests conducted. Numerous leak tests demonstrated leakage less than 10-3 standard cubic centimeters per second (SCCS) for internal seat leakage at lock-up and less than10-5 SCCS for external leakage through the regulator ambient reference cavity. The successful tests have shown the potential for 10,000 psig helium systems in NASA spacecraft and have reduced risk associated with hardware availability and hardware ability to meet RLL mission requirements.

Burnside, Christopher↗
NASA NTRS2013

An Evaluation of a High Pressure Regulator for NASA's Robotic Lunar Lander Spacecraft

The Robotic Lunar Lander (RLL) development project office at NASA Marshall Space Flight Center is currently studying several lunar surface science mission concepts. The focus is on spacecraft carrying multiple science instruments and power systems that will allow extended operations on the lunar surface or other air-less bodies in the solar system. Initial trade studies of launch vehicle options indicate the spacecraft will be significantly mass and volume constrained. Because of the investment by the DOD in low mass, highly volume efficient components, NASA has investigated the potential integration of some of these technologies in space science applications. A 10,000 psig helium pressure regulator test activity has been conducted as part of the overall risk reduction testing for the RLL spacecraft. The regulator was subjected to typical NASA acceptance testing to assess the regulator response to the expected RLL mission requirements. The test results show the regulator can supply helium at a stable outlet pressure of 740 psig within a +/- 5% tolerance band and maintain a lock-up pressure less than the +5% above nominal outlet pressure for all tests conducted. Numerous leak tests demonstrated leakage less than 10-3 standard cubic centimeters per second (SCCS) for the internal seat leakage at lock-up and less than 10-5 SCCS for external leakage through the regulator body. The successful test has shown the potential for 10,000 psig helium systems in NASA spacecraft and has reduced risk associated with hardware availability and hardware ability to meet RLL mission requirements.

Burnside, Christopher G.↗
NASA NTRS2013

Personnel Data Analysis and Retrieval of Phase 1 Move To LC-39 Area

As a technology major from Jackson State University (JSU) I was called in as a summer intern at Kennedy Space Center (KSC) to work in the NASA Engineering, Control and Data Systems (NE-C) Division supporting the Spaceport Command and Control System (SCCS) at the Space Station Processing Facility (SSPF). I was given a two-part project; the first consisted of lending support relocating SCCS Computer Equipment and Project Personnel to the Launch Control Center (LCC). This task involved me using a Microsoft Office data processing tool to assist with the analysis and information management of logistics worth millions of dollars. With the assistance of two other interns, I was responsible for collecting data on equipment used, on a daily basis, by over 200 KSC employees. The many network servers, enterprise switches, desktop computers, and fiber optics had to be handled in an equally prompt and precise manner in order to ensure a minimal amount of equipment down time; which is critical in ensuring a properly secured networking environment. The second part of my project was to assist KSC in developing a more cost effective way of maintaining and taking full advantage of the functionality of some new kiosk units. Since KSC currently has no expert on the servicing and maintenance of the units, I, as a computer technology major, was given the opportunity to assess the hardware and software of the machines. The goal was to learn to establish a secure and remote environment for the kiosks; a goal highly valuing convenience by preserving valuable man-hours saved by not having to travel to each individual kiosk location. In addition, I was to leave a clear and precise plan for future users and administrators of the devices to follow.

Davis, Derrick D.↗
NASA NTRS2013

Small Radioisotope Power System Testing at NASA Glenn Research Center

In April 2009, NASA Glenn Research Center (GRC) formed an integrated product team (IPT) to develop a Small Radioisotope Power System (SRPS) utilizing a single Advanced Stirling Convertor (ASC) with passive balancer. A single ASC produces approximately 80 We making this system advantageous for small distributed lunar science stations. The IPT consists of Sunpower, Inc., to provide the single ASC with a passive balancer, The Johns Hopkins University Applied Physics Laboratory (JHUAPL) to design an engineering model Single Convertor Controller (SCC) for an ASC with a passive balancer, and NASA GRC to provide technical support to these tasks and to develop a simulated lunar lander test stand. The single ASC with a passive balancer, simulated lunar lander test stand, and SCC were delivered to GRC and were tested as a system. The testing sequence at GRC included SCC fault tolerance, integration, electromagnetic interference (EMI), vibration, and extended operation testing. The SCC fault tolerance test characterized the SCCs ability to handle various fault conditions, including high or low bus power consumption, total open load or short circuit, and replacing a failed SCC card while the backup maintains control of the ASC. The integrated test characterized the behavior of the system across a range of operating conditions, including variations in cold-end temperature and piston amplitude, including the emitted vibration to both the sensors on the lunar lander and the lunar surface. The EMI test characterized the AC and DC magnetic and electric fields emitted by the SCC and single ASC. The vibration test confirms the SCCs ability to control the single ASC during launch. The extended operation test allows data to be collected over a period of thousands of hours to obtain long term performance data of the ASC with a passive balancer and the SCC. This paper will discuss the results of each of these tests.

Vibration↗
NASA NTRS2014

Integration and Testing of LCS Software

Kennedy Space Center is in the midst of developing a command and control system for the launch of the next generation manned space vehicle. The Space Launch System (SLS) will launch using the new Spaceport Command and Control System (SCCS). As a member of the Software Integration and Test (SWIT) Team, command scripts, and bash scripts were written to assist in integration and testing of the Launch Control System (LCS), which is a component of SCCS. The short term and midterm tasks are for the most part completed. The long term tasks if time permits will require a presentation and demonstration.

Command Script↗