Ground Timeout Detection

[PokeyOne]

Description

Once the rocket is on the ground we should have a way for the Pi to stop logging information and cleanup active things. This is because the FC will be constantly writing data to BB, and if we were to just shut off FC, it may leave currupted data. Having FC stop logging after a certain amount of time would be ideal.

How to Detect

There are two main modes of detection that were discussed:

1. General timeout (for example, expected flight time + 10 minutes)
2. Detection of ground (plus a five minute buffer or something)

Acceptance Criteria

• Assess whether data curuption would even be a real issue.
• Assess and decide on the approppriate way to detect this.
• Implement detection
• Stop logging data some time after detection.
• There should be a buffer between detection and stopping logging.
• There should be a minimum time before it even considers stopping logging.
• It should only be able to stop loggin in the recovery state. It would be very bad if we just stopped logging in the middle of the burn.

[PokeyOne]

Also something I just thought about:

This might not be super important.

As far as I am aware there are only two types of data being stored:

1. Text (for the csv)
2. Images from cameras

The text can never really be currupted because it should just be appending, and the worst case is an unfinished row in the csv that we can manually edit.

For the images, if we are just storing images every certain period, we may just end up with one unfinished frame. This should leave the rest of the frames just fine.

So have this task might just be making things needlessly complicated.

[PokeyOne]

Following some discussion in the Discord:

This is probably still worth it in some form.

Another way we could do this is through detecting when the transmitter stops responding and then stop. This way we could just shut down the transmitter and then wait five seconds before turning off the pi.