Learning Center
Plans & pricing Sign in
Sign Out



									                         Valley Technologies, Inc.

Magi Reconfigurable Testbed (MRT)

           For more information on MAGI Email:

Corporate Headquarters                   Engineering Department
724 Claremont Ave.                       2597-1 Clyde Ave.
Tamaqua, Pennsylvania 18252              State College, Pennsylvania 16801
Phone: 570-668-3737                      Phone: 814-234-1603
Fax: 570-668-6360                        Fax: 814-234-0723
Email:               Email:
         Valley Technologies Inc                      Magi Reconfigurable Testbed (MRT)
                                                                             Doc# D860-MAGI Rev 1.0

                                 Magi Reconfigurable Testbed

There are several current programs, as well as many new ones being developed or considered
for development, that will utilize high-performance sensors. As new sensor technologies and
data processing algorithms are developed, VTI believes it can contribute significantly to the
success of such programs. VTI is highly skilled in the development of demonstration platforms
and “proof of concept” systems utilizing the latest processor technologies. Additionally, VTI
has extensive experience in reconfigurable computing, algorithm analysis, algorithm to
hardware mapping, system definition, and algorithm interoperability. Drawing upon this unique
combination of skills and experience, VTI would like to present the following ideas for the “Magi
Reconfigurable Testbed”, or MRT.

To achieve the goals of risk reduction and rapid deployment, the development of algorithm and
control logic must begin as soon as requirements are defined. Algorithm developers and
system integrators cannot wait for actual flight hardware to be defined, built, and tested before
beginning their tasks. Unfortunately, in the current climate, the algorithm and control software
often has to be tailored around the hardware during the system integration and test phase,
making it difficult, if not impossible, to meet deployment deadlines.

With that in mind, the primary purpose of the MRT will be to allow early development, testing,
and integration of:
             system control logic
              data movement
              data formatting
              algorithm development

By beginning these tasks early, you can reduce risk, cut costs, and shorten the development
and integration cycle. In addition, the MRT will enable end-to-end simulation of systems
containing a mixture of software, hardware, emulators, and simulations, thereby providing a
suitable demonstration platform for such systems.

Providing the MRT is not the only way that VTI will contribute to the success of your program.
VTI will work closely with you to identify algorithms and define the hardware required to
support those algorithms. This will include defining the data input and output rates and
formats, as well as program power, weight, and size requirements. Once the program
requirements are defined, VTI will identify any currently available hardware that is compatible
with those requirements. Because VTI is a small company and does not directly compete with
the major hardware developers, we can provide an unbiased assessment regarding the
suitability of available hardware. If it is determined that suitable hardware does not exist or if
the appropriate hardware is too costly to add to the test bed, an emulator or simulation of the

9e1c85dc-2d83-4301-a6f3-c92f5eb750d4.doc                                Printed: 11/2/2012 / Page 2 of 5
         Valley Technologies Inc                      Magi Reconfigurable Testbed (MRT)
                                                                             Doc# D860-MAGI Rev 1.0

necessary hardware can be defined and developed. These emulators and simulations may be
a physical hardware emulator, a pure software emulator, a simulation, or any combination of
elements that is needed to address the requirements of the control software and algorithm
development. The emulators and simulations used will mimic the hardware interfaces and
control logic, thereby allowing for early software and algorithm development and integration.
When real hardware becomes available it is seamlessly integrated into the system, replacing
the emulator or simulation that originally represented it .

As stated previously, the MRT will built on VTI’s Magi software. Therefore, to fully appreciate
the benefits of the MRT, it is necessary to gain a better understanding of Magi. Magi is a
software development and deployment environment being developed by VTI. Magi helps
manage the complexity and overcome the challenges associated with distributed, mixed
(software/simulator/reprogrammable hardware) system development. Magi achieves this, in
part, by providing a single integrated view of the entire system under development. Magi
facilitates code and data reuse by providing an intuitive user interface to the underlying version
control system. Magi allows the user to encapsulate data and instruction sequences into
deployments that can be distributed to any number of components throughout the system.
And, thanks to Magi’s underlying network communications library, it doesn’t matter if those
components are across the room, on the other side of the world, or out in space.

Magi interacts with a specific component in the system through that component’s Board
Support Package, or BSP. In a nutshell, a BSP is an xml description of the component’s
available functions, as well as any operational constraints it may have. To add a new
component to the system, one just adds that component to the BSP. Using the Magi BSP
Generator/Editor facilitates generation of a BSP for new hardware or software. Simply supply
Magi with a header or interface file for the component, answer a few simple questions in the
BSP Generation Wizard, and Magi does the rest.

Magi’s Descriptor Editor, Deployment Builder, and Application Loader combine to provide a
very flexible system command-and-control environment. Data and programming files are
added to the system using the Descriptor Editor, which adds useful metadata before storing
the files in a central repository. Files that have been added to the repository are available for
use in the Deployment Builder. Also available in the Deployment Builder are general logic
objects, as well as all system components and their available functions as described by the
BSP. The user creates a deployment sequence by dragging component functions, data files,
and logic objects to the deployment timeline. Finally, the deployment sequence is launched
using the Application Loader, which provides additional control over deployment execution
such as the ability to set break points or single-step through instructions.

9e1c85dc-2d83-4301-a6f3-c92f5eb750d4.doc                                Printed: 11/2/2012 / Page 3 of 5
         Valley Technologies Inc                       Magi Reconfigurable Testbed (MRT)
                                                                              Doc# D860-MAGI Rev 1.0

Magi also excels as a demonstration platform. In the development of any new system, it’s
crucial to engage the customer and demonstrate the dynamic features of your system. Using
Magi, the user can create a “demonstration” deployment that encapsulates the data and
sequence of steps necessary to make the system run. The deployment timeline in Magi’s
application loader, coupled with Magi’s ability to display graphs and charts of resulting data,
allow customers to “see” the system working. Should more complex display requirements be
needed, Magi has the ability to launch an external application to display this data.

The Magi Reconfigurable Testbed will assist the user in all phases of system development,
from initial design and testing, to final integration and demonstration. Magi’s “plug and play”
architecture has the ability to swap software, hardware emulators, and reprogrammable
hardware into and out of your system at will, eliminating project delays that result from
unavailable hardware. By allowing system integration and testing to begin earlier in the
development of a project, the Magi Reconfigurable Testbed will help reduce risk, reduce cost,
and shorten the development and integration cycle. Ultimately, using the Magi Reconfigurable
Testbed will bring repeatability, reusability, scalability, and accountability to your entire system
development process.

9e1c85dc-2d83-4301-a6f3-c92f5eb750d4.doc                                 Printed: 11/2/2012 / Page 4 of 5
         Valley Technologies Inc                                     Magi Reconfigurable Testbed (MRT)
                                                                                        Doc# QSM00028 Rev 1.0

                                    Example of MAGI Controlled Testbed

9e1c85dc-2d83-4301-a6f3-c92f5eb750d4.doc                                          Printed: 11/2/2012 / Page 5 of 5

To top