System Description
Camera Name and Model: Flir BlackFlys USB3
Operating System: Ubuntu 20
Spinnaker Version: Latest
ROS Version: Noeic
Multiple Cameras Only
How is the triggering setup? Master/Slave or all slaves or all software triggered? The cameras are being triggered through a teensy. We are sending an output signal through the black cable and then have he blue cable as ground
For USB 3.0 cameras:
On same USB 3.0 bus or different buses? Different Buses. Each camera is plugged into seperate usb ports on the computer
Is the USB 3.0 hub externally powered?no
For Ethernet cameras:
How busy is the network, does the system work in grayscale, at a lower resoultion (binning) and framerate? The network is fine as long as we dont use external triggers we are able to store images and create rosbags
Do the cameras work with SpinView? yes
Describe the bug
We have a yaml file that is being used to trigger our system using a teensy. However, whenever we use this driver, we keeping getting the same error that we are using the wrong line_mode and line_source, I have copied a screenshot of the error below. This yaml file worked when we used the melodic version of the spinnaker camera driver and this problem only started when we transferred to the noetic version of the driver. Now when we updated, we can no longer trigger the camera so we are unable to control the frame rate and or capture images. I have looked over the yaml files provided in the github, but they do not clarify how to actually trigger these cameras. The yaml code is below:
System Description Camera Name and Model: Flir BlackFlys USB3 Operating System: Ubuntu 20 Spinnaker Version: Latest ROS Version: Noeic
Multiple Cameras Only How is the triggering setup? Master/Slave or all slaves or all software triggered? The cameras are being triggered through a teensy. We are sending an output signal through the black cable and then have he blue cable as ground
For USB 3.0 cameras: On same USB 3.0 bus or different buses? Different Buses. Each camera is plugged into seperate usb ports on the computer Is the USB 3.0 hub externally powered?no
For Ethernet cameras: How busy is the network, does the system work in grayscale, at a lower resoultion (binning) and framerate? The network is fine as long as we dont use external triggers we are able to store images and create rosbags
Do the cameras work with SpinView? yes
Describe the bug We have a yaml file that is being used to trigger our system using a teensy. However, whenever we use this driver, we keeping getting the same error that we are using the wrong line_mode and line_source, I have copied a screenshot of the error below. This yaml file worked when we used the melodic version of the spinnaker camera driver and this problem only started when we transferred to the noetic version of the driver. Now when we updated, we can no longer trigger the camera so we are unable to control the frame rate and or capture images. I have looked over the yaml files provided in the github, but they do not clarify how to actually trigger these cameras. The yaml code is below:
enable_trigger: 'On' line_mode: 'Input' line_selector: 'Line1'
line_source: 'ExposureActive'
trigger_activation_mode: 'RisingEdge' trigger_selector: 'FrameStart' trigger_source: 'Line0' trigger_overlap_mode: 'ReadOut'
image_format_color_coding: Mono8 auto_sharpness: true gamma_enable: false auto_white_balance: Continuous exposure_mode: 'Timed' exposure_auto: 'Continuous' auto_exposure_time_upper_limit: 24000 # increase until frame rate drops
timeout: 1000
Error Messages Copy and paste your error messages here
Screenshots If applicable, add screenshots to help explain your problem.