Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System Analysis: Other S/S Hard Reset #2

Open
2 of 6 tasks
chgio opened this issue Oct 20, 2022 · 2 comments
Open
2 of 6 tasks

System Analysis: Other S/S Hard Reset #2

chgio opened this issue Oct 20, 2022 · 2 comments
Labels
model-feature Functional modelling, at any level obc Within the scope of the On-Board Computer Subsystem

Comments

@chgio
Copy link
Member

chgio commented Oct 20, 2022

Existing diagrams to extend:

  • [MCB] System Capabilities:
    • add FDIR capability
  • [SFBD] Root System Function Breakdown
  • [SAB] System Architecture

(check comments)

New diagrams to create:

  • [ES] Subsystem Hard Reset Scenario:
    • some system failure state
    • placeholder for failure identification
    • note: failure characterisation as solvable by hardware reset only
    • tackled by hard reset signal GPIO -> RST line

Next steps:
when closing this issue, make a new issue out of the checkbox below:

@chgio chgio added model-feature Functional modelling, at any level obc Within the scope of the On-Board Computer Subsystem labels Oct 20, 2022
@chgio chgio changed the title OBC Scenario: Other S/S Hard Reset Other S/S Hard Reset Scenario Oct 20, 2022
@chgio chgio added this to the Other S/S Reset Capability milestone Oct 26, 2022
@chgio chgio changed the title Other S/S Hard Reset Scenario System Analysis: Other S/S Hard Reset Scenario Nov 2, 2022
@chgio chgio changed the title System Analysis: Other S/S Hard Reset Scenario System Analysis: Other S/S Hard Reset Nov 9, 2022
@chgio chgio modified the milestones: Other S/S Reset Capability, System-Wide FDIR Capability Dec 29, 2022
@chgio chgio assigned ZonaDashti and unassigned muhamedshaheenar Jan 13, 2023
@chgio chgio assigned Jstephenson808 and unassigned ZonaDashti Feb 3, 2023
@chgio
Copy link
Member Author

chgio commented Feb 3, 2023

just model a placeholder function for system failure and identification, to expand as part of #38
(use involved states to convey system failure)

@chgio
Copy link
Member Author

chgio commented Mar 21, 2023

at the System Analysis level, let's actually have a path to represent the telecommand/execution/report pattern, leading to "system does X" not unlike the fault identification placeholder:

  • operator issues X t/c
    • g/s sends X t/c
      • system receives X t/c
      • (switch to a Downlink mode: through change mode, collect telemetry -- thanks @muhamedshaheenar for pointing this out!)
      • system does X
      • system sends X report
    • g/s receives X report
  • operator interprets X report

at the other end of "system does X", a link to telemetry generation should also be made for when this function is triggered automatically and there is no option to immediately downlink the report.

muhamedshaheenar pushed a commit that referenced this issue Mar 28, 2023
in [SFBD] Root System Function Breakdown:
- add functions to issue, send and receive HR requests.
- add error detections post HR command execution
- add error report downlink request functions
- rename O-S/S to general HR for simplicity
- add two functional chains to denote telecommanded and automated
functions, hid them from view in the [SFBD]

create clones of main [SAB] to highlight those functional chains:
- [SAB] System Architecture View of hard reset commands
-highlighted the created funtional chains

Close #2
muhamedshaheenar added a commit that referenced this issue Mar 28, 2023
in [SFBD] Root System Function Breakdown:
- add functions to issue, send and receive HR requests.
- add error detections post HR command execution
- add error report downlink request functions
- rename O-S/S to general HR for simplicity
- rename FIP to mode change to prevent ambiguity and throwing an error
during validation
- add two functional chains to denote telecommanded and automated
functions, hid them from view in the [SFBD]

create clones of main [SAB] to highlight those functional chains:
- [SAB] System Architecture View of hard reset commands
-highlighted the created funtional chains

Close #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model-feature Functional modelling, at any level obc Within the scope of the On-Board Computer Subsystem
Projects
None yet
Development

No branches or pull requests

4 participants