Cognex Support FAQ: 7 Questions Engineers Actually Ask (Including the Thermal Camera One)

Seven questions I actually answer as a Cognex support engineer

I've handled Cognex support requests for about six years. Before that, I was the engineer stuck on the other end of the phone, waiting for a ticket response. This is the FAQ I keep on my desk—seven questions that come up constantly, including a few that embarrassed me to learn the answers to.

They're meant to be read in any order. Skip ahead.

1. How do I get human Cognex support when I'm stuck?

Start at support.cognex.com. Create an account, register your device, and open a ticket with your part number, serial number, firmware version, and a clear photo or video of the problem. That last part is not optional.

My first year, 2019, I submitted a ticket that just said "camera not reading." I got a reply asking for details I should have included from the start. A day gone. Now I tell customers: logs beat adjectives. "It's broken" is a feeling, not a data point.

Here's the part I'm not proud of. I once told a customer, "It might be the cable." What he heard was, "Replace the camera." He ordered a $1,200 replacement, it arrived, and it behaved exactly the same. The problem? The cable.

As of early 2025, the support portal is still the fastest route—but it works best when you've already tested the basics. Detail wins. Every time.

2. Does Cognex make a thermal camera?

No. And if you typed "Cognex thermal camera" into a search engine and landed here, you're not confused—just pointed at the wrong shelf.

Cognex makes machine vision systems, barcode readers, and vision sensors. We don't build thermal cameras. I once told a customer, with full confidence, that our In-Sight series could handle "thermal-ish" inspection. He asked two follow-up questions, I went quiet, and we both learned something that day. I still wince.

Thermal is a different tool for a different problem. Reading codes, checking assembly presence, measuring dimensions—that's machine vision. Measuring heat, spotting insulation gaps, checking motor bearings—that's thermal imaging, typically from companies like FLIR. Different physics, different product lines.

3. How to use a FLIR thermal camera for industrial inspection

Since this keeps coming up, here's the short version. Set your emissivity first. Every FLIR user manual includes emissivity values for common materials—plastic, painted metal, bare aluminum, all different. Pick the value that matches your target. If you don't know the material, start around 0.95 and verify with a contact thermometer. Why does this matter? Because a wrong emissivity setting can throw a reading off by tens of degrees, and you'll never see it coming.

Next, check your temperature range. A camera set up for 400°C furnace work is nearly blind to a 40°C bearing housing. Adjust the span to your application, not the marketing video.

Finally, let the camera stabilize. Thermal sensors drift for a few minutes after power-up. Give it five minutes, then start judging.

One thing I repeat often: don't use a thermal camera to read barcodes. It won't. That's the visible-light Cognex camera's job. In the stations we build, they sit side by side—thermal for heat signatures, machine vision for codes. Teammates, not rivals.

4. Can I use a Fluke 117 multimeter to troubleshoot my Cognex system?

Yes, and I do. I spent an afternoon reading 117 multimeter reviews before picking the Fluke 117 for my field bag. It's the meter I grab when a camera dies at 3 a.m.—or rather, when the camera's power supply dies at 3 a.m. That distinction is the whole lesson.

What do I actually measure? The 24V DC supply at the camera input, ground continuity, and the sensor wiring. The Fluke 117's non-contact voltage detection sounds like a gimmick until it catches a mis-wired panel. It caught one for me. I stopped smiling at that feature.

The mistake I used to make was blaming the camera before measuring anything. I chased a "camera fault" for a week—or rather, I chased a loose ground for a week. The multimeter sat in its case the whole time. Simple. Humiliating. Never again.

Measure first. The camera can wait.

5. Why won't my reader scan the barcode on a pipette holder?

This one arrived as an email from a small biotech startup. A pipette holder—small, curved, frosted plastic—and their new Cognex reader couldn't hold a consistent read. Their order was tiny. Their frustration was not.

The reader wasn't the problem. The lighting was. A curved, translucent surface scatters light in every direction, killing barcode contrast. We added a simple backlight behind the holder, and read rates went from roughly 40% to near-perfect in an afternoon.

That email also changed how I treat small inquiries. In 2022, I let a different small request sit for two days. The customer found help elsewhere and told me about it, politely, six months later. I don't let small orders wait anymore. Small doesn't mean unimportant. It means potential.

6. Is Cognex support going to ignore me if I'm a small customer?

No, but I understand the worry. I was that customer when my automation budget was one project and a good lunch. The vendors who took my $200 orders seriously are the same ones I still call for $20,000 orders. Those early calls shaped how I answer tickets today.

You don't need a support contract to open a case, and Cognex Academy has free training that covers setup and diagnostics. The documentation portal is searchable if you know your product family. Start there, escalate when you're stuck. That's the right order.

I have mixed feelings about support contracts. On one hand, they're a budget line you have to defend every year. On the other, the one quarter we didn't have coverage was the quarter everything failed at once. My compromise: maintain a path to support, even if it's per-incident. A line down at 2 a.m. with no one to call is a feeling you can't expense.

7. What do you check before you even call support?

This is the question I'm now paid to ask other people. After the third rejected ticket in Q1 2024, I built a pre-check list. It's boring. It works.

• Part number and serial number
• Firmware version
• Measured supply voltage at the device
• Cable tested with a known-good spare
• Error code shown on screen
• Photo of the setup

Seven items. Ten minutes. We've caught 47 potential errors using this list in the past 18 months. Before it existed, I was the guy calling with "it's broken" and burning everyone's time.

The camera is rarely the problem. The cable, the lighting, the ground, the settings—those are the problem. The camera is just the component with the blinking light.

Run the list. Then call me.