cubesat.wdfiles.comcubesat.wdfiles.com/.../plm-man-wpbdescrip-517-4.docx · web viewusing the logic...

University of Leicester PLUME Ref: PLM-MAN-WPBDescrip-517-4Date: 08/01/2010

Work Package Breakdown Descriptions List

L. Evans

Date Updated Reference Number change

12/08/2009 PLM-MAN-WPBDescrip-517-0 first draft17/08/2009 PLM-MAN-WPBDescrip-517-1 first version issued11/09/2009 PLM-MAN-WPBDescrip-517-2 Updated with PAY, CAM,

OBDH, PSU, COMS07/01/2010 PLM-MAN-WPBDescrip-517-3 Updates to OBDH08/01/2010 PLM-MAN-WPBDescrip-517-4 Updated PAY, CAM.

Work Package Title Test PPB EMCO HV supplyReference Number PLM-PAY-WPPPBTestHV-001-1Length 2Cost £0.00Requirements Electronics lab space, 1500V-capable voltmeter.Pre-requisites NoneDescription The PPB has three main components: the HV supply, the DC-DC

converter and the signal processing chain. The HV supply must be connected to a suitable voltmeter and the predicted ratio of output to input voltages must be verified. The HV supply will not be connected to an MCP for this experiment so the voltage curve recorded will correspond to a plate of infinite resistance. This is the condition for a ‘bad contact’ failure mode, which the flight software will have to detect.

Outputs Results document including input-output voltage curve for the HV supply (for infinite resistance plate).

Work Package Title Test PPB RECOM DC-DC converter Reference Number PLM-PAY-WPPPBTestDC-002-1Length 2Cost £0.00Requirements Electronics lab space.Pre-requisites NoneDescription The DC-DC converter supplies -5V power to the signal processing

chain. It must be shown that the converter and its regulator is producing the correct voltages before the expensive signal processing chain components are installed.

Outputs Validated DC-DC converter circuit.

of 47


Work Package Title Test PPB signal processing chainReference Number PLM-PAY-WPPPBTestSignal-003-1Length 2Cost £0.00Requirements Electronics lab space, pulse generator, oscilloscope, electronics

specialist.Pre-requisites PLM-PAY-WPTestDC-002-1Description The installation of the AmpTek A250 and A275 chips should be

carried out by an electronics engineer (like Duncan Ross). The signal processing chain is responsible for processing the charge pulses given off by detector events into a form that a computer (like an MCA, or the MCU on our satellite) can read. The PPB contains the first two components of this chain; a charge-sensitive preamplifier and a shaping amplifier. These must be tested with simulated signals, the gain of the shaping amplifier must be calibrated, and the noise level taken.

Outputs Results document including noise levels and gain calibration settings for the signal chain.

Work Package Title Acquire new filmed MCP.Reference Number PLM-PAY-WPLaserMCPAcquire-004-1Length 1Cost £0.00Requirements Access to storesPre-requisites NoneDescription The laser testing of the detector hardware conducted before the

summer holidays was a great success, but resulted in terminal damage to the MCP. A new MCP of identical specification must be procured, it must be installed in the detector body (which provides a mechanical and electrical interface between the detector inside the chamber and the equipment outside it), and it must be mounted to the vacuum chamber which must then be pumped down and leak tested.

Outputs Filmed MCP.

Work Package Title Install MCP stack in detector bodyReference Number PLM-PAY-WPLaserMCPBody-005-1Length 1Cost £0.00Requirements MCP specialist, laminar flow cabinet.Pre-requisites PLM-PAY-WPLaserMCPAcquire-004-1Description The new MCP must be installed in the detector body (which

provides a mechanical and electrical interface between the detector inside the chamber and the equipment outside it) compatible with the vacuum chamber.

Outputs Constructed MCP stack.

of 47


Work Package Title Attach new MCP to vacuumReference Number PLM-PAY-WPLaserMCPVacuum-006-1Length 1Cost £0.00Requirements Rob Limpenny, vacuum chamber.Pre-requisites PLM-PAY-WPLaserMCPBody-005-1Description The MCP must be mounted to the vacuum chamber which must

then be pumped down and leak tested.Outputs Vacuum chamber fitted with filmed MCP detector body.

Work Package Title Use NIM to power up MCPReference Number PLM-PAY-WPLaserVerifyMCP-007-1Length 1Cost £0.00Requirements Vacuum chamber, NIM rack HV supply and ammeter, MCP

specialist supervision.Pre-requisites PLM-PAY-WPLaserMCPBody-006-1Description New MCPs are particularly susceptible to damage during use. Plate

resistance and current must be carefully monitored to ensure that thermal runaway or shorts due to outgassing do not damage the plate. The NIM rack in the cryolab contains high voltage power supplies and connections for voltmeters and ammeters, which provide a level of safety that the PPB lacks. It should be used for the first powerup of the new MCP with the eventual aim of running the MCP stably at operating voltages for a week.

Outputs Stable MCP detector in vacuum chamber.

Work Package Title Write PPB MCP powerup test planReference Number PLM-PAY-WPLaserMCPTestPlan-008-1Length 1Cost £0.00Requirements PPB circuit diagram, EMCO HV supply application notes.Pre-requisites NoneDescription A test plan must be written to describe powering up the MCP

detector using the PPB. This test will include obtaining the input-output voltage ratio for the HV supply, as in PLM-PAY-WPPPBTestHV-001-1 only for a connected MCP with a particular resistance. This is important because the flight payload will have no ability to sense the plate current directly; instead, it measures the ratio of HV input to HV output which goes up when more current is drawn from the supply. With the MCP connected to the PPB supply, the voltage curve for normal plate operation can be found.

Outputs Test plan for PPB MCP powerup.

of 47


Work Package Title Use PPB to power up MCPReference Number PLM-PAY-WPLaserPowerMCP-009-1Length 2Cost £0.00Requirements Vacuum chamber.Pre-requisites PLM-PAY-WPLaserVerifyMCP-007-1, PLM-PAY-

WPLaserMCPTestPlan-008-1Description The PPB’s high voltage supply should be used to power up the

MCP according to the test plan. Outputs Results document including input-output voltage curve (normal

load).

Work Package Title Acquire pulse laserReference Number PLM-PAY-WPLaserAcquire-010-1Length 1Cost £0.00Requirements Chemistry department contact.Pre-requisites NoneDescription The best simulation of a dust impact on the detector that can be

performed in Leicester involves firing a laser into the detector aperture to vapourize the film on the front of the MCP in the same way that a micrometeoroid would. A suitable laser belongs to the chemistry department, and it must be obtained in order for the laser testing to proceed. Tests using this laser took place last term and were highly successful.

Outputs Nd:YAG laser and power supply.

Work Package Title Write laser experiment planReference Number PLM-PAY-WPLaserPlan-011-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription A test plan must be written to verify that the laser events can be

detected using the PPB.Outputs Laser experiment plan.

Work Package Title Set up laser experimentReference Number PLM-PAY-WPLaserSetup-012-1Length 1Cost £0.00Requirements Laser specialist supervision, Nd:YAG laser, optical benchPre-requisites NoneDescription An optical bench for aligning and aiming the laser must be set up,

the vacuum chamber with the detector must be moved and the laser itself must be borrowed installed under supervision from the chemistry department.

Outputs Prepared laser testing setup.

of 47


Work Package Title Conduct second laser experimentReference Number PLM-PAY-WPLaserTest-013-1Length 2Cost £0.00Requirements Laser specialist supervision, Nd:YAG pulse laser, optical bench,

vacuum chamber, MCA.Pre-requisites PLM-PAY-WPLaserSetup-012-1, PLM-PAY-WPLaserTestPlam-

011-1.Description A test of the suitability of the detector setup for detecting dust using

an Nd:YAG pulse laser has already been successfully carried out. To validate the PPB for such purposes, the laser experiment must be repeated, investigating pulse height distributions for different plate voltages. The information gathered from this experiment can be used to help calibrate the gain setting on the signal processing chain.

Outputs Results document containing pulse height distribution for PPB under laser testing conditions, calibration data for PPB.

Work Package Title Analyse laser experiment results.Reference Number PLM-PAY-WPLaserAnalysis-014-1Length 4Cost £0.00Requirements Laser experiment results documentPre-requisites PLM-PAY-WPLaserTest-013-1Description The plate voltage must be related to the gain of the plate for a single

laser burst. For this analysis, it will also be necessary to look at the plate under a microscope to determine how many channels were fired with each laser pulse.

Outputs Gain equation with respect to voltage and seed cloud size.

Work Package Title Install flight-type MCP detector in stackReference Number PLM-PAY-WPDustMCPBody-015-1Length 2Cost £0.00Requirements MCP specialist, laminar flow cabinet.Pre-requisites NoneDescription Photonis has supplied us with an MCP with identical specifications

to the flight detectors. However, the MCP is installed in a body which is not directly compatible with our vacuum system. A way of installing one in the other must be devised before the Heidelberg experiments can take place.

Outputs Constructed flight-type MCP stack

Work Package Title Power up flight-type MCP in preparation for Heidelberg testsReference Number PLM-PAY-WPDustMCPTest-016-1Length 2Cost £0.00Requirements NonePre-requisites PLM-PAY-WPDustMCPBody-015-1Description The flight-type MCP must be stably run in a vacuum under test

of 47


conditions here in Leicester before it can be shipped to Germany.Outputs Validated flight-type MCP stack.

Work Package Title Arrange test using Heidelberg dust acceleratorReference Number PLM-PAY-WPDustArrangeTest-017-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription The Max Planck institute for nuclear physics in Heidelberg operates

a powerful dust accelerator, which among other things was used in the development of the Cassini spacecraft cosmic dust analyser. This is the ideal facility to perform the final tests of our detector. The facility must be contacted and dates and procedures must be agreed on.

Outputs Date for dust accelerator testing in Germany, and experimental procedures.

of 47


Work Package Title Prepare PPB for transportReference Number PLM-PAY-WPDustTravel-018-1Length 2Cost £0.00Requirements Engineering assistance, vacuum engineer, possibly metalworking.Pre-requisites NoneDescription Both the payload prototype board and the detector body must be

configured so that they will be compatible with the Heidelberg dust accelerator, as well as packaged for the journey there.

Outputs Travel-ready PPB and MCP detector body.

Work Package Title Write dust experiment planReference Number PLM-PAY-WPDustPlan-019-1Length 1Cost £0.00Requirements NonePre-requisites PLM-PAY-WPLaserAnalysis-014-1Description A plan must be written for the Heidelberg experiments. The purpose

of these tests is to understand the relationship between plate voltage, dust mass and dust energy. Predictions of signal size should be made based on the laser experiment analysis.

Outputs Dust experiment plan.

Work Package Title Dust bombardment measurements at HeidelbergReference Number PLM-PAY-WPDustTest-020-1Length 3Cost UnknownRequirements Transport and accommodation at Heidelberg.Pre-requisites PLM-PAY-WPDustPlan-019-1 Description This work package includes travelling to Heidelberg and

implementing the test plan on their accelerator equipment.Outputs Results document with plate voltage/mass/velocity relationship for

the PLUME detector.

Work Package Title Analyse dust experiment resultsReference Number PLM-PAY-WPDustAnalyse-021-1Length 4Cost UnknownRequirements Heidelberg experiment results.Pre-requisites PLM-PAY-WPDustPlan-020-1 Description From the results document, in addition to the laser experiment

results document and gain calculations, final settings for the payload should be obtained. These should include final potentiometer values for the signal processing chain and voltage ranges for the detector DAC.

Outputs Final settings for PLUME detectors.

Work Package Title Learn to integrate circuits with the MCUReference Number PLM-PAY-WPLearnMCUIntegration-022-1

of 47


Length 2Cost UnknownRequirements PLM-OBDH-Operations-215.docxPre-requisites NoneDescription Most of the components of the payload need to be controlled by the

MCU in order to function. The OBDH development hardware contains a working MCU; a payload team member will need to become proficient in connecting circuitry to this MCU and physically setting up the hardware so that software can be downloaded and tests can take place.


Work Package Title Learn to program the MCUReference Number PLM-PAY-LearnMCUProgramming-023-1Length 4Cost UnknownRequirements PLM-OBDH-Operations-215.docxPre-requisites None Description A member of the payload team will have to have a good working

knowledge of how to program the MCU. The responsibility of writing flight software is down to the OBDH team, but test software must be handled by the payload team. Most of the software for testing the payload will be modified flight software, and a programmer will be needed to do the modification.


Work Package Title Acquire DAC componentsReference Number PLM-PAY-WPDACAcquire-024-1Length 0.5Cost £0.00Requirements Access to stores.Pre-requisites NoneDescription The DAC (digital-analog converter) allows the MCU to select one of

eight different voltages to power the HV supply with, which varies the output voltage and with it the gain of the dust detector. The DAC circuit has been designed, and components must be procured in order to test it. The DAC uses common components which should be easy to find.

Outputs DAC components.

of 47


Work Package Title Breadboard the DACReference Number PLM-PAY-WPDACBreadboard-025-1Length 0.5Cost £0.00Requirements Electronics lab space.Pre-requisites PLM-PAY-WPDACAcquire-024-1Description Use a breadboard to construct the DAC according to the circuit

diagram.Outputs DAC breadboard.

Work Package Title Write software for DAC MCU testsReference Number PLM-PAY-WPDACSoftware-026-1Length 1Cost £0.00Requirements OBDH development hardware, programmerPre-requisites PLM-PAY-LearnMCUProgramming-023-1Description Software must be written so that the DAC can be controlled by the

MCU prototype board. Since this software will not be included in the flight board program, it is the responsibility of the payload team to write it. The OBDH operations manual contains references to programming instructions.

Outputs DAC testing software.

Work Package Title Integrate the DAC with MCU dev. board Reference Number PLM-PAY-WPDACIntMCUDev-027-1Length 0.5Cost £0.00Requirements OBDH development hardware.Pre-requisites PLM-PAY-WPDACBreadboard-025-1, PLM-PAY-

WPLearnMCUIntegration-022-1Description The DAC breadboard must be electrically connected to the MCU

development board. The OBDH operations manual contains instructions for doing so.

Outputs Integrated MCU-DAC.

Work Package Title Write DAC test plan Reference Number PLM-PAY-WPDACTestPlan-028-1Length 1Cost £0.00Requirements PLM-OBDH-Operations-215-2.docxPre-requisites NoneDescription A test plan must be written for the communications tests with the

DAC. It must describe how to verify that the DAC is responding to the MCU commands with the correct voltages.

Outputs DAC test plan.

of 47


Work Package Title Test DAC with MCU.Reference Number PLM-PAY-WPDACTest-029-1Length 2Cost £0.00Requirements OBDH development hardware, electronics lab space, DAC test

plan, logic analyser.Pre-requisites PLM-PAY-WPDACTestPlan-028-1, PLM-PAY-WPDACIntMCUDev-

027-1, PLM-PAY-WPDACSoftware-026-1Description Implement the test plan and use the MCU to control the voltage

output of the DAC. If necessary, change component values until the output of the DAC is in the correct regime. If testing is successful, the test software should be checked against the flight software to ensure that the flight software would also be able to correctly control the DAC.

Outputs Results document, working DAC breadboard.

Work Package Title Complete design of sample-hold (buffer) circuitReference Number PLM-PAY-WPSampleDesign-30-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription The sample-hold circuit is the interface linking the signals from the

detector to the onboard MCU’s analog-digital converter. The payload requires a circuit that samples the signal voltage input from the A275 shaping amplifier, and then ‘holds’ it when it reaches its highest value on an output pin which would then be connected to the ADC. The sample hold must also be resettable via a signal from the MCU, and give a signal to the MCU when the hold is triggered. A circuit must be designed with this functionality.

Outputs Sample-hold circuit design

Work Package Title Acquire sample-hold componentsReference Number PLM-PAY-WPSampleAcquire-031-1Length 0.5Cost £0.00Requirements Access to stores.Pre-requisites PLM-PAY-WPSampleDesign-030-1Description A separate breadboard to the one used for the DAC must be

procured in addition to acquiring the necessary components to build the sample-hold prototype circuit.

Outputs Sample-hold circuit components.

of 47


Work Package Title Breadboard sample-hold circuit. Reference Number PLM-PAY-WPSampleBreadboard-032-1Length 0.5Cost £0.00Requirements Electronics lab space.Pre-requisites PLM-PAY-WPSampleAcquire-031-1Description The sample-hold must be breadboarded.Outputs Prototype sample-hold circuit breadboard.

Work Package Title Write sample-hold circuit test plan. Reference Number PLM-PAY-WPSampleTestPlan-033-1Length 1Cost £0.00Requirements PLM-OBDH-Operations-215-2.docxPre-requisites NoneDescription A test plan must be written; the sample-hold will require both

preliminary electrical testing to ensure that it is producing acceptable voltages, and testing using the MCU development board to prototype it.

Outputs Sample-hold test plan.

Work Package Title Test the sample-hold circuitReference Number PLM-PAY-WPSampleTestPulse-034-1Length 2Cost £0.00Requirements Electronics lab space, sample-hold test plan.Pre-requisites PLM-PAY-WPSampleTestPlan-033-1Description Preliminary testing of the sample hold will involve first connecting it

up to a power supply and checking its inputs and outputs, and secondly sending test pulses through it to ensure that it is triggering correctly. The rate at which voltage drains from the hold capacitor must also be ascertained, and if it drains too rapidly then a different hold capacitor must be tried.

Outputs Results document with electrical characteristics of the sample-hold circuit.

Work Package Title Write software for sample-hold MCU testsReference Number PLM-PAY-WPSampleSoftware-035-1Length 1Cost £0.00Requirements OBDH development hardware, programmer.Pre-requisites PLM-PAY-WPSampleTestPlan-033-1, PLM-PAY-

LearnMCUProgramming-022-1Description Software must be written to enable the MCU to read and reset the

sample hold under test conditions. Again, since this is not flight software, it is the payload team’s responsibility.

Outputs Software for the MCU/sample-hold testing.

Work Package Title Integrate sample-hold with the MCU dev. board

of 47


Reference Number PLM-PAY-WPSampleIntMCUDev-035-1Length 0.5Cost £0.00Requirements Electronics lab space.Pre-requisites PLM-PAY-WPSampleBreadboard-032-1, PLM-PAY-

WPLearnMCUIntegration-023-1Description The Sample-hold breadboard must be electronically integrated with

the MCU development board.Outputs Integrated sample-hold and MCU, ready for testing.

Work Package Title Test the sample-hold MCU softwareReference Number PLM-PAY-WPSampleTestMCU-037-1Length 2Cost £0.00Requirements Electronics lab space, pulse generator, oscilloscope, logic analyser.Pre-requisites PLM-PAY-WPSampleIntMCUDev-036-1, PLM-PAY-

WPSampleTestPlan-033-1Description The test plan must be executed in collaboration with the OBDH

team, so that if the flight software is inadequate for controlling the sample-hold it can be modified.

Outputs Results document, tested and validated sample-hold design.

Work Package Title Acquire level shifter componentsReference Number PLM-PAY-WPShifterAcquire-038-1Length 0.5Cost £0.00Requirements Access to stores.Pre-requisites NoneDescription The level shifters used in the payload are electrical switches that

use 3.3V logic to switch on or off a 5V supply. The level shifter circuit has already been designed, but components must be acquired so that it can be breadboarded. The breadboards containing the sample-hold and DAC circuitry must be preserved, so a new board must be located for the level shifter.

Outputs Level shifter components.

Work Package Title Breadboard level shifter Reference Number PLM-PAY-WPShifterBreadboard-039-1Length 0.5Cost £0.00Requirements Electronics lab space.Pre-requisites PLM-PAY-WPShifterAcquire-038-1Description The level shifter circuit must be breadboarded according to the

circuit design.Outputs Level shifter breadboard.

of 47


Work Package Title Write level shifter test plan Reference Number PLM-PAY-WPShifterTestPlan-040-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription A test plan must be written; the level shifter will need to be tested

with a power supply and multimeter to determine its voltage and current characteristics.

Outputs Level shifter test plan.

Work Package Title Test level shifter circuitReference Number PLM-PAY-WPShifterBenchTest-041-1Length 2Cost £0.00Requirements Electronics lab space.Pre-requisites PLM-PAY-WPShifterTestPlan-040-1, PLM-PAY-

WPShifterBreadboard-039-1Description The test plan must be executed.Outputs Results document with current voltage characteristics of the level

shifter.

Work Package Title Design PPB flight upgradeReference Number PLM-PAY-WPPPBDesign-042-1Length 2Cost £0.00Requirements PLM-PAY-SoftwareInter-026Pre-requisites PLM-PAY-WPDACTest-029-1, PLM-PAY-WPSampleTestMCU-037-

1, PLM-PAY-WPShifterBenchTest-041-1Description The PPB is designed as a portable and human-readable MCP

detector interface, as well as a prototype of the circuitry that will be included on the flight model. It cannot be directly interfaced with the MCU for testing. However, using the breadboarded DAC, level shifter and sample-hold an interface can be made that will allow the MCU to take measurements using the PPB. The connections of this interface must be designed that emulates the flight design as closely as possible.

Outputs Upgraded PPB with attached breadboards.

of 47


Work Package Title Upgrade the PPB to flight prototype configurationReference Number PLM-PAY-WPPPBUpgrade-043-1Length 1Cost £0.00Requirements Electronics lab space.Pre-requisites PLM-PAY-WPPPBDesign-042-1Description The PPB is designed as a portable and human-readable MCP

detector interface, as well as a prototype of the circuitry that will be included on the flight model. It cannot be directly interfaced with the MCU for testing, however, using the breadboarded DAC, level shifter and sample-hold an interface can be made that will allow the MCU to take measurements using the PPB.

Outputs Upgraded PPB with attached breadboards.

Work Package Title Write test plan for PPB flight prototype configurationReference Number PLM-PAY-WPPPBFlightTestPlan-044-1Length 1Cost £0.00Requirements PLM-OBDH-Operations-215-2.docxPre-requisites NoneDescription The upgraded PPB does not have directly analogous electrical

connections to the flight model of the payload, but it should prove adequate for testing out the MCU flight code. A test plan must be written to simulate the in-flight use of the payload as closely as possible, granted that only one detector is supported by the PPB and the flight model will have two.

Outputs MCU-PPB test plan.

Work Package Title Integrate the PPB flight prototype with MCU development boardReference Number PLM-PAY-WPPPBIntMCUdev-045-1Length 1Cost £0.00Requirements Electronics lab space, OBDH development hardware.Pre-requisites PLM-PAY-WPPPBUpgrade-043-1Description The PPB must be integrated with the OBDH team’s MCU

development board. Some modification of the MCU software may be necessary to accommodate the test plan.

Outputs Integrated PPB-MCU hardware and software.

of 47


Work Package Title Test the PPB flight prototype with MCUReference Number PLM-PAY-WPPPBMCUTest-046-1Length 2Cost £0.00Requirements Electronics lab space, logic analyser, OBDH development

hardware, PPB flight prototype test plan.Pre-requisites PLM-PAY-WPPPBFlightTestPlan-044-1, PLM-PAY-

WPPPBIntMCUdev-045-1Description The test plan must be executed and the PPB must be able to

successfully respond to commands from the MCU.Outputs Results document.

Work Package Title Design circuit layout for flight boardReference Number PLM-PAY-WPFlightDesignCircuit-047-1Length 2Cost £0.00Requirements Payload team leader, Electronics specialist.Pre-requisites PLM-PAY-WPDACTest-029-1, PLM-PAY-WPSampleTestMCU-037-

1, PLM-PAY-WPShifterBenchTest-041-1, PLM-CAM-WPTestCircuit-709-1

Description The individual components of the flight circuitry will all have been validated at this point. These must be combined into a single diagram and board layout for two detectors, the ADCS board and a socket for the camera board and it’s electronics.

Outputs Flight board circuit diagram and layout.

Work Package Title Source components for the flight boardReference Number PLM-PAY-WPFlightAcquire-048-1Length 1Cost $1510Requirements Access to stores, contacts with AmpTek, EMCO, RECOM; Payload

team leader.Pre-requisites PLM-PAY-WPFlightDesignCircuit-047-1, PLM-PAY-

WPDustAnalyse-021-1Description A second set of AmpTek components, two more EMCO HV supplies

and two RECOM DC-DC converters must be purchased, and all other electronic components must be acquired as samples.

Outputs Flight board components.

Work Package Title Acquire hardware for the flight boardReference Number PLM-PAY-WPFlightAcquireHard-049-1Length 1Cost £0.00Requirements Access to stores, Payload team leaderPre-requisites PLM-PAY-WPFlightDesignCircuit-047-1Description The two Photonis filmed detector bodies, as well as cables to

connect them to the flight board, must be acquired.Outputs Flight payload hardware.

of 47


Work Package Title Vacuum powerup of flight MCPsReference Number PLM-PAY-WPFlightVerifyMCPs-050-1Length 3Cost £0.00Requirements Vacuum chamber equipment, possibly metalworking, NIM rack HV

supply and ammeter.Pre-requisites NoneDescription As with the last MCP, both of the flight MCPs must be powered up

in a vacuum chamber to with the NIM rack to ensure that they are stable. This may require modifications to the vacuum equipment.

Outputs Validated flight MCPs.

Work Package Title Construct final flight boardReference Number PLM-PAY-WPFlightBuild-051-1Length 2Cost ~£200.00Requirements PCB manufacturing facilities, OBDHPre-requisites PLM-PAY-WPFlightDesignCircuit-038-1, PLM-PAY-

WPFlightAcquire-039-1Description Duncan Ross, having seen our circuit diagram, will send it to a

manufacturing facility to be fabricated. The electronics specialists can then populate the board.

Outputs Populated payload flight board.

Work Package Title Write test plan for the flight board Reference Number PLM-PAY-WPFlightTestPlan-052-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription A test plan for verifying proper functioning of the flight board must

be written.Outputs Flight board test plan.

Work Package Title Integrate flight board with MCU development board Reference Number PLM-PAY-WPFlightIntMCUDev-053-1Length 1Cost £0.00Requirements OBDH development hardware, PLM-OBDH-Operations-215-2.docxPre-requisites PLM-PAY-WPFlightBuild-051-1Description The flight board must be integrated with the MCU development

board for electrical and software testing.Outputs Integrate flight board/MCU development board.

of 47


Work Package Title Test flight boardReference Number PLM-PAY-WPFlightTest-054-1Length 2Cost £0.00Requirements Electronics lab space, OBDH development hardware, logic

analyser, 1500V voltmeter.Pre-requisites PLM-PAY-WPFlightIntMCUDev-053-1, PLM-PAY-

WPFlightTestPlan-052-1Description The flight board must undergo testing with the flight code on the

bench before it can be integrated with the actual flight MCU.Outputs Flight board ready for assembly, integration and testing.

Work Package Title Document equipment and software available at NSCReference Number PLM-COMS-DocumentNSC-101-1Length 1Cost £16.00Requirements Transport to the NSCPre-requisites NoneDescription Arrange a time to go to the National Space Centre to inspect the

ground station equipment available there. Go and produce written documentation and photographs of what software and hardware is in use there. Compile this into single document.

Outputs Document describing the NSC equipment

Work Package Title Design command interface between NSC software and ground segment software

Reference Number PLM-COMS-DesignCmdInterf-102-1Length 1Cost £0.00Requirements Document describing the NSC equipmentPre-requisites PLM-COMS-DocumentNSC-101Description Design and document the command interface between the NSC

equipment documented previously, and the software that will be run on our ground segment computer. Specify how to change between transmitting and receiving.

Outputs Interface documentation

of 47


Work Package Title Design data interface between NSC software and ground segment software

Reference Number PLM-COMS-DesignDataInterf-103-1Length 1Cost £0.00Requirements Document describing NSC equipmentPre-requisites PLM-COMS-DocumentNSC-101Description Design and document the data interface between the NSC

equipment documented previously, and the software that will be run on our ground segment computer. Specify the data format(s) that will be used on the ground segment computer, and what hardware calls will be required to retrieve the signal.

Outputs Interface documentation

Work Package Title Implement interface between NSC software and ground segment software

Reference Number PLM-COMS-ImplementInterf-104-1Length 2Cost £0.00Requirements All interface documentationPre-requisites PLM-COMS-DesignCmdInterf-102, PLM-COMS-DesignDataInterf-

103Description Based on interface documentation, write and test the software that is

required by the ground segmentOutputs Functioning software that allows interface between NSC hardware

and ground segment.

Work Package Title Design FSK decoding softwareReference Number PLM-COMS-DesignFSK-105-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription Design and document software to demodulate the Frequency Shift

Keyed signal received by the ground segment. Verify the exact form of modulation in the signal, and produce simulated wave forms to test the code.

Outputs Design for FSK decoding software

of 47


Work Package Title Implement FSK decoding softwareReference Number PLM-COMS-ImplemntFSK-106-1Length 1Cost £0.00Requirements Design for FSK decoding softwarePre-requisites PLM-COMS-DesignFSK-105Description Design and document software to demodulate the Frequency Shift

Keyed signal received by the ground segment. Verify the exact form of modulation in the signal, and produce simulated wave forms to test the code.

Outputs FSK decoding software

Work Package Title Add FSK decoding software to ground segment softwareReference Number PLM-COMS-AddFSK-107-1Length 1Cost £0.00Requirements Ground segment software, FSK decoding softwarePre-requisites PLM-COMS-ImplementFSK-106, PLM-COMS-ImplementInterf-104Description Integrate decoding software to the ground segment software, and

test the integrated package. Convert a test wave form to a file and verify it against the original data used to produce the test wave form

Outputs Interface with integrated and tested decoding software

Work Package Title Design UI for ground segment softwareReference Number PLM-COMS-DesignUI-108-1Length 1Cost £0.00Requirements Ground segment softwarePre-requisites PLM-COMS-AddFSK-107Description Design a graphical user interface that enables students without

extensive knowledge of how the ground segment works to communicate with the satellite and retrieve data from it.

Outputs UI design documentation

of 47


Work Package Title Implement UI for ground segment softwareReference Number PLM-COMS-ImplementUI-109-1Length 1Cost £0.00Requirements UI design documentation, ground segment softwarePre-requisites PLM-COMS-DesignUI-108Description Implement the graphical user interface that has been designed, and

test both its functionality (by decoding a sample wave form) and its usability (by giving it to a user with no prior experience of the system to test)

Outputs Complete and tested UI

Work Package Title Design system test plan for ground segmentReference Number PLM-COMS-DesignTestPlan-110-1Length 2Cost £0.00Requirements Complete ground segment softwarePre-requisites PLM-COMS-ImplementUI-109Description Design and document a plan to test the entire ground segment

system. Include plans to produce test signals and any requirements this may have

Outputs System test plan

Work Package Title Implement system test plan for ground segmentReference Number PLM-COMS-ImplementTestPlan-111-1Length 3Cost £0.00Requirements Complete ground segment software, system test planPre-requisites PLM-COMS-DesignTestPlan-110Description Implement the system test plan for the ground segment and produce

documentation of the results. Correct any problems that are encountered and if needed repeat the test. Produce an analysis of the results showing the system is correct.

Outputs Table of results from test, and analysis of results.

of 47


Work Package Title Implement modesReference Number PLM-OBDH-Modes-201-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites NoneDescription In the main() subroutine in the main.c file (found on google code),

write a separate loop for each of the modes of the satellite. Include in each loop the condition for moving between modes. Include a normal square wave output (e.g. P1OUT=255-P1OUT) in each cycle of the loop) so that the logic analyser can tell if the code is functional. Remove this code when you are finished. Once the code successfully compiles and runs, commit changes to google code.

Outputs Code in main.c, logic analyser trace confirming functinoality

Work Package Title Implement action listReference Number PLM-OBDH-ActionList-202-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites PLM-OBSH-Modes-201Description In the main() subroutine in the main.c file (found on google code),

write code in the loop dealing with the Operation mode that will implement the action table. For each action there should be a status variable and a delay variable; if the status variable is nonzero the action is performed in each loop, if the status variable is zero the action is not performed. If the delay is nonzero, it is decremented each loop and when it reaches zero, the status variable is toggled between zero and nonzero (or the other way around). Write code to output a square wave to the logic analyser if certain actions are performed. Confirm functionality on logic analyser and then remove this code. Commit changes to google code.

Outputs Code in main.c, logic analyser trace confirming functionality

Work Package Title Implement the command responseReference Number PLM-OBDH-CmdResponse-203-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Debounced switch circuitPre-requisites PLM-OBDH-ActionList-202Description In the main.c file (found on google code), write an interrupt triggered

by an change on I/O Port 1, that using a global variable passes a signal to main(). Change modes upon receiving this signal, and also give an output readable by the logic analyser. Run the code on the board, and trigger a mode change using the debounced switch circuit, whilst the logic analyser is monitoring. Remove the outputting code, then commit changes to google code.

Outputs Code in main.c, logic analyser trace confirming functionality

Work Package Title Get commands from COMS

of 47


Reference Number PLM-OBDH-CmdCOMS-204-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

2 Modems, Attenuator, Aerial cable, PC to control modemPre-requisites PLM-OBDH-CMDResponse-203Description In the main.c file (found on google code), remove the interrupt that

sends signals to the main() subroutine, and instead place one in coms.c that sends the same signal when a signal is received by the transceiver. In main() put code to output a square wave when a signal is received. Use the two modems connected by the aerial capbles (via the attenuator), one modem connected to the development board and the other controlled by the PC, and send a signal to the board whilst checking the output with the logic analyser. Remove the square wave code, and commit changes to google code.

Outputs Code in main.c, coms.c, logic analyser trace confirming functionality

Work Package Title Implement SD power cycleReference Number PLM-OBDH-SDPower-205-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Multimeter, SD cardPre-requisites NoneDescription In the sd.c file (found on google code), write a wrapper for the

writing routine that minimises the amount of time the SD card spends powered on. In main.c, comment out mode loops and write code that writes any data to the SD card, waits for a time in the order of seconds, then flips I/O Port 1 and loops. Run the code whilst watching a pin of I/O Port 1 with the logic analyser, and whilst measuring the voltage on the pins of the SD card with the multimeter. Confirm the SD card receives no power when not being written to. Remove test code from main.c, uncomment mode loops, and commit changes to google code.

Outputs Code in sd.c, logic analyser trace and multimeter readings

of 47


Work Package Title Write log packetReference Number PLM-OBDH-LogPacket-206-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

SD card, PC with SD card readerPre-requisites PLM-OBDH-SDPower-205Description In the main() subroutine in the main.c file (found on google code), in

the Operation loop enter some code to call the logging subroutine in log.c whenever the appropriate status variable in the action table is set. Comment out the other mode loops so the code goes straight into operations mode. Add code before the loop to set the logging status. Insert the SD card into the development board and run the code, then using the card reader, check the SD card contains log data. Remove the code setting the action table, and uncomment out the rest of the mode loops. Commit the changes to google code

Outputs Code in main.c, SD card data to confirm functionality

Work Package Title Write minilog packetReference Number PLM-OBDH-MiniLog-207-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites NoneDescription In the main() subroutine in the main.c file (found on google code), in

the Operation loop enter some code to call the minilog subroutine in log.c whenever the appropriate status variable in the action table is set. Comment out the other mode loops so the code goes straight into operations mode. Add code before the loop to set the minilog status, and code within the loop to flip I/O Port 1 when the minilog routine completes in each loop. Use the logic analyser to monitor Port 1 and confirm the minilog function is being called. Remove the code setting the action table, and uncomment out the rest of the mode loops. Commit the changes to google code

Outputs Code in main.c, Logic analyser trace

of 47


Work Package Title Establish power up criteriaReference Number PLM-OBDH-PowerCrit-208-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription Elicit information from PSU documentation and PSU team members

as to what criteria will be used to determine whether or not a subsystem can be powered without compromising the satellite. Using the list of commands provided by the PSU team, determine how the OBDH should discover whether or not this criterion is met and the exact sequence of commands required for this.

Outputs Documentation describing the power up criteria and how they are to be implemented in code, including specific commands that must be sent across the I2C bus.

Work Package Title Inidividual power upsReference Number PLM-OBDH-PowerUps-209-1Length 3Cost £0.00Requirements Development Board, Programming tools, Compiler, Logic analyser,

PC which can simulate an I2C slavePre-requisites PLM-OBDH-PowerCrit-208, PLM-OBDH-I2CSend-210, PLM-

OBDH-I2cInter-211Description In the recover.c file (found on google code) add a subroutine to

retrieve via the I2C bus the information required by the criteria specified in PLM-OBDH-PowerCrit-208. Then add code to power up each subsystem depending on if the evaluation of the criteria deems it safe. Have the power up status of each subsystem be transmitted in a separate pin of I/O Port 1. Connect the development board to the I2C simulator, and monitor the pins of I/O Port 1 with the logic analyser. Program a script on the PC to reply to each I2C request with a value that can be typed in for test run. For each run, reset the board and use the logic analyser to see which systems are turned on. Once the test is complete, remove the code that outputs on I/O Port 1 and commit the changes to google code

Outputs Table of data relating simulated PSU outputs to the systems that are turned on. Detailed analysis of this data showing that response of code matches the previously specified criteria.

of 47


Work Package Title I2C connection to I2C simulatorReference Number PLM-OBDH-I2CSimulator-241-1Length 3Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

I2C simulatorPre-requisites NoneDescription Insert code into i2c.c that sends an i2c command, and code that

generates an interrupt when an i2c signal is received. Comment out the mode loops in main.c, and insert code the continually sends a predetermined i2c command. Connect the development board to the i2c simulator, and check that it responds in the expected way. Alter the command in the code, and repeat the test. Document in each case the command used and the response generated.Insert test code into i2c.c that writes data received to I/O Port 1. Send i2c signals to the board from the simlulator, and use the logic analyser to ensure that the data received is the same as the data sent. Repeat this for different test data and document the results Remove the test code in main.c and i2c.c, uncomment out the mode loops and commit changes to google code

Outputs Code in i2c.c, documentation of test

Work Package Title Send I2C command to PSUReference Number PLM-OBDH-I2CSend-210-1Length 3Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Laminar flow cabinet, PSU flight hardware, Multimeter, Cleaning equpment

Pre-requisites NoneDescription This work package involves hardware that must be kept clean, so

abide by the flight hardware procedures in the OBDH operations manual PLM-OBDH-Operations-215In the main() subroutine in the main.c file, comment out the mode loops and insert a call that sends an I2C signal telling the PSU to output in a certain way (see PSU documentation for details) and then enter an infinite loop that sends a square wave to I/O Port 1. Insert the flight hardware into the development board, connect the probes of the logic analyser to any pins of I/O Port 1, and verify the code is running. Use the multimeter to measure the output of the PSU board, and note it down. Repeat this for all the different commands that can produce measurably different outputs from the PSU board.Remove the test code in main.c, uncomment out the mode loops and commit changes to google code

Outputs Verified code in i2c.c, Table of data from the experiment, Analysis of the data.

Work Package Title I2C Interrupt with PSUReference Number PLM-OBDH-I2CInter-211-1Length 2

of 47


Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Laminar flow cabinet, PSU flight hardware, Regulated power supply, Cleaning equipment

Pre-requisites PLM-OBDH-I2CSend-210Description This work package involves hardware that must be kept clean, so

abide by the flight hardware procedures in the OBDH operations manual PLM-OBDH-Operations-215In the I2C.c file, write an interrupt that flips I/O Port 1 when an signal is received on the I2C bus indicating a change in power status (see PSU documentation for more details). Insert the flight hardware into the development board; connect the probes of the logic analyser to any pins of I/O Port 1. Connect the regulated power supply to the board and while monitoring the logic analyser initiate the change that should trigger the interrupt. Repeat this process for all possible conditions the PSU could generate. Then remove the I/O Port 1 output code and commit the changes to google code.

Outputs Verified code in i2c.c, Table of data from the experiment, Analysis of the data

Work Package Title Implement modem commandsReference Number PLM-OBDH-ModemCmd-212-1Length 3Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites NoneDescription In the modem.c file, write a subroutine that sends to the modem

commands to sleep, wake, and any other commands required (see COMS documentation), the command being selected by a parameter of this subroutine.In the main() subroutine in the main.c file, comment out the mode loops and insert a loop that continuously calls the modem command subroutine with a continuous value. Run this code on the development board and record the logic analyser trace. Repeat this with all the commands implemented, recording the results each time.Uncomment the mode loops in main(), remove the loop that calls the modem command subroutine, and commit the changes to google code.

Outputs Code in modem.c, logic analyser traces confirming each command

Work Package Title Implement modem interruptReference Number PLM-OBDH-ModemInter-213-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

WirePre-requisites PLM-OBDH-ModemInter-213Description In the modem.c file, write an interrupt that is triggered when a signal

is detected on the modem pins, and initiates a square wave on I/O

of 47


Port 1.Run this code on the development board, and generate a signal on modem pins by connecting them to the 5V output on the board’s surface. Use the logic analyser to check the square wave appears. Remove the code that generates the square wave, and commit the changes to google code.

Outputs Logic analyser trace, code in modem.c

of 47


Work Package Title SD card hash functionReference Number PLM-OBDH-SDHashFunc-214-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler Logic analyser,

SD card, PC with SD card reader.Pre-requisites NoneDescription In sd.c, write subroutines to calculate a hash based on a block of

data being written to the card, and then write it to a specific location on the card. In the main() subroutine in main.c, comment out the mode loops and insert code that writes a block of data containing human-readable text to the SD card, and then enters and endless loop outputting a square wave on I/O Port 1. Run this on the development board, with an SD card in place, and check the square wave appears on the logic analyser.Remove the SD card and read both the block of data written, and the hash with a hex editor. Confirm the hash function works as intended. Remove the code producing the square wave, uncomment out the mode loops, and commit the changes to google code.

Outputs Logic analyser trace, SD card data, SD card hash, Analysis of the two showing correct functionality.

Work Package Title Implement temperature samplingReference Number PLM-OBDH-TempSample-215-1Length 1Cost £0.00Requirements Development board, Programming tools, CompilerPre-requisites NoneDescription In the adc_sample() subroutine in the adc.c file, add code which,

based on the argument received, samples from the temperature sensor instead of one of the adc inputs.In the main() subroutine in the main.c file, comment out the mode loops and add a never ending loop that samples the temperature using the above subroutine, and then writes that value to I/O Port 1.Run the code, verify that the temperature reading being produced is realistic using the logic analyser trace, then remove the testing code from main.c, uncomment out the mode loops, and commit the changes to google code

Outputs Logic analyser trace, code in adc.c

of 47


Work Package Title Implement ax.25Reference Number PLM-OBDH-AxTwoFive-216-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Development

modem, Logic analyser.Pre-requisites NoneDescription In coms.c, program a subroutine to send ax.25 commands over the

modem. Comment out the mode loops in the main() subroutine in main.c, and write in a loop that repeatedly calls the above subroutine, with the same value.Interface the development modem with the board, run this program, and use the logic analyser to monitor the output of the modem and confirm transmission. Repeat this for all ax.25 commands. Remove the test code from main(), uncomment out the mode loops, and commit the changes to google code.

Outputs Logic analyser trace for each command, code in coms.c

Work Package Title COMS packet transmissionReference Number PLM-OBDH-COMSPacketTx-217-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Development

modem, logic analyser.Pre-requisites PLM-OBDH-ModemCmd-212, PLM-OBDH-AxTwoFive-216Description In coms.c, write a subroutine to read a block from the SD card, and

send that block over the modem then return a value depending on whether or not the modem reported success. In the main() subroutine in the main.c file, comment out the mode loops and enter code to send a block of data and then enter an infinite loop outputting a square wave on I/O Port 1.Run the code on the development board, and use the logic analyser to monitor the square wave and confirm the code has run. Remove the extra code from main.c, uncomment out the mode loops, and commit the changes to google code

Outputs Logic analyser trace, code in coms.c

Work Package Title Command verificationReference Number PLM-OBDH-CmdVerify-218-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites NoneDescription On a PC, write a subroutine that compares a 32 bit input against a

list of permissible commands. Test this on its own.Transfer this code into main.c, place an infinite loop producing a square wave on I/O Port 1 in that loop, and then check with the logic analyser that the subroutine runs. Remove the square wave loop and commit the changes to google code.

Outputs Logic analyser trace, code in main.c

of 47


Work Package Title Camera image retrievalReference Number PLM-OBDH-CamImage-219-1Length 3Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Development camera, SD cardPre-requisites NoneDescription Write code in camera.c to pull data from the development camera

then invoke sd.c to write it to the SD card. Write an infinite loop at the end of this code that outputs a square wave to I/O Port 1. In main() in main.c, add code that keeps ‘take photo’ in the action table.Insert the SD card into the development board and plug in the camera. Run the code and verify it is running with the logic analyser. Remove the square wave code from camera.c and the action table code from main.c, and commit to google code

Outputs Logic analyser trace, code in camera.c

Work Package Title Implement ADILReference Number PLM-OBDH-ADIL-220-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Development camera, SD card, handheld camera.Pre-requisites PLM-OBDH-CamImage-219Description Write code in camera.c to implement bright pixel counting. Write

code in main() in main.c to infinitely loop, whilst retrieving camera images and analysing them with ADIL. Have the loop output a square wave on a different pin of I/O Port 1 depending on whether or not the image passes inspection.Insert the SD card into the board, plug in the modem and connect the logic analyser to the pins of I/O Port 1. Point the camera at various light and dark images to verify function. Take a photo of the development cameras target with a separate camera in order to document its function.Remove the extra code from main.c, and commit changes to google code.

Outputs Code in camera.c, Logic analyser traces with corresponding photos of camera target.

of 47


Work Package Title Cosine transformReference Number PLM-OBDH-CamDCT-221-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites NoneDescription On a PC, write a subroutine that performs a Discrete Cosine

transform on an 8x8 matrix, using a lookup table. Write a program around this subroutine that allows you to manually enter values and see how they are transformed. Verify it is mathematically correct.Transfer the subroutine for the DCT and the definition of the lookup table into camera.c, then check that the code still compiles and runs on the board. Commit changes to google code

Outputs Code in camera.c, text file showing mathematically correct function of DCT. DCT testing code.

Work Package Title Implement JPEG compressionReference Number PLM-OBDH-CamJPEG-222-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Development Camera, SD cardPre-requisites PLM-OBDH-CamDCT-221Description In the code used to test the DCT routine, add the rest of the JPEG

compression algorithm, and replace manual entry of data with entry of data from a file. Using a graphics package such as GIMP, create a .raw image file, and have the program compress it. Check the output is a valid JPEG file.Transfer the code into camera.c, place a square wave loop in main.c and insert ‘take photo’ into the action table. Insert the SD card, plug in the camera, and run the code. Check with logic analyser that it runs correctly. Remove the additional code from main.c and commit changes to google code.

Outputs Logic analyser trace, JPEG test code, processed image files

of 47


Work Package Title Payload data retrievalReference Number PLM-OBDH-PayData-223-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Regulated power supplyPre-requisites NoneDescription Write code in in interrupt in pay.c that uses ADC.c to sample data

from the pins used for payload data and converts it to digital data then outputs this digital data across the unused I/O Ports. Using the logic analyser to read the digital output, a 3.3V stablised power supply to trigger the interrupt, and the power supply to produce an analogue input (taking care not to exceed the current and voltage the board is designed for of course) make a table of data showing how input voltages map to data values. Remove the extra code from main.c, and commit changes to google code.

Outputs Logic analyser traces, table of analogue to digital conversions

Work Package Title Payload initialisationReference Number PLM-OBDH-PayInit-224-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Payload development hardware, Payload team membersPre-requisites NoneDescription Write code in recover.c that goes through the steps specified in the

payload interface documents to initialise the payload. In main() in main.c, add code that calls the power up routine and then enters and infinite loop outputting a square wave on I/O Port 1.Plug the payload development hardware into the development board, attach a logic analyser to the pins of I/O Port 1 and run the code. Monitor the payload development hardware as directed to by the payload team. Remove extra code from main.c and commit changes to google code

Outputs Logic analyser trace, code in recover.c, data from payload team

of 47


Work Package Title Camera sun shutdownReference Number PLM-OBDH-CamSun-225-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

I2C simulator, Development cameraPre-requisites PLM-OBDH-CamImage-219, PLM-OBDH-I2CInter-211, PLM-

OBDH-I2CSend-210Description Write code in camera.c to invoke i2c.c and check with the PSU the

power level on the solar panel on the +Z face of the satellite. Calculate a threshold power (corresponding to a level of illumination on the +Z face that could damage the camera) and write code to abort any camera routine if the power from the solar panel is above that threshold, and return a value indicating failure.In main() in main.c, comment out the mode loops and enter code constantly samples from the camera and, depending on success or failure, writes a square wave to different pins of I/O Port 1. Using the I2C simulator to send simulated power data back to the board, run the code and note the mapping between power data and the logic analyser traces. Remove the additional code from main.c and commit the changes to google code

Outputs Code in camera.c, table of data showing solar panel power/camera status relationship.

Work Package Title SD card physical securityReference Number PLM-OBDH-SDGlue-226-1Length 1Cost £10.00Requirements Spare SD card (any capacity, cheapest available), epoxy supplied

by SRC, metal surface, good quality digital cameraPre-requisites NoneDescription With help from SRC staff, determine the right kind of epoxy for

securing the SD card whilst in space, and obtain some of this. Place a small bead of It on top of the SD card, and then attach it to the metal surface. Allow the epoxy to harded for 24 hours, and then take a close up photo of the resultant stake. Then find out if there are any ways to test the strength of this bond and carry them out.

Outputs Notes on correct epoxy to use, photo of stake produced. Results of any strength test.

of 47


Work Package Title SD card write latch securityReference Number PLM-OBDH-SDLatch-227-1Length 1Cost £10.00Requirements Spare SD card (any capacity, cheapest available) with a write

protect latch, epoxy supplied by SRC, good quality digital camera, Development board

Pre-requisites NoneDescription Acquire an appropriate epoxy from the SRC and, ensuring the write

protect latch of the card is in the ‘write enabled’ position, place a very small bead of epoxy in the gap the latch would have to move into in order to become ‘write protected’. Allow this to harden for 24 hours, and then take a close up photograph of it. Ensure that, with this modification, the SD card will still slide into the development board slot easily.

Outputs Photo of bead used to fix write protect latch.

Work Package Title Integrate SD card with flight hardwareReference Number PLM-OBDH-SDIntegration-228-1Length 1Cost £100.00Requirements Industrial grade SD card with 2Gb capacity, cleaning equipment,

OBDH flight hardware, epoxy supplied by SRC, clean room, small clamp suitable for work on flight hardware, knife, camera

Pre-requisites PLM-OBDH-SDGlue-226, PLM-OBDH-SDLatch-227Description Purchase the industrial SD card, move it into the clean room and

the clean it under the supervision of SRC staff. Using epoxy supplied by the SRC, and referencing the photos taken of the previous tests, epoxy the latch in the write enabled position. Leave to harden for 24 hours and then return to the clean room. Check that the industrial SD card can be inserted into the flight hardware and if not, remove excess epoxy with knife.Insert SD card in flight hardware, clamp in place gently, and referencing the photos of the test apply a small bead of epoxy to the top of the SD card, between the card and the metal holder (NOT between the SD card and the PCB). Allow hardening for 24 hours, then removing the clamp and inspecting to ensure SD card makes contact. If not, extract SD card with knife and try again. Take close up photographs of the integrated card

Outputs SD card fixed into flight board, photographs of stakes

of 47


Work Package Title Test PayloadReference Number PLM-OBDH-TestPayload-242-1Length 4Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

SD card, Payload development hardware, Payload team membersPre-requisites PLM-OBDH-PayData-223, PLM-OBDH-PayInit-224Description Write code that uses the payload initialisation and data subroutines

to power up the payload development hardware, and in response to interrupts from it, retrieves data and stores it on the SD card. Have the payload team generate a number of simulated signals in the development hardware and then create a table of inputted signals and outputted data.

Outputs Test results for payload

Work Package Title Test MPLReference Number PLM-OBDH-TestMPL-229-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites PLM-OBDH-Modes-201, PLM-OBDH-ActionList-202, PLM-OBDH-

CmdResponse-203Description Perform Main Programme Loop test. See PLM-OBDH-TestPlan-206

document for detailsOutputs Test results for MPL

Work Package Title Test SDReference Number PLM-OBDH-TestSD-230-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

SD card, PC capable of reading SD cardsPre-requisites PLM-OBDH-SDPower-205Description Perform SD card test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for SD card

Work Package Title Test ADCSReference Number PLM-OBDH-TestADCS-231Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

ADCS development hardware, SD card, PC capable of reading SD cards

Pre-requisites PLM-OBDH-TestSD-230Description Perform ADCS test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for ADCS

of 47


of 47


Work Package Title Test CameraReference Number PLM-OBDH-TestCam-232-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Development camera, SD card, PC capable of reading SD cardsPre-requisites PLM-OBDH-CamImage-219, PLM-OBDH-ADIL-220, PLM-OBDH-

CamDCT-221, PLM-OBDH-CamJPEG-222, PLM-OBDH-TestSD-230, PLM-OBDH-TestTime-234

Description Perform camera test. See PLM-OBDH-TestPlan-206 document for details

Outputs Test results for camera

Work Package Title Test LoggingReference Number PLM-OBDH-TestLog-233-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

SD card, PC capable of reading SD cardsPre-requisites PLM-OBDH-TestSD-230, PLM-OBDH-LogPacket-206, PLM-OBDH-

MiniLog-207, PLM-OBDH-TestMPL-229Description Perform logging test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for log

Work Package Title Test TimingReference Number PLM-OBDH-TestTime-234-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyserPre-requisites NoneDescription Perform timing test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for timing

of 47


Work Package Title Test ModemReference Number PLM-OBDH-TestModem-235-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Development modems, PCPre-requisites PLM-OBDH-ModemCmd-212, PLM-OBDH-ModemInter-213Description Perform modem test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for modem

Work Package Title Test ComsReference Number PLM-OBDH-TestComs-236-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Development modems, PCPre-requisites PLM-OBDH-AxTwoFive-216, PLM-OBDH-COMSPacketTx-217,

PLM-OBDH-TestModem-235, PLM-OBDH-TestSD-230Description Perform coms test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for coms

Work Package Title Test PSUReference Number PLM-OBDH-TestPSU-237-1Length 1Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Regulated power supply, Multimeter, Laminar flow cabinetPre-requisites PLM-OBDH-I2CInter-211, PLM-OBDH-I2CSend-210Description Perform PSU test. See PLM-OBDH-TestPlan-206 document for

detailsOutputs Test results for PSU

of 47


Work Package Title Development hardware testReference Number PLM-OBDH-TestDev-238-1Length 6Cost £0.00Requirements All available development hardware, Development board,

Programming tools, Compiler, Logic analyser, SD card, PC capable of reading SD cards

Pre-requisites PLM-OBDH-TestMPL-229, PLM-OBDH-TestSD-230, PLM-OBDH-TestADCS-231, PLM-OBDH-TestCam-232, PLM-OBDH-TestLog-233, PLM-OBDH-TestTime-234, PLM-OBDH-TestModem-235, PLM-OBDH-TestComs-236, PLM-OBDH-TestPSU-238

Description Test the OBDH with all other development hardware at once, where available. See PLM-OBDH-TestPlan-206 document

Outputs Complete set of interface test results

Work Package Title Programming flight hardwareReference Number PLM-OBDH-Program-239-1Length 2Cost £0.00Requirements Flight hardware, Programming tools, Compiler, clean room, cleaning

equipment.Pre-requisites PLM-OBDH-TestDev-238, PLM-OBDH-SDIntegration-228Description Transport programming hardware into the clean room, and ensure

that the connectors that will contact the flight hardware are cleaned. Connect the flight hardware to the programming hardware, and upload the code. The software that accompanies the programming hardware will inform of success/failure

Outputs Flight hardware with code on board.

Work Package Title Verifying flight hardware programReference Number PLM-OBDH-TestFlight-240-1Length 1Cost £0.00Requirements Flight hardware, clean room, cleaning equipment, logic analyser,

regulated power supplyPre-requisites PLM-OBDH-Program-239Description Transport the equipment needed into the clean room, and clean any

parts of it that will contact the flight hardware.Carefully check the regulated power supply is set to an appropriate voltage and current for the board, and then connect it to the +5V and GND pins of the flight board. Connect logic analyser probes to the transceiver pins, and then remove the “remove before flight” pin and ensure the launch switch is not pressed. The satellite will, if programming has been successful, turn on and attempt to power up the transceiver.

Outputs Logic analyser trace verifying programming

Work Package Title Design battery/board integration test planReference Number PLM-PSU-DesignBBInterf-301-1

of 47


Length 2Cost £0.00Requirements NonePre-requisites NoneDescription Design and document a plan to test electronic and mechanical

integration between battery and board. Include all procedures for handling flight hardware in laminar flow cabinet.

Outputs Battery/board integration test plan

Work Package Title Implement battery/board integration test planReference Number PLM-PSU-ImplementBBInterf-302-1Length 1Cost £0.00Requirements PSU board and two lithium polymer batteries (all flight hardware),

Laminar flow cabinet, gloves.Pre-requisites PLM-PSU-DesignBBInterf-302-1Description Carry out the battery/board integration as documented, recording

actions taken and all data Outputs Integration test data

Work Package Title Test I2C commands from OBDHReference Number PLM-PSU-TestI2CCmd-303-1Length 3Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Laminar flow cabinet, PSU flight hardware, Multimeter, Cleaning equpment

Pre-requisites NoneDescription Coordinating with OBDH team, verify that I2C commands can be

sent to and acted upon by the PSU board. For details, see PLM-OBDH-I2CSend-210 work package.

Outputs Table of data from the experiment, Analysis of the data.

of 47


Work Package Title Test I2C data to OBDHReference Number PLM-PSU-TestI2CData-304-1Length 2Cost £0.00Requirements Development board, Programming tools, Compiler, Logic analyser,

Laminar flow cabinet, PSU flight hardware, Regulated power supply, Cleaning equipment

Pre-requisites PLM-PSU-TestI2CCmd-303Description Coordinating with OBDH team, verify that the PSU board can send

data to the OBDH development board over the I2C bus. For details, see PLM-OBDH-I2CInter-211 work package

Outputs Table of data from the experiment, Analysis of the data

Work Package Title Specify solar array layout and geometryReference Number PLM-PSU-SolarLayout-305-1Length 2Cost £0.00Requirements Access to 3D modelling and technical drawing software (either

personally or through university staff)Pre-requisites NoneDescription Determine, with reference to documentation for other subsystems

and management, what gaps need to be left in the solar panels. Either produce 3D models and technical drawings, or give specifications to staff who can do this.

Outputs 3D models and technical drawings of all solar panels

Work Package Title Design solar array mechanical interfaceReference Number PLM-PSU-SolarMechInterf-306-1Length 2Cost £0.00Requirements Existing cubesat mechanical documentationPre-requisites NoneDescription Design and document the interface between the solar panels and

the frame of the satellite, taking care to keep the interface consistent with existing documentation.Determine what if any additional steps will be taken to secure solar panels to satellite frame.

Outputs Mechanical interface documentation

of 47


Work Package Title Purchase solar arrayReference Number PLM-PSU-GetSolar-307-1Length 1Cost Approximately £15,000Requirements MoneyPre-requisites PLM-PSU-SolarLayout-305Description Send the technical drawings of the solar panels to the manufacturer

and arrange for them to be paid. Make arrangements to receive solar panels and write down procedure to transport them directly into the clean room. Take delivery of solar panels and put them in the clean room.

Outputs Delivered solar panels

Work Package Title Design solar array electrical interfaceReference Number PLM-PSU-SolarElecInterf-308-1Length 2Cost £0.00Requirements Existing cubesat mechanical and electrical documentationPre-requisites NoneDescription Determine and document which electrical connections need to be

made between the solar panels and the board, and the characteristics of those electrical connectionsDetermine, with reference to documentation, what route the wires connecting the solar panels to the PSU board will take through the satellite

Outputs Electrical interface documentation

Work Package Title Design Integration PlanReference Number PLM-PSU-DesignIntegration-309-1Length 2Cost £0.00Requirements NonePre-requisites PLM-PSU-GetSolar-307, PLM-PSU-SolarElecInterf-308, PLM-PSU-

SolarMechInterf-306, PLM-PSU-TestI2CData-304, PLM-PSU-SolarLayout-305

Description Design a plan for integrating the PSU flight hardware into the satellite frame and OBDH board. This plan must include procedures for using the clean room, and for transporting necessary equipment there and cleaning it if it is to come into contact with flight hardware.All actions to be performed in the clean room must be enumerated in the document, so they can be checked off as they are performed.

Outputs Integration plan

of 47


Work Package Title Integrate solar arrayReference Number PLM-PSU-IntegrateSolar-310-1Length 3Cost £0.00Requirements PSU flight hardware, Solar panels, OBDH flight hardware, clean

room, Integration planPre-requisites PLM-PSU-DesignIntegration-309Description Verify the integration plan is correct with SRC staff, and then

implement it. Check off all steps in the integration plan as they are performed, and have one student photograph the procedure.

Outputs Integrated hardware, photographs and documentation of integration.

Work Package Title Design integrated solar array test planReference Number PLM-PSU-DesignSolarTest-311-1Length 2Cost £0.00Requirements NonePre-requisites NoneDescription Design and document a plan to test the solar panels once they have

been integrated to the flight hardware. Pay attention to the requirements of working in the clean room. All actions to be performed in the clean room must be enumerated in the document, so they can be checked off as they are performed.

Outputs Integrated solar array test plan

Work Package Title Integrate solar arrayReference Number PLM-PSU-IntegrateSolar-312-1Length 4Cost £0.00Requirements PSU flight hardware, Solar panels, OBDH flight hardware, clean

room, Integrated solar array test planPre-requisites PLM-PSU-DesignSolarTest-311, PLM-PSU-IntegrateSolar-310Description Verify the integrated solar array test plan is correct with SRC staff,

and then implement it. Check off all steps in the test plan as they are performed. Have one student recording data and another photographing the procedure

Outputs Documentation of test, test data, photographs

of 47


Work Package Title Determine software configuration for cameraReference Number PLM-CAM-WPSoftwareConfig-701-1Length 1Cost £0.00Requirements OV7640 manual, SCCB manualPre-requisites NoneDescription The OmniVision OV7640 is a camera designed for use with modern

desktop computers. The flight MCU has far inferior processing power to such machines, and in a default setup the camera board outputs data far too fast for the MCU to be able to read it. However, the camera board is controlled by a microprocessor which has functions that can slow down the camera’s data output significantly. A software configuration for this microprocessor must be found so that the camera and OBDH can communicate.

Outputs Camera board software configuration

Work Package Title Camera standalone powerupReference Number PLM-CAM-WPStandalonePowerup-702-1Length 1Cost £0.00Requirements NonePre-requisites NoneDescription The OV7640 can be connected to a desktop computer using a USB

interface board. This component will not accompany the satellite into orbit, so the functionality it provides must be replicated using in-house electronics before any meaningful integration or programming work can be carried out. At the completion of this WP the camera board should be set up to operate fully independently of the USB interface board.

Outputs Camera board electronics configuration, working camera prototype board

Work Package Title Integrate camera with MCU dev. board Reference Number PLM-CAM-WPIntMCUDev-703-1Length 2Cost £0.00Requirements OBDH development hardware, PLM-OBDH-Operations-215-2.docxPre-requisites PLM-CAM-WPStandalonePowerup-702-1Description The OV7640 must be physically integrated with the OBDH board,

such that signals from one can be read by the other, before any further testing can take place.

Outputs Integrated MCU/camera board

Work Package Title Test image acquisitionReference Number PLM-CAM-WPTestImage-704-1Length 3Cost £0.00Requirements Electronics lab space, OBDH development hardware, logic

analyser.Pre-requisites PLM-CAM-WPIntMCUDev-703-1

of 47


Description The code for image acquisition is the responsibility of the OBDH team. Once the camera is integrated with the development board and powered from an external supply, it will be electronically identical to the flight configuration and should be able to run the same software. The camera must be placed in the correct software mode as determined in PLM-CAM-WPSoftwareConfig-701-1 and an image must be acquired.

Outputs Results document including camera test image.

Work Package Title Acquire flight cameraReference Number PLM-CAM-WPGetFlightCam-705-1Length 1Cost £0.00Requirements Omnivision contact.Pre-requisites NoneDescription Omnivision give their camera boards for free for educational

purposes. A new OV7640 camera board should be sent for to act as flight model.

Outputs Flight camera board.

Work Package Title Calibrate camera lensReference Number PLM-CAM-WPCalibrateLens-706-1Length 0.5Cost £0.00Requirements Workshop space, engineering supervision.Pre-requisites PLM-CAM-WPGetFlightCam-705-1Description Omnivision supply the OV7640 with a lens made of materials

suitable for use in space. The lens must be mounted and glued into place on the camera board at the correct distance to produce in-focus images. If the lens is to be mounted flush with the board, then a small vent must be chiselled in the side of it to permit outgassing.

Outputs Vented lens assembly.

Work Package Title Construct shieldReference Number PLM-CAM-WPBuildShield-707-1Length 3Cost £10.00Requirements Workshop space, engineering supervision.Pre-requisites PLM-CAM-WPGetFlightCam-705-1Description The camera is a commercial component not designed for flight in

the high radiation environment of space. An aluminium enclosure for the camera lens half a millimetre thick should provide adequate protection. The enclosure must be light-tight, as the lens venting will introduce a light leak in the lens housing. This package includes the shield design and construction. A method of fixing the lens to the camera board must also be determined.

Outputs Aluminium shield.

Work Package Title Design camera support electronicsReference Number PLM-CAM-WPDesignCircuit-708-1

of 47


Length 2Cost £0.00Requirements NonePre-requisites NoneDescription The camera flight board will require at least two pieces of circuitry

on the flight board, a clock oscillator and an overcurrent protection circuit to detect latchup. The design of both of these must be finalized before the final circuit can be manufactured. This work package may be extended to include any extra electronics that the camera requires to run.

Outputs Camera circuit designs

Work Package Title Prototype camera support electronicsReference Number PLM-CAM-WPTestCircuit-709-1Length 2Cost £10.00Requirements Electronics lab space, OBDH development hardware, logic analyser.

Pre-requisites PLM-CAM-WPDesignCircuit-708-1Description The camera’s support electronics must be laid out and tested before

the circuit design can be finalized and the final payload board circuit diagram can be made.

Outputs Results document detailing performance characteristics of the camera support electronics

Work Package Title Electrical tests on the flight camera board Reference Number PLM-CAM-WPFlightTest-708-1Length 1Cost £0.00Requirements Electronics lab space, OBDH development hardware, logic

analyser.Pre-requisites PLM-CAM-WPGetFlightCam-705-1Description Electrical tests (including current drain and expected pin voltages as

well as image acquisition using the supplied camera USB interface) should be carried out to ensure the flight camera board is working properly.

Outputs Working flight camera board.

Work Package Title Integrate camera with payload flight board Reference Number PLM-CAM-WPIntFlightPayload-709-1Length 1Cost £0.00Requirements Cleanroom equipment, engineering supervision.Pre-requisites PLM-CAM-WPFlightTest-708-1, PLM-CAM-WPBuildShield-707-1,

PLM-CAM-WPCalibrateLens-706-1, PLM-PAY-WPFlightTest-043-1Description The camera flight board should be cleaned, integrated with the

vented lens and shield, and installed on the payload flight board.Outputs Combined camera/payload board.

of 47


of 47

cubesat.wdfiles.comcubesat.wdfiles.com/.../plm-man-wpbdescrip-517-4.docx · web viewusing the logic...

Documents