Vision Systems — troubleshooting procedures

Configuration, calibration, and troubleshooting for industrial vision systems, smart cameras, and machine vision controllers.

16 published procedures.

• Cognex In-Sight Not Acquiring — Online/Offline & Trigger Checks

  When a Cognex In-Sight camera stops grabbing images, the cause is usually the Online/Offline state, a missed trigger, or an editing lock — not a broken camera. Work these checks before swapping hardware.

• Keyence XG / CV-X — Trigger Input but No Image Capture

  When a Keyence XG or CV-X vision system receives a trigger but doesn't capture, the cause is usually the flowchart structure or a waiting state — not the camera. Check the program flow first.

• Omron FH Vision — STEP Trigger Not Accepted

  When an Omron FH vision controller ignores its measurement trigger, work the STEP / BUSY / READY handshake and the STEP input filter before suspecting the camera — most 'no measurement' cases are signal timing.

• Banner iVu — Output/Trigger Polarity & Remote Teach

  When a Banner iVu sensor's Pass/Fail output or trigger seems wrong, it's usually PNP/NPN polarity or the input transition direction — plus a missing pull-up on NPN triggers. Set the Input Polarity to match your wiring.

• Datalogic Matrix — NO READ Recovery (Focus & Setup)

  A Datalogic Matrix reader lighting the red STATUS (NO READ) LED usually needs the focus distance set to the code or a Setup/Learn to configure photometry and symbology — use X-PRESS or DL.CODE, not a replacement.

• Basler Camera Not Detected in pylon Viewer

  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.

• ifm O2D/O2I — No Evaluation & 'Trigger Overrun'

  When an ifm O2D/O2I vision sensor produces no evaluation or its output won't switch, the usual cause is the trigger mode or a 'Trigger overrun' from re-triggering too early. Check the trigger timing in ifm Vision Assistant.

• Balluff BVS — Trigger/Output Line Config in BVS Cockpit

  When a Balluff BVS SmartCamera won't trigger or its output won't switch, the cause is usually the I/O line direction, a non-PNP trigger, or the pulse/delay settings. Configure the lines in BVS Cockpit.

• Matrox Iris GTR — Camera Offline & Comms Setup

  A Matrox Iris GTR smart camera that won't show up in Design Assistant is almost always a network issue: it ships on DHCP. Learn to find it with IrisGTRDiscovery, set a static IP, enable the PLC protocol in MILConfig, and pull a troubleshooting log.

• Teledyne DALSA GigE — Camera Not Detected in Sapera

  A Teledyne DALSA Genie Nano or Linea GigE camera that won't show up in Sapera CamExpert is nearly always a network/IP issue. Learn to force discovery with Scan Network, fix the LLA/DHCP address fallback, clear the firewall, and resolve the filter-driver conflict.

• Baumer VeriSens — No Trigger or No Output

  A Baumer VeriSens vision sensor that never fires or never switches an output is usually a trigger-source or output-assignment problem, not a bad sensor. Learn to work through it in VeriSens Application Suite — trigger, job result, digital output and network.

• Festo SBS Vision Sensor — No Image or No Trigger

  A Festo SBS/SBSi vision sensor that shows no live image or never inspects is usually stuck in the wrong trigger mode or unreachable on the network. Learn to switch between free-run and triggered capture in Vision Sensor Configuration Studio and fix the connection.

• Leuze LSIS 400i Smart Camera — No Read

  A Leuze LSIS 400i smart camera that won't read a 1D/2D code is usually a focus, lighting, or code-type-configuration problem, not a broken camera. Learn to set it up over the browser (webConfig), dial in the motorized focus, and work through a no-read.

• Contrinex Photoelectric Sensor — No Detection

  A Contrinex photoelectric sensor that misses the target or won't switch its output is usually a teach/alignment/mode problem, not a failed sensor. Learn to check the sensing mode, re-teach the setpoint, confirm light-on/dark-on, and verify the PNP output.

• SICK Lector — NO READ Recovery (Focus & Code Type)

  A SICK Lector code reader outputting NO READ usually has the wrong focus for the working distance or the code type disabled — not a failed camera. Set focus for the exact distance and enable the symbology in SOPAS.

• Cognex In-Sight to PLC Communication — Profinet & Modbus TCP Setup

  Wire a Cognex In-Sight vision system to a Siemens or Allen-Bradley PLC over Profinet and Modbus TCP. Covers In-Sight Explorer network config, GSDML import, Native Mode vs industrial protocol tags, and the common pass/fail data map.