Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

input delay / high latency - basler acA2440-35uc #78

Closed
TKaluza opened this issue Apr 16, 2021 · 3 comments
Closed

input delay / high latency - basler acA2440-35uc #78

TKaluza opened this issue Apr 16, 2021 · 3 comments

Comments

@TKaluza
Copy link

TKaluza commented Apr 16, 2021

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?

@sevenagem
Copy link

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.

@FrancoisPicardDTI
Copy link
Collaborator

Hello @TKaluza
Did you manage to solve your issue at the end? Maybe you can share here how you did solve it?

@FrancoisPicardDTI
Copy link
Collaborator

I am closing this issue for now as it does not seem to be active anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants