Search NASA⌕ Search

SEARCH · Search NASA

Results for “firing room consoles”

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.

7 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Project Summary Report

The project, being the development of resource management applications, consisted entirely of my own effort. From deliverable requirements provided by my mentor, and some functional requirement additions generated through design reviews, It was my responsibility to implement the requested features as well as possible, given the resources available. For the most part development work consisted of database programming and functional testing using real resource data. Additional projects I worked on included some firing room console training, configuring the new NE-A microcontroller development lab network, mentoring high school CubeSat students, and managing the NE interns' component of the mentor appreciation ceremony.

Upchurch, Christopher↗
NASA NTRS2013

Master Console, SMC

The Master Console oversees the function of Computer Systems in Firing room 1 (FR1). Master Console Operators, MCOs' for short, are our customer. I was integrated into the System Monitoring and Control (SMC) software team that is under the guidance of David Slaiman, who is the product group lead. I have been brought up to speed with System Monitoring and Control. The initial time spent reading SMC software design description and understanding how it works. The current Firing Room 1 Console Display is a floor layout giving the MCO two essential pieces of information which are Health and Status. When an issue arises, the MCO has to look on the display to find which console is affected and then the MCO must use the Reference designator from the display to manually search for the Portal Workstation (PWS) installed in the console using the hardware map; which is a long process to lookup a PWS if an issue is present. My project is to make the FR1 Console Display easier for the MCO's to pinpoint PWS's without having to lookup additional resources in the process. My project also includes updating Firing Room 1 Console Display to include the F1R Non-Redundant Set. The display does not have good use of space and functionality. PWS numbers were not present in the previous design and are the critical component in efficient understanding and administration of the consoles. Part of the process includes getting feedback from the customer, instead of just emailing them with a question, we made a proposal with changes so they could respond and give us their input; which proved to be an effective method for engaging them. In order to do this I had to use the Display Editor (DE) tool developed by NASA, Paint.Net and Visio. The process I have been using has been Visio to alter the floor layout of Firing Room and take advantage of the white areas, and then I take the altered floor plan into Paint.Net. Once in Paint.Net I put the new floor plan as a background to the standard console display. Paint.Net also serves as a tool to create the new service state bars for the new background; finally I used the DE to assemble everything and setup the right CUI's for each PWS.

MCO↗
NASA NTRS2013

Design and Development of Functionally Effective Human-Machine Interfaces for Firing Room Displays

This project involves creating software for support equipment used on the Space Launch System (SLS). The goal is to create applications and displays that will be used to remotely operate equipment from the firing room and will continue to support the SLS launch vehicle to the extent of its program. These displays include design practices that help to convey information effectively, such as minimizing distractions at normal operating state and displaying intentional distractions during a warning or alarm state. The general practice for creating an operator display is to reduce the detail of unimportant aspects of the display and promote focus on data and dynamic information. These practices include using minimalist design, using muted tones for background colors, using a standard font at a readable text size, displaying alarms visible for immediate attention, grouping data logically, and displaying data appropriately varying on the type of data. Users of these displays are more likely to stay focused on operating for longer periods by using design practices that reduce eye strain and fatigue. Effective operator displays will improve safety by reducing human errors during operation, which will help prevent catastrophic accidents. This report entails the details of my work on developing remote displays for the Hypergolic fuel servicing system. Before developing a prototype display, the design and requirements of the system are outlined and compiled into a document. Then each subsystem has schematic representations drawn that meet the specifications detailed in the document. The schematics are then used as the outline to create display representations of each subsystem. Each display is first tested individually. Then the displays are integrated with a prototype of the master system, and they are tested in a simulated environment then retested in the real environment. Extensive testing is important to ensure the displays function reliably as intended.

displays↗
NASA NTRS2013

Master Console System Monitoring and Control Development

The Master Console internship during the spring of 2013 involved the development of firing room displays at the John F. Kennedy Space Center (KSC). This position was with the Master Console Product Group (MCPG) on the Launch Control System (LCS) project. This project is responsible for the System Monitoring and Control (SMC) and Record and Retrieval (R&R) of launch operations data. The Master Console is responsible for: loading the correct software into each of the remaining consoles in the firing room, connecting the proper data paths to and from the launch vehicle and all ground support equipment, and initializing the entire firing room system to begin processing. During my internship, I developed a system health and status display for use by Master Console Operators (MCO) to monitor and verify the integrity of the servers, gateways, network switches, and firewalls used in the firing room.

Brooks, Russell A.↗
NASA NTRS2013

Master Console System Monitoring and Control Development

The Master Console internship during the summer of 2013 involved the development of firing room displays and support applications at the John F. Kennedy Space Center (KSC). This position was with the Master Console Product Group (MCPG) on the Launch Control System (LCS) project. This project is responsible for the System Monitoring and Control (SMC) and Record and Retrieval (R&R) of launch operations data. The Master Console is responsible for: loading the correct software into each of the remaining consoles in the firing room, connecting the proper data paths to and from the launch vehicle and all ground support equipment, and initializing the entire firing room system to begin processing. During my internship, I created control scripts using the Application Control Language (ACL) to analyze the health and status of Kennedy Ground Control System (KGCS) programmable logic controllers (PLCs). This application provides a system health and status display I created with summarized data for use by Master Console Operators (MCO) to monitor and verify the integrity of KGCS subsystems.

Brooks, Russell A.↗
NASA NTRS2020

Command and Control System Automated Testing

To support the National Aeronautics and Space Administration’s (NASA) Space Launch System (SLS) rocket, Kennedy Space Center (KSC) has developed the Spaceport Command and Control System (SCCS) to monitor and control the pre-launch and launch operations. Within SCCS, the Launch Control System (LCS) is designed to allow console engineers to control and monitor the status of the launch and flight hardware, as well as issue commands to ground control systems and launch vehicles. The display software of the LCS is responsible for visualizing the various data that can be received from the hardware and software components of the LCS. Since this system is providing critical information to engineers in the firing room, the visualization of data across the system must be easy to understand, but also reliable and accurate.

Software↗
NASA NTRS2006

Incident Involving 30-Ah Li-ion Cell at NASA Glenn Research Center

The key lesson learned from the February 17, 2006 cell explosion incident is that PC-based test-systems, even those having built-in watchdog monitors, can lose control and malfunction. In the case of lithiumion cell/battery testing, the stored energy can be released explosively causing considerable injury and damage to facilities. The investigation showed that although the Arbin system has a built-in watchdog monitor, the circumstances of the incident defeated the action of the watchdog and allowed the cycler to continue operation without control. An upgrade to the most recent version of Arbin software (version 4) was provided as a fix to the presumed control problem. This upgrade included newer EPROM s for the cycler microprocessor. Investigation revealed that similar incidents have occurred at other NASA centers with a variety of PC-based test instruments. JPL suffered an incident with Maccor testers and the GRC fuel cell group observed similar problems with LabView software. This is not exclusively an Arbin problem, but an issue with all PC-based systems. In this incident, it was fortunate that the event occurred after-hours with no-one in the room. The facility arrangement placed control consoles adjacent to the test chamber doors. Had someone been in the room during the event, they would have been exposed to hot debris and toxic combustion products. It was also fortunate that the exploded cell stayed inside the chamber after the door was forced open. If the cell had been ejected into the room it could have caused serious facility damage by impact and possibly caused a fire in the facility.

Bennett, William↗