Skip to content

Conversation

@psmithcrl
Copy link

Make sure the fps change has been accepted by camera before finishing reconfiguration.
FPS can take the camera time to apply and can result in a failed setting if queried too quickly.

@psmithcrl psmithcrl requested a review from mattalvarado August 6, 2024 16:30
}
}

crl::multisense::Status Camera::verifyFpsChange(const crl::multisense::image::Config& config)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@psmithcrl Is FPS the only parameter which needs to be confirmed like this? Out of curiosity what failure were you seeing by setting the FPS once?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found the thread on slack. Sorry

@mattalvarado
Copy link
Collaborator

My preference would be we close this PR since this is now fixed in firmware newer than 7.06

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