Launch Readiness Review JASMM Virginia Tech Team Members: Robbie Robertson Zack HarlowJeremiah Shiflet Daniel Martin Matt James Anthony Rinaldi Senior Advisors: Melissa Motylinski Adam Jones Jeff Crayley Sruthi KrishnanMichelle Perez June 9, 2010

User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A Type of RestrictionRestrictionStatus Mass allotment: = 10lb (including bottom bulkhead and half of the skin) Within.1lb Volume allotment: = Bottom Half (to 4.5”) The payload’s center of gravity (CG): At the center of our half. x-.078 y-.033 z-.177 Activation met under requirement: (either 1.SYS.1 or 1.SYS.2) 1 Ledex 1 Command Line Structure mounts: Top and bottom bulkheads. No mounts to sides of cans. Sharing: We take half volume and mass and set our CG in our center

We will complete our half first and CU will build their half off of the top of ours. The interface will consist of male threaded rods protruding through our ballast plate from standoffs. We are close enough to the edge of our canister that CU blocking our view out of the window with their lower plate should not be an issue We will be able to make weight/cg adjustments by adding or removing washers from the lower ballast (above or below the bottom plate). User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

Photometric Probe Testing –The A/D conversion has been calibrated and tested A power supply was used to apply various voltages to the inputs pins, and a program was written for the Gumstix computer to continuously output voltages to a putty window The results were correct within.001 V The A/D conversion has been calibrated and tested\ –The probe itself still needs to be tested For this we will use the same Gumstix code and bring the payload to our ECE professor’s lab to be tested with the correct wavelength of light. User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

IMU Testing –A program has been written for the Gumstix computer that outputs the IMU data once every two seconds to a putty window for testing –The current serial data packets returned by the IMU are identical to one another –The signal stops when the IMU is disconnected, so it is not some default signal from the microcontroller on the ASIM interface –We are working on the ASIM code to make this work –If it doesn’t work in time, we will only collect the photometric probe data and maybe rely on our colleagues for inertial data to correlate to our probe data User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

Power System Testing –The latching system works and all components work with the resulting outputs. –This Friday a researcher is returning to our lab who will bypass the g-switch and latching relays on our positive supply to prepare for a command line. –Thursday or Friday (6/10 or 6/11), we will test our new more powerful batteries for 15 minutes and run our individual IMU and probe testing programs to simulate the power requirements of flight –The heat sink on our power supply for the Cubesat computer system gets pretty hot, so we will monitor this during testing, and if it becomes an issue, we will collect data for a shorter period of time before powering off User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

We are not ready. To Do: –Bypass latching circuit and g-switch on one of our two power supplies to prepare for a command line –Run a day in the life power system test –Test photometric probe at optics lab –Complete IMU ASIM code Serial output is constant (not changing with IMU position) –Complete Flight Code Compiler is not working First code will be written only to store Probe Data as a minimal opition –This code is mostly finished, but compilation issues continue –Full day in the life testing User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

Why we aren’t ready: –Because of mistakes early on, the power system had to be redesigned and rebuilt. –Our team started late. –The software was neglected for too long. If the software can be finished in the next couple of days, our chances of finishing in time for reasonable testing are good User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

We have a custom box put together with padding for the payload and labeled bags of extra parts (electronics and hardware) We will bring wrenches, a drill, a soldering iron, screw drivers, a set of hex wrenches, a glue gun, large wrench for the adjustable bottom ballast, wire, shrink tube, and a heat gun. User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

The team members who are attending still need to go through the procedure. If we are able to complete our action items in time, the inspections should be no problem for us. User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A

How long will the command line activate before launch? User Guide ComplianceFinal PayloadIntegration Update/PlanTesting Results Level Of ReadinessRequired ToolsInspectionsQ/A