Baumer VeriSens — No Trigger or No Output

Baumer · intermediate · 25 min

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.

ℹ️ A VeriSens that 'does nothing' almost always has a trigger problem (it's never told to inspect) or an output-assignment problem (it inspects but the result isn't wired to a pin). Configure both in VeriSens Application Suite and test them separately.

One tool configures everything: VeriSens Application Suite

Baumer VeriSens vision sensors (ID / CS / XF / XC series) are all set up in the VeriSens Application Suite — a single configuration tool with a web interface that walks you from a blank sensor to a working job in a few clearly-defined steps. Almost every "it's not working" case is a configuration gap in one of three areas: trigger, job result, or output — so test them in that order.

1. Is it triggering?

The sensor only inspects when it's triggered. If nothing happens at all:

• Check the trigger mode/source in the Application Suite — is it set to an external (hardware) trigger, and is that input actually being pulsed by the PLC/photoeye? Or is it set to a free-run/internal trigger when you expected external (or vice-versa)?
• Verify the trigger input wiring and signal level.
• Do a manual/software trigger from the Suite to confirm the sensor images and runs the job at all.

2. Is the job passing or failing?

Once it triggers, look at the feature-check result in the Suite. Each feature you added (pattern, contrast, code read, measurement) has a pass/fail with the settings that decide it. A sensor that triggers but the output never changes may simply be failing every inspection (bad ROI, threshold, or reference) — the pre-configured input mask for each feature helps you find the optimum settings. Tune the feature until good parts pass and bad parts fail reliably.

3. Is the result wired to an output?

A passing job still does nothing externally unless the result is assigned to a physical output. Check the digital output / process-interface configuration: which output pin carries the overall pass/fail (or a specific feature result), and its polarity/logic. Confirm the wiring to the PLC input matches that assignment.

Network / connection

If you can't even reach the sensor from the Application Suite, check the sensor's network settings under Device → Device settings → IP address / Network — the sensor and PC must be on the same subnet. Fix the IP before trying to configure anything else.

Step-by-step

1. Reach the sensor in the Application Suite (fix IP under Device settings if not).
2. Test the trigger — correct source (external vs free-run), input pulsed, wiring good; try a software trigger.
3. Check the job result — is it passing/failing correctly? Tune features so good vs bad parts separate.
4. Check output assignment — the result is mapped to a real output pin with the right logic, and wired to the PLC.
5. Re-test end to end with real parts.

Never do this

Don't loosen a feature's thresholds until everything 'passes' just to get an output — that ships bad parts. Tune so genuine good parts pass and genuine defects fail, then wire that honest result to the PLC.