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
On our system with Intel(R) Xeon(R) CPU E3-1505M v6 we have very heavy delays (several seconds, sometimes over 10 seconds) until the message arrives. We use a USB3 Basler acA2440-35uc camera for this. If we open PylonViewer directly on the same computer, it works fine. Via rqt_image_view (and no matter which topic we connect to) the message is delayed very long.
All settings are stored within a User-Settings, which is invoked while launching. The framerate is set to 20hz. No scaling is applied. The framerate of the received, but delayed message seems to be okay (movements are smooth). We do not face this problem on a desktop pc setup.
On the first look I think this issues #17 is fixed and does not relate to this problem anymore, or does ist?
Are there any approaches to solving this problem?
Is there a option for software scaling within the pylon-ros-camera node?
The text was updated successfully, but these errors were encountered:
I have a similar issue with two acA1920-40gc (GigE) cameras. Although, the delay I am seeing is about 2 seconds, not 10.
However, if I subscribe to the image topic before I start the pylon node (e. g. using an image view), I get no delay and everything is working as it should. If I stop all nodes subscribed to the image topic and then subscribe to the topic again, I get the delay again.
Using this workaround, I am able to use the cameras. But it is very annoying that the node has to be restarted to fix the delay again.
On our system with Intel(R) Xeon(R) CPU E3-1505M v6 we have very heavy delays (several seconds, sometimes over 10 seconds) until the message arrives. We use a USB3 Basler acA2440-35uc camera for this. If we open PylonViewer directly on the same computer, it works fine. Via rqt_image_view (and no matter which topic we connect to) the message is delayed very long.
All settings are stored within a User-Settings, which is invoked while launching. The framerate is set to 20hz. No scaling is applied. The framerate of the received, but delayed message seems to be okay (movements are smooth). We do not face this problem on a desktop pc setup.
On the first look I think this issues #17 is fixed and does not relate to this problem anymore, or does ist?
Are there any approaches to solving this problem?
Is there a option for software scaling within the pylon-ros-camera node?
The text was updated successfully, but these errors were encountered: