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

FrameReceived stops getting called #38

Open
gseyfarth opened this issue Nov 20, 2018 · 2 comments
Open

FrameReceived stops getting called #38

gseyfarth opened this issue Nov 20, 2018 · 2 comments

Comments

@gseyfarth
Copy link

Hello - I've currently got 4 G319C's plugged into a 1Gbps PoE switch and am using this driver. I'm using 47e83f9 with Kinetic on 16.04.1. Occasionally, one/some of the cameras stop publishing and I've traced it as far as the FrameReceived callback in frame_observer.cpp. It seems that this callback simply stops being called. It looks like it turns into the Vimba SDK above that point so I can't really go any further. Has anyone else experienced this/know what the cause might be? With the current camera settings each camera is roughly 60 Mbps so I don't think it has anything to do with bandwidth. I've also observed similar behavior on a higher end 10Gbps switch. No consistent error messages in the terminal - from time to time I'll see a 'VmbFrameStatusIncomplete' message but not always.

@ykhedar
Copy link

ykhedar commented Nov 22, 2018

Hi, I have had this problem also recently with G-917C Camera. This is also connected via a 1Gbps switch to my computer. Please keep updating your progress. I will look into the direction which you have mentioned.

@JWhitleyWork
Copy link

This fork is no longer actively maintained. Please see our new fork at https://github.com/astuff/avt_vimba_camera, which has been updated and recently released.

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