Basler Camera Manual de usuario descargar pdf (Pagina 3)

If "no", the most likely reason is an enabled firewall. As described in the

INSTALL document, disable the firewall for those network adapters cameras

will be connected to. If you don't have a firewall, enabled reverse-path

filtering in the kernel may prevent detection of the camera. Refer to the

next problem description for further details.

* Problem: The IP Configurator can't see my camera. I'm not able to

reconfigure the camera to make it visible again.

Solution: First make sure you don't have a firewall enabled on your network

interface the camera is connected to.

If you still can't see the camera, reverse path filtering in the kernel may

prevent the IP Configurator to detect the camera. On some Linux

distributions reverse path filtering may prevent the discovery of GigE Vision

cameras. This can happen if the camera's IP is not within the same subnet as

the network adapter the camera is attached to. Normally the IP Configurator

can handle this by using broadcasts to discover the camera on any subnet.

Reverse-path filtering may prevent the IP Configurator to receive the

answer from the broadcast which in turn prevents the IP Configurator

from detecting the camera. To check whether filtering is turned on, run the

following command:

sysctl -a 2>/dev/null | grep '\.rp_filter'

in the output look for the following lines:

net.ipv4.conf.all.rp_filter=1

net.ipv4.conf.eth1.rp_filter=1

where "eth1" is the network adapter the camera is connected to.

The "net.ipv4.conf.all.rp_filter" is a global switch which must be turned off.

The "net.ipv4.conf.eth1.rp_filter" tells whether filtering for the specified

network adapter is activated. To disable filtering, you must first turn off

filtering for "all" and the specific network interface (in this

sample "eth1"). Use the following commands to change the filtering behavior

at runtime:

sudo sysctl net.ipv4.conf.all.rp_filter=0

sudo sysctl net.ipv4.conf.eth1.rp_filter=0

Restart the IP Configurator and check whether the camera(s) are

detected. Reconfigure the camera(s) and use "Write Configuration" to make

your changes persistent. You can re-enable filtering by executing the same

commands but set a value of 1. If you want to turn off filtering permanently,

you can edit the same values in /etc/sysctl.conf.

* Problem: When grabbing images, the CPU load is higher than expected.

Solution: Ensure that jumbo frames are enabled and large network packets are

used as described above in the 'Performance Optimization' section.

* Problem: Grabbing images leads to errors with error code 0x81010014.

This error code indicates that the PC received incomplete images, i.e.,

network packets have been dropped.

Solution 1: Ensure that jumbo frames are enabled as described above in the

'Performance Optimization' section. Also make sure that the camera's packet

size is set to a high value, if possible 8192.

Solution 2: Increase the maximum UDP receive buffer size to a value that is

large enough, e.g. by issuing the sudo sysctl net.core.rmem_max = 2097152

command. This allows pylon to increase the socket buffer size to 2 MB to

ensure a stable image acquisition. To make this setting persistent, you can

add the net.core.rmem_max setting to the /etc/sysctl.conf file.

Solution 3: Ensure that the application has the required permissions to set

the pylon receive thread's priority to real-time thread priority as described

in the INSTALL document.

Solution 4: Check the cable. For GigE, Cat 5e cables are recommended. Poor

cable quality or damaged cables can lead to unrecoverable transmission errors.

1 2 3 4 5

Comentarios a estos manuales

Sin comentarios

Basler Camera Manual de usuario Pagina 3

Comentarios a estos manuales

Relacionado con productos y manuales para Cámaras Bridge Basler Camera