Members Can Post Anonymously On This Site
-
Similar Topics
-
By Space Force
U.S. Space Force Chief of Space Operations Gen. Chance Saltzman and Italian Air Force Chief of Staff Lt. Gen. Luca Goretti signed a statement of understanding.
View the full article
-
By European Space Agency
Image: Part of the Italian island of Sardinia is featured in this image captured by the Copernicus Sentinel-2 mission. View the full article
-
By NASA
NASA astronaut and Expedition 72 flight engineer Anne McClain is pictured near one of the International Space Station’s main solar arrays during a spacewalk.NASA/Nichole Ayers In this May 1, 2025, photo taken by fellow NASA astronaut Nichole Ayers, Anne McClain works near one of the International Space Station’s main solar arrays during a spacewalk. During the May 1 spacewalk – McClain’s third and Ayers’ first – the astronaut pair relocated a space station communications antenna and completed the initial mounting bracket installation steps for an International Space Station Rollout Solar Array, or IROSA, that will arrive on a future SpaceX commercial resupply services mission, in addition to some get ahead tasks.
Learn more about station activities by following the space station blog.
Image credit: NASA/Nichole Ayers
View the full article
-
By NASA
5 min read
Preparations for Next Moonwalk Simulations Underway (and Underwater)
Editor’s Note: The following is one of three related articles about the NASA Data Acquisition System and related efforts. Please visit Stennis News – NASA to access accompanying articles.
A blended team of NASA personnel and contractors support ongoing development and operation of the NASA Data Acquisition System at NASA’s Stennis Space Center. Team members include, left to right: Andrew Graves (NASA), Shane Cravens (Syncom Space Services), Peggi Marshall (Syncom Space Services), Nicholas Payton Karno (Syncom Space Services), Alex Elliot (NASA), Kris Mobbs (NASA), Brandon Carver (NASA), Richard Smith (Syncom Space Services), and David Carver (NASA)NASA/Danny Nowlin Members of the NASA Data Acquisition System team at NASA’s Stennis Space Center evaluate system hardware for use in monitoring and collecting propulsion test data at the site.NASA/Danny Nowlin NASA software engineer Alex Elliot, right, and Syncom Space Services software engineer Peggi Marshall fine-tune data acquisition equipment at NASA’s Stennis Space Center by adjusting an oscilloscope to capture precise measurements. NASA/Danny Nowlin Syncom Space Services software test engineer Nicholas Payton Karno monitors a lab console at NASA’s Stennis Space Center displaying video footage of an RS-25 engine gimbal test, alongside data acquisition screens showing lab measurements. NASA/Danny Nowlin Just as a steady heartbeat is critical to staying alive, propulsion test data is vital to ensure engines and systems perform flawlessly.
The accuracy of the data produced during hot fire tests at NASA’s Stennis Space Center near Bay St. Louis, Mississippi, tells the performance story.
So, when NASA needed a standardized way to collect hot fire data across test facilities, an onsite team created an adaptable software tool to do it.
“The NASA Data Acquisition System (NDAS) developed at NASA Stennis is a forward-thinking solution,” said David Carver, acting chief of the Office of Test Data and Information Management. “It has unified NASA’s rocket propulsion testing under an adaptable software suite to meet needs with room for future expansion, both within NASA and potentially beyond.”
Before NDAS, contractors conducting test projects used various proprietary tools to gather performance data, which made cross-collaboration difficult. NDAS takes a one-size-fits-all approach, providing NASA with its own system to ensure consistency.
“Test teams in the past had to develop their own software tools, but now, they can focus on propulsion testing while the NDAS team focuses on developing the software that collects data,” said Carver.
A more efficient workflow has followed since the software system is designed to work with any test hardware. It allows engineers to seamlessly work between test areas, even when upgrades have been made and hardware has changed, to support hot fire requirements for the agency and commercial customers.
With the backing and resources of the NASA Rocket Propulsion Test (RPT) Program Office, a blended team of NASA personnel and contractors began developing NDAS in 2011 as part of the agency’s move to resume control of test operations at NASA Stennis. Commercial entities had conducted the operations on NASA’s behalf for several decades.
The NASA Stennis team wrote the NDAS software code with modular components that function independently and can be updated to meet the needs of each test facility. The team used LabVIEW, a graphical platform that allows developers to build software visually rather than using traditional text-based code.
Syncom Space Services software engineer Richard Smith, front, analyzes test results using the NASA Data Acquisition System Displays interface at NASA’s Stennis Space Center while NASA software engineer Brandon Carver actively tests and develops laboratory equipment. NASA/Danny Nowlin NASA engineers, from left to right, Tristan Mooney, Steven Helmstetter Chase Aubry, and Christoffer Barnett-Woods are shown in the E-1 Test Control Center where the NASA Data Acquisition System is utilized for propulsion test activities. NASA/Danny Nowlin NASA engineers Steven Helmstetter, Christoffer Barnett-Woods, and Tristan Mooney perform checkouts on a large data acquisition system for the E-1 Test Stand at NASA’s Stennis Space Center. The data acquisition hardware, which supports testing for E Test Complex commercial customers, is controlled by NASA Data Acquisition System software that allows engineers to view real-time data while troubleshooting hardware configuration.NASA/Danny Nowlin NASA engineers Steven Helmstetter, left, and Tristan Mooney work with the NASA Data Acquisition System in the E-1 Test Control Center, where the system is utilized for propulsion test activities.NASA/Danny Nowlin “These were very good decisions by the original team looking toward the future,” said Joe Lacher, a previous NASA project manager. “LabVIEW was a new language and is now taught in colleges and widely used in industry. Making the program modular made it adaptable.”
During propulsion tests, the NDAS system captures both high-speed and low-speed sensor data. The raw sensor data is converted into units for both real-time monitoring and post-test analysis.
During non-test operations, the system monitors the facility and test article systems to help ensure the general health and safety of the facility and personnel.
“Having quality software for instrumentation and data recording systems is critical and, in recent years, has become increasingly important,” said Tristan Mooney, NASA instrumentation engineer. “Long ago, the systems used less software, or even none at all. Amplifiers were configured with physical knobs, and data was recorded on tape or paper charts. Today, we use computers to configure, display, and store data for nearly everything.”
Developers demonstrated the new system on the A-2 Test Stand in 2014 for the J-2X engine test project.
From there, the team rolled it out on the Fred Haise Test Stand (formerly A-1), where it has been used for RS-25 engine testing since 2015. A year later, teams used NDAS on the Thad Cochran Test Stand (formerly B-2) in 2016 to support SLS (Space Launch System) Green Run testing for future Artemis missions.
One of the project goals for the system is to provide a common user experience to drive consistency across test complexes and centers.
Kris Mobbs, current NASA project manager for NDAS, said the system “really shined” during the core stage testing. “We ran 24-hour shifts, so we had people from across the test complex working on Green Run,” Mobbs said. “When the different shifts came to work, there was not a big transition needed. Using the software for troubleshooting, getting access to views, and seeing the measurements were very common activities, so the various teams did not have a lot of build-up time to support that test.”
Following success at the larger test stands, teams started using NDAS in the E Test Complex in 2017, first at the E-2 Test Stand, then on the E-1 and E-3 stands in 2020.
Growth of the project was “a little overwhelming,” Lacher recalled. The team maintained the software on active stands supporting tests, while also continuing to develop the software for other areas and their many unique requirements.
Each request for change had to be tracked, implemented into the code, tested in the lab, then deployed and validated on the test stands.
“This confluence of requirements tested my knowledge of every stand and its uniqueness,” said Lacher. “I had to understand the need, the effort to meet it, and then had to make decisions as to the priorities the team would work on first.”
Creation of the data system and its ongoing updates have transformed into opportunities for growth among the NASA Stennis teams working together.
“From a mechanical test operations perspective, NDAS has been a pretty easy system to learn,” said Derek Zacher, NASA test operations engineer. “The developers are responsive to the team’s ideas for improvement, and our experience has consistently improved with the changes that enable us to view our data in new ways.”
Originally designed to support the RPT office at NASA Stennis, the software is expanding beyond south Mississippi to other test centers, attracting interest from various NASA programs and projects, and garnering attention from government agencies that require reliable and scalable data acquisition. “It can be adopted nearly anywhere, such as aerospace and defense, research and development institutions and more places, where data acquisition systems are needed,” said Mobbs. “It is an ever-evolving solution.”
Read More Share
Details
Last Updated May 08, 2025 EditorNASA Stennis CommunicationsContactC. Lacy Thompsoncalvin.l.thompson@nasa.gov / (228) 688-3333LocationStennis Space Center Related Terms
Stennis Space Center View the full article
-
By USH
In a groundbreaking development, advances in quantum data analysis have led to a discovery no scientist could have foreseen. NASA’s deep space monitoring system, upgraded with a quantum processor designed to filter cosmic noise and decode interstellar signals, produced something startling: an image.
A conceptual interpretation of the Voyager 1 image.
But this wasn’t an input, a simulation, or a product of algorithmic imagination. It wasn’t the result of random noise or a misfired pattern recognition process. The quantum system returned a coherent, structured, and symmetrical image, undeniably artificial. And the data it derived from? None other than Voyager 1.
Renowned physicist Michio Kaku addressed the anomaly in a recent interview: “We may be witnessing the first whisper of a new intelligence, something not man-made, not terrestrial, and certainly not random.”
The image, reconstructed via entangled qubit networks, depicted a figure: humanoid in silhouette, yet composed of geometric segments that defied any known biological or mechanical blueprint. It seemed deliberately crafted to challenge human comprehension, alien, yet eerily familiar enough to spark recognition.
Not long ago, NASA pushed the boundaries of computation by launching an experimental quantum computer, capable of processing vast, multidimensional data streams. But after this revelation, NASA abruptly shut down the system following the unexpected and unsettling incident, in 2023, though some believe the research continued in secret.
Meanwhile, Voyager 1—the most distant human-made object in space, still traveling beyond our solar system after 45 years—has been transmitting strange, inexplicable data. According to NASA engineers, the spacecraft’s Attitude Articulation and Control System (AACS) began sending signals that “do not reflect what’s actually happening onboard.”
Instead of useful telemetry, Voyager 1 has been broadcasting a puzzling sequence: a repeating pattern of ones and zeros. Initially dismissed as a glitch, engineers traced the anomaly to the Flight Data Subsystem (FDS), pinpointing a malfunctioning chip. Yet, despite their efforts, the signal persisted, a digital enigma from 24 billion kilometers away.
Is this merely a failing system showing its age? Or is something, or someone, intentionally altering the data?
What if this “error” is a message? And if so, who’s sending it?
View the full article
-
-
Check out these Videos
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.