Download presentation
Presentation is loading. Please wait.
Published byEleanor Shepherd Modified over 9 years ago
1
Verification Data (Spatial and Weight) Unguided MK66 Weight = 23.4 lbs. (7.14 lbs fuel) Length = 55 in. x (c.g.) = 30 in. y (c.g.) = 0.0 in. z (c.g.) =.002 Guided MK66 Weight = 34.4 lbs. Max Length = 79.7 in. Max Center of Gravity - Move Aft - Decrease Yaw Rate on Missile - Remain Neutral in y & z
2
Verification Data (Performance) Consideration #1: Design to sustain Max g’s. Mechanical – stress concentrations on moving parts (i.e. canards) Electrical – tracking, servo response SL-MTI DC Servomotor MIL spec, designed for missile fin actuation
3
Max G’s: 64.8g
4
Guided Max G’s: 80g
5
Consideration #2: Design to sustain max jerk. Jerk is the rate of change of acceleration Commonly called pulse, impulse, shock, bounce, or jolt Important when evaluating destructive force on components
6
Max. Jerk: 291,786.7 m/s^3
7
Consideration #3: Thrust and Engine Burn-out Engine burns out at 1.2 seconds Max thrust occurs at.965 seconds Burn-out corresponds to approx. horizontal distance of 317m (4000m range)
8
Max. Thrust: 8142 N
9
Plans for Progress 1.Begin programming/simulation with Datcom Upsides Multiple Inputs Simple Programming (Dos-Prompted) Calculates Aerodynamic Forces on Missile and automatically generates plots Downsides Doesn’t model canards accurately at supersonic speeds 125 input lines vs. 26,000 output lines
10
Plans for Progress 2. Solid Modeling of Missile (ProE Wildfire) Will depict areas of stress concentrations Spatial Considerations Material Selection
11
Plans for Progress 3. Obtain Aerospace Blockset (Mathworks) Inputs: Aerodynamic Coefficients Dynamic Pressure Center of Gravity (CG) Center of Pressure Outputs: Aerodynamic Forces at CG (Drag, Lift) Aerodynamic Moments at CG
12
Aerospace Blockset Screenshot
13
Processor Solution - Altera Provides flexible I/O interfaces for purposes of acquiring GPS and IMU data Re-programmable if solution is not optimal according to design Have contact information within Altera
14
Why not M68K? No included/implicit interfacing without BIOS support No hardware multiplier support FPGA allows greater configuration flexibility than fixed-core CPU
15
Why not LabView? Proprietary FPGA solution requires PCI bus – not feasible for use inside a missile Possible overhead involved in using LabView as programming language instead of VHDL We already have Altera development software
16
Processor State Diagram
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.