Prosilica GC750C GigE camera not acquiring images using NI software

[benjamin UB]

We recently got a Prosilica GC750C GigE camera. After activating the Jumbo packages the camera is recognised and acquires images using Allied Sample Viewer. The NI Vision Assistand and MAX also recognise the camera. But trying to acquire images results in the attached error message. I would be very grateful for any help.

Best regards,

Benjamin

Operating System: Windows 7, 64-bit

Firewall disabled; Jumbo packages enabled

Allied Sample Viewer 1.24

NI Vision Assistant 2010 (build 20100621052956)

NI Max 4.7.2

[Pixar]

Hi Benjamin

Did you activate the Vision Acquisiton Software, is there a green cube in the license manager ?

Second point is, not all network cards support the jumbo frame size, here you can find a document to troubleshoot the GigE acquisition:

Troubleshooting GigE Vision Cameras read and examine all points carefully

So it is very important that you install and activate the vision driver (Vision Acquisition Software), the high performance driver for the network device and after that you can acquire images in MAX and set all parameters in MAX first before you do something with the Vision Assistant.

Regards

Pixar

NI Germany

[toto26]

Hi there,

First if jumbo frame is activated, you NIC is compatible.

This error message always happens if a firewall is activated.

be sure to deactivate any firewall. In XP, I know it's possible to deactivate firewall for one NIC in particular.

Then just check in MAX that the "Packet Size" is set to 8000. 

Regards

[BlueCheese]

To troubleshoot, the best thing to try here would be to change the packet size down to 1500 bytes in MAX and try acquiring again. If it works, then you know it is a problem receving jumbo frames with your network configuration. If it doesn't, then it is likely something to do with a firewall or some other software that is blocking the data from the camera.

Eric

[benjamin UB]

Hi Pixar

The Vision Acquisition Software is activated and Jumbo Frames is set on 9014.

Best regards, Benjamin

[benjamin UB]

Thank you very much for the multiple answers.


Both Allied AVT UniCam Version 1.1.3.0 and Allied SampleViewer Version 1.24 are acquiring images properly. Therefore I cannot imagine that a firewall is interfering. Also setting the packet size to 1500 in MAX did not solve the problem. Any other ideas?

[BlueCheese · Accepted solution]

---

@benjamin UB wrote:

Thank you very much for the multiple answers.


Both Allied AVT UniCam Version 1.1.3.0 and Allied SampleViewer Version 1.24 are acquiring images properly. Therefore I cannot imagine that a firewall is interfering. Also setting the packet size to 1500 in MAX did not solve the problem. Any other ideas?

---

Hi Benjamin,

If you are using a software-based firewall, there are actually quite a few reasons that one piece of software can acquire but another can't. Software can attach to the network stack at different layers and the behavior can be quite different. I believe the two places AVT software can attach are either in user-mode (in which case the firewall software can easily be configured on a per-application basis to let the traffic through), or as a kernel-based network filter driver (sits below the firewall so it is not affected by it). In IMAQdx's case, the two locations it can attach to the network stack are either in kernel-mode talking to the TCP/IP stack (above the firewall) or as a miniport driver directly above the hardware and below the firewall (if you have an NI GigE Vision card or one that is compatible with the NI High Performance Driver).

The newer versions of the GigE Vision standard have a new feature that make the protocol more "friendly" to firewalls. Our upcoming version of IMAQdx (which I believe should be on the web any day now) has support for this new feature. We've tested newer AVT cameras and it is supported as well. This should make firewall issues like this less of a problem.

Eric

Eric

[benjamin UB]

Hello,

It seems that there was a corrupted firewall configuration file. Resetting the operating system solved the problem. Thank you very much again for the assistance.

Best regards,

Benjamin