Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Jetson AGX Xavier - Unable to capture synchronised shutter using master configuration #143

Open
@jwurts-mitre

Description

@jwurts-mitre

System Description
Camera Name and Model: 2x Blackfly S (USB3, connected via Sync cable)
Operating System: Ubuntu 18.04.5
Spinnaker Version: 2.2.0.48
ROS Version: Melodic

Computer details
Processor: Nvidia AGX Xavier
RAM: 32GB

Multiple Cameras Only
How is the triggering setup? Master, Master/Slave, Default, see below

For USB 3.0 cameras:
On same USB 3.0 bus or different buses? Same bus
Is the USB 3.0 hub externally powered? Yes

Do the cameras work with SpinView?
Yes

Describe the bug
I can't acquire camera images when the camera is in master SpinView configuration on a Jetson AGX. Ros error is:

[FATAL]: Spinnaker: Failed waiting for EventData on NEW_BUFFER_DATA event. [-1011]
Likely reason is that slaves are not triggered. Check GPIO cables

I have two Blackfly S cameras and have tested many configurations on a Jetson AGX and x86 laptop. On the x86 laptop, I can publish the two camera streams when in default Flir camera settings, publish the two camera streams when in Master/slave configuration, and publish one camera stream when in Master configuration.

On the Jetson AGX, I can build spinnaker_sdk_camera_driver, following the steps laid out in#89. Within SpinView, I can see the two camera stream when in default/default, two streams in master/slave, and single stream in master configuration. I can launch spinnaker_sdk_camera_driver and see the stream(s) when in default camera configuration(s). However, when I launch ros with the camera in master or master/slave configurations, ros errors out.

The above variations account for the related yaml files and such. Given the variations run on the x86 machine, I trust the configurations and connections are set appropriately. But I can't resolve why the ros launch errors on master configuration, especially given SpinView streams.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp