search

JBmiog / QC-embedded

QUADCOPTERS
0 stars 2 forks source link

Data logging #14

Open makbut opened 7 years ago

makbut commented 7 years ago

We should implement data logging. Jeffrey declared interest

JBmiog commented 7 years ago

data loging discussion points

  1. data logging should be done in all modes
  2. data to be written to the storage includes: timestamp, mode, battery voltage, barometer, gyroscope, accelerometer
  3. logging should be done in round robbin fashion, overwrite oldest data first
  4. log when the connection with computer is lost
  5. keep open later modifications aimed towards logging received packets aswell.
  6. logging should not be done in a timer/interrupt, but based on a counter
JBmiog commented 7 years ago

Hey, it seems that we can only write data to empty spots on the memory. At the moment, we can only clear memory by erasing all data on the chip. If we do so, when do we clear the chip? When we leave safe mode? When do we decide to read the data from the chip? Maybe on a special key event?

JBmiog commented 7 years ago

Okey, in order to proceed implementation, I've chosen to erase the chip data upon leaving manual mode. On default, It dumps all data on startup. As this process takes a while, I'm thinking of adding a mode specially for dumping the data from flash to terminal, so then we can chose whether we want the data or not.

JBmiog commented 7 years ago

currently in branch drone_logging

JBmiog commented 7 years ago

according to the assignemnt, the following things should also be logged:

JBmiog commented 7 years ago

oke, we don't log the control parameters atm...