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

[Humble] Acquisition and Trigger #213

Open
li-dahua opened this issue Oct 4, 2024 · 1 comment
Open

[Humble] Acquisition and Trigger #213

li-dahua opened this issue Oct 4, 2024 · 1 comment
Assignees
Labels
ROS2 This problem occurs with the ROS2 driver

Comments

@li-dahua
Copy link

li-dahua commented Oct 4, 2024

#How can I adjust these parameters in sync launch code? Thank you

There are three acquisition modes:

Continuous - acquires images continuously. This is the default mode.

Multi Frame - acquires a specified number of images before stopping acquisition.

Single Frame - acquires 1 image before stopping acquisition.

System details

  • operating system/version: ubuntu 22.04
  • ROS version[Humble]): Humble
  • complete FLIR camera model (e.g. BFS-U3-04S2C-C):BFS usb
@li-dahua li-dahua added the ROS2 This problem occurs with the ROS2 driver label Oct 4, 2024
@li-dahua li-dahua changed the title Acquisition and Trigger [Humble] Acquisition and Trigger Oct 4, 2024
@berndpfrommer
Copy link
Collaborator

Changing the acquisition mode is not directly supported for the blackfly S cameras. However, you can implement it easily yourself by modifying the blackfly_s.yaml configuration file. Follow the instructions in the README on how to add your own ros parameters, e.g. call it "acquistion_mode". Then you should be able to specify it at launch time by setting your newly created ROS parameter.
The other alternative is defining a user set with SpinView, and then loading that parameter set in your launch file by setting the correct ROS parameters.
I personally would choose the first option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ROS2 This problem occurs with the ROS2 driver
Projects
None yet
Development

No branches or pull requests

2 participants