DOTNET Framework Design Environment for System Integration of Planetary
Probe ... Interplanetary Trajectory Design Flow as employed in NET Framework.
DOTNET Framework F k Design D ig Environment E i t for f System Sy t Integration I t g ti off Planetary Pl t y Probe P b Payload P yl d Sensors S and d I t pl Interplanetary t y Trajectory T j t y Optimization Opti i ti Prabhakar Subrahmanyam, Subrahmanyam Keith Schreck and Periklis Papadopoulos San Jose State University, University Department of Mechanical and Aerospace Engineering, Engineering One Washington Square, Square San Jose, Jose California, California USA, USA 95152 95152-0087 0087 prasub@gmail com ,
[email protected] [email protected] keithsspace@yahoo com and
[email protected] periklis papadopoulos@sjsu edu
Software f Framework Architecture h
Interplanetary l Trajectory Design Flow l as employed l in .NET NET Framework
Payload l Mass Calculation: l l Inputs
Microsoft’s DOTNET Framework A d IIS W And Web b Server S
JAVA/DOTNET GUI
JAVA Computationa p l Engine
Probes Payload SENSORS Database
DOTNET Interface and Browser
Thermal A Aero
Payload l Mass Calculation l l Output ffrom the h Sensors Database b and the h program
Material Geometry
Planetary Probe OLAP Database
Interplanetary Trajectory j y Optimization
Generate Trajectory Data
Google’s KML Format
Excel Template Plots TecPlot Template Plots
Initiall Mass Calculations l l
I t pla Interplanetary p ta y Pa Payload yl ad d SSensors aand d Mi Mission i D Design ig g U Using i gM Multi lti Di ipli Disciplinary p yD Design ig g Opti Optimization p i ti ¾ Launch L h vehicle hi l p performance f – The Th Energy E gy equation q ti ¾ Planetary y orbital position p – Keplerian p orbit elements ¾ Interplanetary p y trajectories j – Lambert’s Problem
Patt h d C nii IInterplanetary Patched-Conic ntt plan ta t yT Trajectory ajj t y O Optimization ptimizati ti i ti n DOTNET Pl Planetary t Probe P b Vehicle V h l and d Trajectory T t Design D Interface I t f
¾ Developed a Payload Sensors RDBMS and Integrated DB with . NET Framework for Web accessibility ¾ Database manager allows selective data retrieval through .NET NET web application user interface ¾Comprehensive database of existing planetary probe designs and Sensors ¾ Features tables for aerothermal aerothermal, geometry ggeometry, y trajectory trajectory, j y sensors etc sensors, etc.. information ¾Users can modifyy existingg vehicle designs g byy changing g g geometric g features available in GUI GUI, Update p the database for their custom test pprobe architectures architectures. Add/Modifyy sensors in the UI based on the initial selection byy the system y driven byy Planetaryy body/Mission y Framework k Entry Design Environment ¾ SPARTA Design environment is an Automation Package for Sensor design ¾ Choose a Target Planetary body and the Sensors are automatically loaded into the DOTNET design interface ¾ The total power, power thermal, thermal mass requirements and other parameters are automatically calculated from the database and populated in the user interface ¾ The user is empowered with an option to add or delete a sensor for packaging into the probe ¾The TOF TOF, ΔV are all calculated and the user is alerted. alerted ¾ For Earth (Re) Entry Entry, user is presented with KML format for reentry visualization in Google Earth Driving Google l ffrom DOTNET Framework
¾ ΔV computations – Patched-Conic Patched Conic Approximation ¾ PSM derivation – Rocket engine equation ¾ Optimum case determination – MDO Simplex and Matrix Experiment techniques ¾ Ability to calculate conic section between planets using i the th Lambert L b t targeting t ti technique t h i
Total ΔV Vs Time of Flight
Payload System Mass Vs Time of Flight
¾ Calculation C l l ti off conic i section ti from f planet l t center t to t planet p l t center t in i a specified p ifi d time ti ¾ Ability Ability to calc calculate late the required req q ired velocity elocity impulse imp p lse at each of the planets p
Pl t Planetary P Position iti B Benchmark h k NET F Framework k Vs V JPL
Payload l Sensors and Planetary l Probe Relational l l Database Management
ΔV Benchmark B h k Driving g Google g Visualization: Stardust Re Re-entry entry y Aerial View
¾ Earth E th (R (Re) (Re)-Entry ) Entry E t Trajectory T j t Data D t converted t d to t Keyhole K h l Markup M k L Language (KML) ¾ Framework F k converts t the th trajectory t j t data d t andd produces d a fresh f h KML file fil for f every trajectory t j t array set.t ¾ Google G l Earth E th interprets i t t itit’s it’s native ti KML format f t andd produces d fl by fly-by fly b visualization i li i along l the h entry trajectory j ¾ Google G l Earth E h provides id rich i h interactive i i andd attractive i platform l f for f visualizing geospatial data. data ¾ The framework employs a pure Java library which generates KML output to display the most commonly interesting forms of geospatial data. data ¾ No prior knowledge of KML is required for the end-user end user. ¾ They are presented with a very simple API which expects data in the form of arrays arrays, in which it is likely to already exist exist, and will create graphical elements of the sort which users are most likely to want want. Driving Google Visualization from DOTNET: Stardust Trajectory
