Skip to content

Add CameraManager 1 and 2 implementations#8

Open
KR-1234 wants to merge 2 commits into
mainfrom
testBranch
Open

Add CameraManager 1 and 2 implementations#8
KR-1234 wants to merge 2 commits into
mainfrom
testBranch

Conversation

@KR-1234

@KR-1234 KR-1234 commented May 8, 2026

Copy link
Copy Markdown

Added Camera1Manager.md and Camera2Manager.md as Layer 2 hardware manager SDDs.

AryanTaywade and others added 2 commits May 6, 2026 23:47
…logy

- Add Camera1Manager.md and Camera2Manager.md: Layer 2 Active hardware
  manager SDDs following the flat SM pattern (OFF → RESET → WAIT_RESET →
  ENABLE → CONFIGURE → RUN). Cameras are command-driven (POWER_ON,
  POWER_OFF, CONFIGURE, CAPTURE via Fw.Cmd cmdIn) and push frames to
  DataCollectionApplication via Cam.ImagePort.
- Update DataCollectionApplication.md: add missing imageIn[2]: Cam.ImagePort
  input port to receive frames from both camera managers.
- Update sdd.md: correct camera manager SM descriptions to include OFF state,
  add Camera1Manager and Camera2Manager to RateGroup2 schedule, define
  Cam.ImagePort in synchronized capture section.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@h-badams

Copy link
Copy Markdown
Contributor

The overall architecture of Camera1 looks very reasonable to me. However, if it is truly the case that Camera1 and Camera2 are identical as you suggest in your Camera2 document, then they should be one F Prime component with two instances in the topology. That said, please check the datasheets for both cameras to verify that they have the same hardware interfaces (I would be a bit surprised if they are different models and have the same hardware interfaces).

@j4lando do you have any input re: the Camera design or data collection topology?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants