Is your industrial camera suddenly not outputting images? Don’t rush to reinstall the software—first check these five areas.

What is the biggest concern during on-site commissioning?

It’s not that the image is unclear; rather:

The camera was working fine yesterday, but today it suddenly doesn’t show a single photo.

Many people’s first reaction is:

Reinstall the drivers, reinstall the software, and switch to a new computer.

In fact, when an industrial camera “doesn’t output images,” the issue is often not that complicated.

First, check in the following order.

01｜Let’s start with the simplest: the wire and power supply.

USB camera, please confirm first:

Is the USB cable loose, and is it plugged into a USB 3.0 port?

For GigE cameras, you must verify:

Is the network cable, power supply, or PoE functioning properly?

Basler’s troubleshooting guide also lists the power supply, cables, and interfaces as the first items to check when the camera is not detected.

For USB3 and GigE industrial cameras, the first step is always to check the physical connections.

Sometimes the most effective solution is also the simplest:

Unplug it and plug it back in, try a different port, and then switch to another cable.

02｜Has the computer actually recognized the camera?

The camera light being on doesn’t guarantee that the software will be able to detect it.

You can preview the USB camera first:

Windows Device Manager

Has the device been detected?

If a yellow exclamation mark appears, you should typically perform a more thorough check of the driver.

Teledyne’s troubleshooting documentation also notes that when a USB camera is visible in Device Manager but displays a yellow exclamation mark, it typically requires a driver check.

For GigE cameras, the approach is different:

It primarily relies on network card communication; don’t simply determine its status by checking whether a camera appears in Device Manager.

03｜GigE cameras are most prone to getting stuck in network settings.

The GigE camera’s light is on, and the network cable is also functioning properly.

But the software can’t find it?

At this point, the key checks are:

Are the computer’s network card and the camera on an IP subnet that can communicate with each other?

GigE cameras connect via Ethernet, and in multi-camera systems, network configuration requires particular attention.

Basler recommends using a dedicated GigE configuration tool to optimize the network card and camera’s network settings; improper network cards or network configurations can also lead to stability issues and problems with image data transmission.

In short:

For USB cameras, first check “USB and drivers”; for GigE cameras, first check “network card and IP address.”

04｜The camera can detect it, but when I press “Capture,” there’s no image?

In this case, stop fiddling with the network cable.

Most likely:

The camera is now in trigger mode.

The camera is waiting for an external signal:

“The product has arrived; you can place your order now.”

However, the sensor, PLC, or trigger line is not sending a signal,

The camera, of course, never took a picture.

Typical vision system: sensors detect the product, then trigger the camera to capture an image.

At this point, you can temporarily switch back:

Continuous / Free Run Continuous Acquisition

Let’s see if there’s any footage.

If the continuous mode is functioning properly,

Then the problem most likely lies in:

Trigger signal, trigger source, or I/O wiring.

Basler’s troubleshooting documentation also lists configuration errors and the absence of a trigger signal as typical causes of acquisition timeouts.

05｜Can generate the diagram, but throws an error as soon as it’s run?

At this point, you should start watching:

Bandwidth and network quality.

Especially for GigE cameras, if:

Poor cable quality, insufficient switch performance, and network card overload,

It may occur:

Incomplete image, packet loss, and capture failure.

Basler’s documentation also notes that Ethernet cables, switches, and NIC performance issues can all lead to packet loss, resulting in image acquisition failures.

At this point, check again:

Packet Size,Jumbo Frame, Bandwidth Usage

That’s what makes it more meaningful.

Don’t forget to check the software too.

If the hardware is functioning properly, you can also launch the camera manufacturer’s built-in Viewer tool.

Tools such as the Basler pylon Viewer can first verify whether the camera is recognized and whether it can acquire images normally.

If the drawing can be displayed correctly in the vendor’s Viewer,

But your own program doesn’t work,

Then the problem has most likely been narrowed down to:

SDK, program parameters, or code logic.

Finally, remember this troubleshooting sequence.

If an industrial camera suddenly stops outputting images, don’t rush to reinstall the operating system.

First, follow this order:

Cable and power supply → Computer recognition → IP/driver → Trigger mode → Bandwidth and software

Many on-site issues,

The first three steps can actually already lead you to the answer.

When a camera “doesn’t produce images,” the worst thing is to start poking around blindly.

Arranging them in order is actually the fastest.