Increasing bandwith ROS Topic Image_raw (USB) about pylon-ros-camera HOT 6 CLOSED

Hi,
I'm not able to solve your problem but I had the same problems like you some time ago.
In my opinion this node is a bit 'messy' which means it isn't behaving like I would expect and it isn't implemented like ROS would recommend.
Here are some adviced that helped me:

• Make sure that you use a USB3.0 connection I know that the cameras are working with USB2.0 but it isn't recommended.
• Play a bit with the exposure time. I'm not really sure how to explain it, but sometimes it helps.
• Try to watch the compressed images.
• Simply reduce the resolution. I know it's stupid, but this was finally my way to go, as I wasn't get acceptable frame rates out of it.
• Are you watching the images on the device on which the camera is connected to? Otherwise the network transport could be also a big bottle neck.

from pylon-ros-camera.

Thanks for the quick answer!
I think the problem is the ROS environment, because when i connect the camera with the same settings(bayer_rgb, resolution etc.) to the pylon viewer, i reached 40 fps and something round about 160 MB/s.
I changed the max USBFS MEMORY LIMIT in ubuntu to 1000MB, so ubuntu should be also not the problem.
So it should be possible to reach more than 6 fps and 12 MB/s for the image_raw topic...

from pylon-ros-camera.

Yeah I would agree. I think that the Ros Node is somehow a limiting factor.
Are you trying to vizualize the images with Rviz or rqt? Maybe they are also a problem? Have you tried to receive the images in your own node? What data rates are you reaching?

from pylon-ros-camera.

It seems that the developers have fixed some issues in the meatime since I've had this issues:
#29
#21
#28

Unfortunately, I have no camera over here to verify that but I think it will solve your problems!

from pylon-ros-camera.

@hannespimmel @FranekStark Hi, if you excluded any limitations due to exposure time and the camera being operatzed in USB2.0 mode, then it is because of the Software Trigger mode, which is by default used in the ROS adapter implementation. This mode naturally limits the maximum possible frame rate by at least a half. Thus, check especially #28 and use either free-run (like default in pylon viewer) or hardware trigger (you'll need an external cabling and trigger then). Cheers

from pylon-ros-camera.

It seems the issue has been solved. I am closing the issue.

from pylon-ros-camera.