Network


Latest external collaboration on country level. Dive into details by clicking on the dots.

Hotspot


Dive into the research topics where Jacob Christensen is active.

Publication


Featured researches published by Jacob Christensen.


AIAA Infotech@Aerospace 2010 | 2010

CubeFlow: Training for a New Space Community

Craig J. Kief; Jacob Christensen; Bryan Hansen; Jesse Mee

Many organizations (academia, industry and government) make high quality satellite components; however, very few organizations make entire satellites well. Those that can successfully create entire satellites, often take years to design and deploy “Swiss watch,” one-of-a-kind satellites. The federal government wants a way to capitalize on all of these organization’s quality components in a quick and efficient manner. To be more responsive to the military and emergency responder’s needs, rapid satellite development and deployment is critical. There is a need for a method to go from pushbutton mission design to off the shelf components (that all seamlessly integrate) in a rapid fashion. Under sponsorship by the Operationally Responsive Space (ORS) office, the Air Force Research Laboratory (AFRL) developed a modular, nanosatellite, plug-and-play (PnP) approach where hardware and software modules can be rapidly merged to form functional satellites. The Stanford/Cal Poly CubeSat and Poly-Picosatellite Orbital Dispenser (PPOD) standards have revolutionized the way that small satellites are developed and deployed. AFRL wants to capitalize on this momentum to advance the concepts and goals of rapid space. Small satellites are an excellent test bed for larger spacecraft. The combination of the AFRL’s PnP design paradigm and the CubeSat standards has resulted in the creation of a CubeFlow program and CubeFlow training. The basis of the electrical and software infrastructure is the AFRL Space PnP Avionics (SPA) technology. Many have complained about the complexity of developing components that conform to the SPA standards. To alleviate this, a secure, web-based, design system has been created that allows convenient access for developing design configurations and coordinating the offerings of a community of component developers. This system provides a simple development flow through which component manufacturers can easily and efficiently create a PnP module. This stems from the idea that minimizing the amount of code that a developer must produce and also minimizing human error through constant validation will greatly increase efficiency. The hope is that those trained in the CubeFlow courses will gain the skills needed to produce useful PnP components and allow the PnP community to expand. Currently, there are a number of organizations and universities that have expressed interest in nano-satellite programs and rapid space development. CubeFlow is intended to address the issue that, due to lack of funding or capability, it is rare that a single organization or university would be able to research and develop all the necessary components for a small satellite. If a community can be built around an accepted standard such as PnP, then it may be possible to coordinate efforts in such a way that no longer would a single entity be tasked with the development of an entire satellite - but rather a single module or component. It is believed that this will not only lead to faster development, but higher quality satellites.


Infotech@Aerospace 2011 | 2011

Trailblazer: Proof of Concept CubeSat Mission for SPA-1

Craig J. Kief; Brian Zufelt; Jacob Christensen; Jesse Mee

The Space Plug-and-play Architecture (SPA) concept of rapid satellite development has progressed exponentially over the past several years. The team at the Configurable Space Microsystems Innovations and Applications Center (COSMIAC) in conjunction with the Space Dynamics Laboratory (SDL) and the Air Force Research Laboratory have trained over 500 individuals on this rapid bus architecture related to satellite development. This paper will outline the first CubeSat satellite proof of concept flight for a SPA only spacecraft. The Trailblazer mission is designed to fly a 1U CubeSat that is based entirely on a SPA bus implementation. Trailblazer will consist of Commercial Off The Shelf (COTS) parts converted to be SPA compliant. This allows not only a demonstration of the bus reliability in a space environment, but also the ease in converting existing components to be SPA compliant. With the dimensional constraints and power budget of Trailblazer, we have elected to use the SPA-1 standard. SPA-1 is the most recent addition to the AFRL SPA family. The SPA-1 data transfer protocol is based on 400 kbit/s I2C making it the lowest power, and lowest bandwidth option for SPA. Given the power constraints of typical satellite architecture, it is generally advantageous to interface devices/modules which do not require high data transfer rates to a SPA network via the SPA-1 Applique Sensor Interface Module (ASIM). This ASIM is logic that enables SPA Plug-and-Play for hardware components. It contains all the information needed for the system to automatically discover and automatically configure the hardware component. SPA-1 ASIMs can be any microcontroller that supports I2C and has enough memory to contain the needed logic. This allows the standard to remain open to a variety of dynamic implementations. The Trailblazer mission is being launched under the National Aeronautics and Space Administration (NASA) Educational Launch of Nanosatellite (ELaNA) program. This NASA program is designed to provide affordable access to space through collaborative efforts with academic institutions. The ELaNA program provides manifesting and launch of CubeSats for


AIAA Infotech@Aerospace 2010 | 2010

Automatic Software Generation of ASIM Program Code from an xTEDS

Jacob Christensen; Scott R. Cannon; Bryan Hansen

30,000 per 1U module. The proposed orbit is 325 km with an inclination of 51 degrees for a launch in 2011.


ieee aerospace conference | 2014

Standard Network Adapter for Payloads (SNAP)

Lt. Garrett Ellis; Paul Graven; Quinn Young; Jacob Christensen

The Satellite Data Model (SDM) developed at Utah State University (USU) is a plugand-play system for satellites. An xTEDS must be written for each sensor device that participates with the SDM. An interface module called an Appliqu e Sensor Interface Module (ASIM) must be developed to interface between the SDM and the sensor device. The program code that runs on an ASIM can be di cult to develop. This paper presents a technique for automatically generating ASIM program code by extrapolating the needed information from the sensor device’s xTEDS. This technique has been implemented in a tool called the ASIM Wizard. The ASIM Wizard reduces the time and e ort required to develop an ASIM.


ieee aerospace conference | 2012

Scalable network approach for the Space Plug-and-Play architecture

Jacob Christensen; David B. Anderson; Mark E. Greenman; Bryan Hansen

Given todays challenging budget environment for the Department of Defense, the National Security Space Enterprise is seeking unique and affordable ways to gain access to space. An emerging solution is aimed at addressing the fiscal challenges using commercially hosted payloads for military missions. With the success of Commercially Hosted Infrared Payload (CHIRP) in 2011, the United States Air Force is continuing to pursue new and innovative concepts and technologies to ensure hosted payloads remain an affordable avenue for resilient future space architectures. A specific enabling concept is a Modular, Open Networked Architecture (MONA) which is an outgrowth of two Department of Defense policy documents: the DODI 5000.02 and DoDD 8320.02. An emerging technology demonstration of MONA for the Hosted Payload Office is the Standard Network Adapter for Payloads (SNAP). In conjunction with the Space Dynamics Laboratory at Utah State University, the Space & Missiles Systems Centers Development Planning Directorate has demonstrated adapter between diverse hosted payloads and a spacecraft The demonstration was successfully conducted on November 2013 utilizing the ORS MSV testbed located at Northrop Grumman Corporation in Redondo Beach, California. The SNAP ground demonstration showcased ability to interface multiple payload types with multiple spacecraft vehicles. A specific outcome of the ground demonstration is a flight-ready version of SNAP software that can be utilized for follow-on on-orbit demonstration. The SNAP software supports both Linux and VxWorks Operating Systems. demonstration entailed three different simulated hosted payloads and quantified the integration time for each payload. The SNAP unit demonstrated that a payload with a Mil-Std-1553, RS-422, or SpaceWire connection can successfully, rapidly interface with a spacecraft that provides one of these connections. One critical component for the hosting of future military missions is resolving the information assurance aspect. For purposes of SNAP demonstration, the security layer was incorporated into the project but must be addressed operational viability in future hosted DoD missions. Demonstration of the SNAP capability has validated potential utility of adopting a MONA approach for a hosted payload adapter, and supports the notion that broader adoption of MONA for space systems development could significant benefits.


Proceedings of SPIE | 2016

Challenges in the application of modular open system architecture to weapons

Jonathan Shaver; Leo J. Rose; Quinn Young; Jacob Christensen

The Air Force Research Laboratory (AFRL) is sponsoring an effort to develop Plug-and-Play (PnP) technology for spacecraft systems. The Space PnP Architecture (SPA) supports a method of constructing arbitrarily complex arrangements of components. SPA is a networked data exchange model. This paper presents the SPA network architecture in relation to the standard five layers of the Open System Interconnect (OSI) model. The responsibilities and functionality of each layer are described. The SPA networking provides a unified methodology for self-discovery and self-configuration of heterogeneous PnP networks. The SPA networking approach is shown to be elegant, robust, and scalable.


Proceedings of SPIE | 2014

Open architecture applied to next-generation weapons

Leo J. Rose; Jonathan Shaver; Quinn Young; Jacob Christensen

The overarching objective for Flexible Weapons is to replace current inventory weapons that will not fully utilize the increased capabilities of 6th generation platforms, with a single weapons kit made up of flexible, open architecture components. Flexible Weapon will develop a common architecture to enable modular subsystems to achieve flexible weapons capability while allowing technology refresh at the pace of technology discovery in an affordable and sustainable design. The various combinations of weapons to address multiple missions must be 100% compatible with 6th generation delivery platforms (fighters, bombers, RPAs) and backwards compatible with 4th and 5th generation platforms.


24th Annual Conference on Small Satellites, Logan, UT, 8-11 August 2010 | 2010

A Plug-and-play Approach Based on the I2C Standard

James Lyke; Jesse Mee; Fredrik Bruhn; Gael Chosson; Robert Lindegren; Henrik Löfgren; Jan Schulte; Scott R. Cannon; Jacob Christensen; Bryan Hansen; Robert Vick; Alonzo Vera; Josette Calixte-Rosengren

The Air Force Research Laboratory (AFRL) has postulated a new weapons concept known as Flexible Weapons to define and develop technologies addressing a number of challenges. Initial studies on capability attributes of this concept have been conducted and AFRL plans to continue systems engineering studies to quantify metrics against which the value of capabilities can be assessed. An important aspect of Flexible Weapons is having a modular “plug-n-play” hardware and software solution, supported by an Open Architecture and Universal Armament Interface (UAI) common interfaces. The modular aspect of Flexible Weapons is a means to successfully achieving interoperability and composability at the weapon level. Interoperability allows for vendor competition, timely technology refresh, and avoids costs by ensuring standard interfaces widely supported in industry, rather than an interface unique to a particular vendor. Composability provides for the means to arrange an open end set of useful weapon systems configurations. The openness of Flexible Weapons is important because it broadens the set of computing technologies, software updates, and other technologies to be introduced into the weapon system, providing the warfighter with new capabilities at lower costs across the life cycle. One of the most critical steps in establishing a Modular, Open Systems Architecture (MOSA) for weapons is the validation of compliance with the standard.


Archive | 2010

Automatic Generation of SDM Application Source Code from xTEDS

Jacob Christensen; Scott R. Cannon; Bryan Hansen; Jim Lyke


Archive | 2014

Multi-layered Security Approaches for a Modular Open Network Architecture-based Satellite

Brandon Shirley; Quinn Young; Peter Wegner; Jacob Christensen; Jeffrey Janicik

Collaboration


Dive into the Jacob Christensen's collaboration.

Top Co-Authors

Avatar
Top Co-Authors

Avatar

Jesse Mee

Air Force Research Laboratory

View shared research outputs
Top Co-Authors

Avatar
Top Co-Authors

Avatar

James Lyke

Air Force Research Laboratory

View shared research outputs
Top Co-Authors

Avatar

Jonathan Shaver

Air Force Research Laboratory

View shared research outputs
Top Co-Authors

Avatar

Leo J. Rose

Air Force Research Laboratory

View shared research outputs
Top Co-Authors

Avatar

Alonzo Vera

University of New Mexico

View shared research outputs
Top Co-Authors

Avatar

Brian Zufelt

University of New Mexico

View shared research outputs
Top Co-Authors

Avatar

Fredrik Bruhn

Mälardalen University College

View shared research outputs
Researchain Logo
Decentralizing Knowledge