05-09-2013 03:04 AM
Hi,
I ended up monitoring the lost packet count to detect when the problem was likely to occur and then reducing the frame rate/s of the imagers to 1 before the hang occured to maintain system stability. It's then up to the user to change the frame rates and resolutions of the imagers to something reasonable. Not very elegant. I've been meaning to make it more intelligent but haven't got to it yet.
Regards,
Mike
04-12-2015 07:17 AM
Dear Chris / Mike,
I am facing the same problems and request you to share the solution if you found it?
04-12-2015 07:32 AM
My problem ended up not having anything to do with the Vision Acquisition Software or my LAN settings, etc., but rather with a PCI board that I was using to communicate data across a Profibus network. The PCI board was the 780160-01 from NI but the particular hardware version I was using at the time had some problem with its onboard clock compatibility with my PC; NI fixed the problem in later versions of this board. In the meantime, I changed to an alternative communication method (using UDP), removed the baord, and never saw the problem occur again.
That said, consider that when Windows Hangs it is often a driver issue or a hardware issue.