Basler Camera Not Detected in pylon Viewer

Basler · beginner · 20 min

A Basler camera missing from pylon Viewer is usually a driver or enumeration issue — commonly a Windows Update disabling the GigE driver. Repair the pylon driver and check the network/USB settings.

ℹ️ pylon enumerates every device and checks it against the GigE Vision / USB3 Vision standard. If your camera isn't in the tree, either the driver isn't presenting it or the device isn't enumerating — both are fixable without new hardware.

Why the camera isn't in the tree

When a Basler camera doesn't appear in the pylon Viewer device tree, pylon either can't enumerate it or the driver isn't presenting it. pylon enumerates all possible devices and checks whether each fits the USB3 Vision or GigE Vision standard, so a missing camera is a driver, network, or connection problem — rarely a dead camera.

The most common cause: a Windows Update disabled the GigE driver

After a Windows Update, Windows 10 may disable the Basler GigE camera because the update uninstalls or alters the Basler Ethernet driver the camera needs. Fix it by:

  1. Run the Basler pylon driver installer and choose Repair, or
  2. Uninstall and reinstall pylon entirely.

This restores the Basler filter/performance driver so GigE cameras enumerate again. If your camera vanished right after a Windows update, check this first.

GigE camera checks

  1. Power and link: confirm the camera is powered and connected to the network; check link LEDs.
  2. Same subnet / IP: the camera and the NIC must be reachable — verify the camera has a valid IP on the NIC's subnet (pylon IP Configurator can set it).
  3. MTU / jumbo frames: for reliable GigE imaging, configure the MTU correctly — enable jumbo frames (e.g. MTU 8192) on the NIC and camera for full-frame throughput.
  4. device_user_id: if you reference the camera by name in code/config, confirm the device_user_id is spelled correctly — it is case-sensitive.

USB3 camera checks

Use the pylon USB Configurator — it detects error conditions and offers solutions, and can generate a report of the current USB device tree you can send to Basler support. Confirm the camera is on a USB3 (SuperSpeed) port with a good cable, and that the USB3 Vision driver is installed.

Step-by-step

  1. After a Windows update: Repair or reinstall the Basler pylon driver first.
  2. GigE: verify power/link, a valid IP on the NIC subnet, jumbo frames/MTU, and correct case-sensitive device_user_id.
  3. USB3: run the pylon USB Configurator, confirm a SuperSpeed port and good cable, and the USB3 Vision driver.
  4. Re-open pylon Viewer and confirm the camera appears in the tree.

Verify

Once the driver and connection are correct, the camera appears in the pylon Viewer tree and you can open a live image. If it still doesn't enumerate, generate the pylon USB Configurator report (USB) or check the NIC's Basler driver binding (GigE) before assuming a hardware failure.

Key points

  • pylon enumerates all devices against GigE/USB3 Vision — a missing camera is a driver, network, or connection issue, rarely a dead camera.
  • The top cause is a Windows Update disabling the Basler GigE driver — Repair or reinstall the pylon driver.
  • GigE: verify power/link, a valid IP on the NIC subnet, and configure jumbo frames/MTU (e.g. 8192) for reliable imaging.
  • device_user_id is case-sensitive — a mis-cased name makes a named camera 'not found'.
  • USB3: use the pylon USB Configurator (it detects errors and reports the USB tree); confirm a SuperSpeed port and good cable.

Codes and symptoms

No devices found — Camera not enumerated
pylon can't enumerate the camera — commonly a Windows-Update-disabled GigE driver, a network/IP issue, or a USB3 connection problem.