Skip to content

Home

Jump to bottom Edit New page
kupsztal edited this page Oct 10, 2011 · 42 revisions

Welcome to the iTesa wiki!

Table of Contents

To Do and Status List

3rd Oct - 5th Nov

  1. Binary Data Storage (aj)
  2. Conceptual Designs (aj)
    • understand android data formats
  3. Database Profiling (jc)
    • ✔ Branch: jakub_preferences
    • ✔ OK. So far I found the bug that was causing the app to crash (bloody comma in SQL statement)
    • ✔ data saved : (timestamp, Bx, By, Bz)
    • TODO data saved: (timestamp, mag.|B|) GPS: (timestamp, GPS coords) Magnetometer (timestamp, |B|)
  4. App options (accuracy, delay rate etc) (jc)
    • ✔ Branch: jakub_preferences
    • ✔ implemented basic menu with preferences (UI update refresh rate). It doesn’t work as expected yet because of the way the timer is set.
    • TODO change the way UI is updated (run the sensor reading as Service)
  5. Plotting functionality - basic (jc)
    • TODO Branch: (none)
    • TODO write the code
  6. Merge the branches (jc)
  7. Test the app, review the code (aj/jc)

23 Sep - 3rd Oct

  1. setup repo on github (done)
  2. write magnetometer test - check values (done)
  3. freq of the measurement (do we actually have any numbers ? not that we need them but would be nice to have)

Additional

  1. Get more tech details from STRaND (5th Nov)
    • data analysis, statistics?
    • SDK version ? interface to the external hardware ?
  2. compare data storage latency
  3. profile code!
  4. calculate angle of sun based on time and GPS coords.
  5. work out what are the things like sensorManager.MAGNETIC_FIELD_EARTH_MAX/MIN, RAW_DATA_X/Y/Z, and other * sensorManager features

iTesa

Requirements

(see checklist)

  1. should be able to run for at least 90 mins w/o crashing or freezing
  2. sensor measurements should be decoupled from the UI update
  3. sensor measurements should be decoupled from the plot update
  4. plot update should be decoupled from the UI update
  5. option for selecting frequency of measurement/UI/plot updates
  6. the code should be flexible enough to be able to choose between sqlite database and raw file for data storage

Architecture

(see checklist)

"There are two basic rules for writing efficient code:
Don't do work that you don't need to do.
Don't allocate memory if you can avoid it.

Scientific(-ish) stuff

Git 

# built application files
*.apk
*.ap_

# files for the dex VM
*.dex

# Java class files
*.class

# generated files
bin/
gen/

# Local configuration file (sdk path, etc)
local.properties

# Eclipse project
.classpath
.project

Nexus One

Android

NDK

Tutorials

Eclipse integration

Accessing sensors in NDK

STRaND related

  • Submission Form - stuff we submitted
  • SSTL
  • STRaND Nanosatellite
  • s-android, Space Android: Android for Space Subsystems
  • Christopher P. Bridges - Dr. Christopher P. Bridges currently works for the Astrodynamics Group at Surrey Space Centre in the University of Surrey. He teaches in dynamics and control of spacecraft and digital design with VHDL. He is currently designing and building a visual inspection payload for a two satellite mission together with EADS Astrium who is designing a microelectromechanical (MEMS) thruster. He is currently the lead research engineer for STRaND, a CubeSat-based 3U nanosatellite with advanced AOCS systems and high performance computers. He is published in mobile-agents, middleware, multi/network softcore processors, distributed satellite systems, and CubeSats. *(wrote the Telemetry App)*
  • STRaND-1 Nanosatellite BBC (youtube)

Other interesting stuff

Add a custom footer
Add a custom sidebar
Clone this wiki locally