Skip to content

Physical Architecture: Pipeline Mode Change Backpropagation #55

@chgio

Description

@chgio

Refine the current steps in the "Pipeline Mode Change" functional chain to reflect the actual implementation in compliance with the hardware constraints: I2C master-slave topology, etc.

Existing diagrams to extend:

  • [PFBD] Root Physical Function Breakdown
  • [PCBD] Root Physical Component Breakdown
  • [PFCD] Physical Functional Chain Description of Pipeline Mode Change
  • [PFCD] Physical Functional Chain Description of Telecommanded Mode Change
  • [PFCD] Physical Functional Chain Description of Auto Mode Change (Sensing Progress)
  • [PFCD] Physical Functional Chain Description of Auto Mode Change (Sensing Exit)
  • [PAB] Root Physical Architecture
  • [PAB] Physical Architecture View of Mode Changes
  • [PAB] Physical Architecture View of Telecommands
  • [PDFB] Functional Dataflow View of Mode Changes
  • [PDFB] Functional Dataflow View of Telecommands
  • [ES] Commanded Mode Change Physical Scenario

New diagrams to create:

  • [ES] Pipeline Mode Change Scenario:
    • OBC -> Pipeline: periodically check processing progress
    • Pipeline -> OBC: send processing progress
    • etc.
  • (Optional) [PDFB] Functional Dataflow View of Pipeline Mode Change
  • (Optional) [PAB] Physical Architecture View of Pipeline Mode Change

Metadata

Metadata

Labels

model-featureFunctional modelling, at any levelobcWithin the scope of the On-Board Computer SubsystemsystemOutside the scope of any single Subsystem

Type

No type

Projects

Status

No status

Relationships

None yet

Development

No branches or pull requests

Issue actions