Knowledge Base

Problem

A user's Basler GigE camera shows as 'Not Reachable' in Pylon IP Configurator and switches to DHCP to restore the connection, but is unsure whether DHCP is safe to use with EthoVision.

Details

When a camera IP and the network adapter IP do not match (e.g., after a network change or driver reset), Pylon reports the camera as 'Not Reachable'. Switching to DHCP may restore connectivity temporarily, but DHCP is not recommended for EthoVision GigE camera setups because the IP address can change between sessions, causing EthoVision to lose the camera. Affected versions: EthoVision XT with Basler GigE cameras (all versions).

Solution

1. DHCP may restore the camera connection temporarily, but static IP is strongly recommended for EthoVision GigE camera setups to ensure consistent detection.
2. Open Pylon IP Configurator (run as Administrator).
3. Select the camera and assign a static IP address (e.g., 169.254.x.x or another address in the same subnet as the dedicated GigE NIC).
4. Assign a matching static IP to the dedicated GigE network adapter in Windows Network Settings — the camera and NIC must be on the same subnet.
5. Confirm the camera status in Pylon changes from 'Not Reachable' to 'Reachable'.
6. Open EthoVision and verify the camera is detected as an acquisition source.
7. If the camera still shows as 'Not Reachable' after matching IPs, power-cycle the camera and restart Pylon.
8. Ensure the GigE NIC is a dedicated adapter (not shared with internet/LAN traffic) for best performance.