You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what you want to implement and what the issue & the steps to reproduce it are:
Hello,
We are working to integrate a Basler ace acA800-200gc color gig-e camera into our ROS setup.
Do to security constraints at our University, we are required to run our ROS environment within an Apptainer container.
We have had success plugging the camera into personal laptops, but when replicating the set up on the work PC we're using for our entire ROS environment, we are not able to connect to the Camera.
We have a static IP set on the camera. This works correctly on the laptop, but the ROS driver cannot find the camera on the PC. We have tried to follow this issue, but the environment variable for the GENICAM do not appear to apply to our camera.
Hardware setup description
Our camera is a Basler ace acA800-200gc color gig-e
Its serial number: "S/N: 24567034"
Both computers we have used are x86_64
The Laptop we are using, where the camera works, has Arch Linux. The Desktop where it is NOT working is using Rocky Linux 9.
In both cases, we are connecting the camera via a power-over-ethernet injector, a Phihong "Single Port Power Over Ethernet IEE802.3at Compliant PSE" Model POE29U-1AT. Both computers, the working laptop and the non-working desktop are plugged into the same ethernet switch, a NetGear ProSAFE GS-108. All cables are standard CAT-6 Ethernet cables.
In both cases, we are basing off of the ROS Humble official Docker Image on Ubuntu 22.04.
Runtime information
Having issues running the pylon viewer within our container (QT issues), not permitted to install it outside of the container.
ipconfigurator does run, it is version 8.0.0.10 (We are manually installing the package, and using pylon 7.5.0.15658 and pylon-supplementary-package-for-blaze 1.6.0.542964d0) Outside of our container, we do see the camera in ipconfigurator, we do NOT see it in ipconfigurator in the container.
echo$ROS_DISTO
humble
Is your camera operational with the Basler pylon Viewer on your platform?
Yes
Thank for any/all help. Sorry this is so scattered, I'm trying to document what's going on across multiple computers with a very restrictive containerization setup!
The text was updated successfully, but these errors were encountered:
Describe what you want to implement and what the issue & the steps to reproduce it are:
Hello,
We are working to integrate a Basler ace acA800-200gc color gig-e camera into our ROS setup.
Do to security constraints at our University, we are required to run our ROS environment within an Apptainer container.
We have had success plugging the camera into personal laptops, but when replicating the set up on the work PC we're using for our entire ROS environment, we are not able to connect to the Camera.
We have a static IP set on the camera. This works correctly on the laptop, but the ROS driver cannot find the camera on the PC. We have tried to follow this issue, but the environment variable for the GENICAM do not appear to apply to our camera.
Hardware setup description
Our camera is a Basler ace acA800-200gc color gig-e
Its serial number: "S/N: 24567034"
Both computers we have used are x86_64
The Laptop we are using, where the camera works, has Arch Linux. The Desktop where it is NOT working is using Rocky Linux 9.
In both cases, we are connecting the camera via a power-over-ethernet injector, a Phihong "Single Port Power Over Ethernet IEE802.3at Compliant PSE" Model POE29U-1AT. Both computers, the working laptop and the non-working desktop are plugged into the same ethernet switch, a NetGear ProSAFE GS-108. All cables are standard CAT-6 Ethernet cables.
In both cases, we are basing off of the ROS Humble official Docker Image on Ubuntu 22.04.
Runtime information
Is your camera operational with the Basler pylon Viewer on your platform?
Yes
Thank for any/all help. Sorry this is so scattered, I'm trying to document what's going on across multiple computers with a very restrictive containerization setup!
The text was updated successfully, but these errors were encountered: