Currently if you deactivate a command pod or command chip with a running flight program the program continues running. I think if a command pod/chip is deactivated the flight program should terminate. When a deactivated command pod/chip is reactivated the flight program should restart (even if it previously exited on its own) as if the craft had just launched (i.e. there one running thread per start block), however values stored in variables should be preserved (thus allowing a flight program to have persistent storage between reboots).

Suggestion Submitted

1 Comment

  • Log in to leave a comment
  • Profile image
    311 zeropol

    It totally makes sense.
    The persistence of variables can be discussed I think, but I have no real argument.

    1.8 years ago


Log in in to upvote this post.