Symptoms

After starting any Impact Acquire based application no GigE Vision™ compliant devices are accessible or detected

Cause

At it is known from surfing the Internet, normally the Ethernet communication channel is protected using a firewall. GigE Vision™ compliant devices are communicating via Ethernet, too, so perhaps the firewall prevents that the devices are detected.

Resolution

As a test, you can switch off the firewall. If the GigE Vision™ devices are detected then, you have to adapt the firewall settings. E.g. the default installation of Ubuntu contains ufw - the uncomplicated fire wall, which is command line based front end for iptables.

At first it might be interesting to figure out if the firewall is actually enabled. This can be done by calling:

sudo ufw status

If the firewall is enabled, the output on Ubuntu 20.04 will be:

Status: active

To turn it off, just enter the following command in the command line:

sudo ufw disable

Checking the status of the firewall again using:

sudo ufw status

Should return:

Status: inactive

Once the firewall is disabled the device should be discovered flawlessly by any of the Impact Acquire applications.

Note: If it is necessary to have an enabled firewall and to use GigE Vision™ devices, it will be necessary to define rules for the firewall. The following UDP ports need to be open: 3956 and from 49152 to 65535 to make sure GigE Vision™ devices can be used without any interference from the firewall.