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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: