OHKLA Design/Avionics Controller

From CSTART Wiki

(Redirected from OHKLA Design/Controller)
Jump to: navigation, search

This page is part of an implementation of the CSTART Engineering Process. Anyone can edit it, but it should only be modified in accordance with the procedures and guidelines of the Process. Please check before editing if you are in doubt.

This document is a leaf node in the Design Task Tree for the OHKLA project.

Contents

[edit] Summary

The purpose of this design task is to select a controller for the avionic systems. This controller will collect data from the various sensors, store it, and trigger parachute release and radio transmission of coordinates under certain conditions.

[edit] Background

The OHKLA launch platform provides an ideal test bed for avionics sensors and controllers to be used in later, more ambitious projects. Additionally, certain control functions are needed to ensure proper rocket recovery. The avionics controller subsystem will provide these functions, and support the capture and storage of data from multiple sensors. To accomplish this, several design tasks will need to be completed, as show below.

  System Level Design 
      Identify and agree upon high level requirements
      Develop subsystem/item level functional descriptions
      Identify dependencies between subsystems
      Conduct a System level Functional Review to ensure that all requirements are addressed by the subsystem functions
  Item Level Design 
      Develop detailed subsystem/item level requirements based on the previously developed functional descriptions
      Evaluate commercially available products against the subsystem requirements
      Design any non-commercially available subsystems
      Conduct an item level Functional Review to ensure that all requirements are addressed by the component functions
  Detailed Design Review
  Fabrication, Integration, and Testing

[edit] Features/Considerations

[edit] Peripheral support

The central issue is peripheral support. The controller must support simultaneous connection of instances of the following peripherals:

  • GPS receiver
  • Inertial measurement units
  • Barometer
  • Magnetometer
  • Storage device (SD card / USB drive)
  • Radio transmitter
  • Control channel (for nose cone separation etc.)

[edit] Microprocessor

Microprocessor power is an issue to consider.

Does our choice of microprocessor place limitations on the languages in which we can write software? Are some processors better than other for open source software development?

[edit] Power requirements

Lower power requirements are better in that they facilitate smaller and hence less massive batteries.

[edit] Other requirements

The Avionics Controller, including any mounting, batteries, etc, must weight less then 1kg.

[edit] Available Solutions

[edit] Supporting material/calculations

Personal tools