Cognex
Cognex In-Sight Smart Cameras: Families, Selection and Failure Modes
Cognex In-Sight smart cameras compared: 2800, 3800, 3900, 8900, 6900 and SnAPP, how to choose one, how they fail on a line, and the older 7000 to 9000.
Cognex In-Sight is the line of smart cameras that most plants meet first when they put machine vision on a production line. Each In-Sight packs the lens, sensor, processor, inspection tools, network ports and discrete I/O into one body that bolts over the product. This page compares the current and older families, explains how a camera is selected, and describes how In-Sight jobs fail in service, which is what separates a demonstration from a station that runs every shift. It sits under the Cognex technology hub.
What an In-Sight does. It waits for a trigger, exposes an image with the light you have fitted, runs a stored job of tools (locate the part, measure, read text or a code, classify with AI) and reports the result. The job lives on the camera, so the camera keeps inspecting if the PC that built the job is switched off. Current models are programmed with In-Sight Vision Suite, in either of its two modes, covered under EasyBuilder versus Spreadsheet.
Cognex In-Sight families compared
The table lists what Cognex documents and announces. Launch dates are from Cognex releases or trade press where noted, and the status column is our label from the lifecycle model as of November 2026.
| Family | Launched | Resolution | What sets it apart | Software | Our status |
|---|---|---|---|---|---|
| 3900 | 5 May 2026 | Up to 25 MP (Cognex states) | Qualcomm Dragonwing platform, dual Ethernet, Edge AI and Advanced AI tools | Vision Suite | Current |
| 6900 controller | 28 April 2026 | Depends on the camera chosen | NVIDIA Jetson, up to 157 TOPS (Cognex states), cameras, lenses and lights chosen separately | Vision Suite | Current |
| 8900 | About March 2025 (trade press) | 0.5 to 12 MP | Small global-shutter body aimed at machine builders | Vision Suite | Current |
| 3800 and 3800 Line Scan | 10 April 2023 | 1.6 to 16 MP | Two Ethernet ports, liquid-lens autofocus, Multi Torch light, Edge AI on the camera | Vision Suite | Current |
| SnAPP | 15 September 2023 | 1.6 MP | Browser setup, presence and defect checks | A web browser | Current |
| 2800 (Mini, Detector) | April 2022 | 0.4 to 2 MP | Compact body, edge learning classify | Vision Suite | Current |
| 9000 | November 2018 | 12 MP area scan, line scan | High resolution, IP67 with cover | Explorer | Mature |
| 7000 second generation, 8000 | 7000 second generation April 2017 (trade press); 8000 date not found | Varies by model | Modular and compact rule-based systems | Explorer | Older, inferred |
| 2000, D900 | Earlier; D900 April 2020 | D900: 2.3 and 5 MP | The D900 ran deep learning on the camera, trained on a GPU PC | Explorer | Older, inferred |
The In-Sight L38 3D camera belongs to the 3D family and is covered on the 3D vision page. Two caveats on the table. The 8900 date is murky: Vision Suite 24.4.0 already listed 8900 support, which suggests the camera reached machine builders before the March 2025 trade article, and the resolution of the 6900 depends on its camera. We did not find model numbers, prices or ship dates for the 3900 or 6900 in Cognex’s releases.
The 3800 resolutions in numbers. Cognex’s 3800 manual lists six sensors from 1.6 to 16 megapixels, with frame rates that fall as resolution rises: 125 frames per second at 1.6 megapixels in monochrome against 18 at 16 megapixels. More pixels give finer detail on a wide field but cost speed and need better glass.
How a job runs, and where it breaks
Every In-Sight job follows the same path, and each stage has its own failure modes. The diagram marks where the common problems enter.
How an In-Sight is selected
Selection runs in the same order every time. First the inspection: what the smallest feature is, how much of the product the camera must see, and how fast parts pass. Those give the resolution and frame rate. Second the optics and light: lens, light colour and angle, and whether the station is washed down. Third the software mode: guided EasyBuilder for a technician-maintained station, or Spreadsheet for custom logic. Fourth the plant interface: which protocol the PLC speaks, how the camera is triggered, and where images go. Last the lifecycle: which software the plant can support and how long the family is likely to stay available.
Resolution is a ratio, not a headline number. Cognex’s own field-of-view tables show, for example, that an IS3801 with a 16 mm lens sees 47 millimetres at a 150 millimetre working distance, so each of its 1,440 pixels covers about 0.033 millimetres. Whether that is enough depends on the feature. The usual rule is to put several pixels across the smallest feature, but that is general vision practice, not Cognex guidance. The choosing an In-Sight camera page turns this into a decision between the 3800, 3900, 8900 and 2800.
How Cognex In-Sight cameras fail
This section is our view, grouped from Cognex’s documented behaviour and common practice in vision work. None of these is a defect in the camera. Each is a way a working station stops working.
Lighting drift. Light levels change as LEDs age, as a power supply changes or as ambient light enters through a door or a window. The job’s thresholds were tuned for yesterday’s image. Mitigations are shielding, a documented light setting, and a periodic check against a reference part. For colour cameras Cognex’s guidance is to use white light.
Focus and mounting. A knocked bracket or a changed working distance moves the image. Cognex states that changing the lens, focus, resolution or camera position invalidates a calibration, so any maintenance that touches those needs a re-calibration step. The 3800 is IP67 only with its cable plug or cables fitted and either the IP67 cover or the Multi Torch light installed; a bare camera is not rated.

Trigger timing. Cognex’s release notes carry a known issue that the trigger interval must be at least 1.5 times the job execution time. A camera that is triggered faster than it can finish drops triggers, and the line sees missing results rather than a fault. For tight timing, a wired trigger into the acquisition input is more predictable than a PLC bit, because the 3800 manual specifies a maximum 24 microsecond latency and a minimum 1 millisecond pulse on that input.
Job changeover. A mixed-SKU line must load the right job for each product. In Cognex’s older Explorer-era documentation, loading a job over EtherNet/IP requires the camera to be offline and the job to exist under the requested number, so a PLC that requests a job while the camera is online, or a number that does not exist, gets an error back. Confirm the current behaviour in Vision Suite documentation for your model before commissioning.
Network, clock and archive. The camera’s factory network setting is DHCP, and Cognex recommends a static address after setup. A power-cycled camera returns its clock to 2000-01-01 until a time server answers, so archived images can carry the wrong date. Cognex documents that an invalid FTP path or credential in the image-write function does not raise an error, so a station can run for weeks writing nothing. These are covered on the image archiving and data page.
Configuration drift and edge cases. A job re-saved on Vision Suite 24.4.0 firmware cannot be loaded on earlier firmware, according to the release history, so a replacement camera with older firmware may not open a newer job. And an Edge AI Anomaly Detect tool needs a fixturing tool upstream so every inspection sees the same perspective. Keep dated backups of every job, and keep the version it was saved with.
A first-check table. When a station misbehaves, start with the symptom the PLC sees and check the likely stage first. The table is our troubleshooting order, not a Cognex procedure.
| Symptom at the PLC | Likely stage | First check |
|---|---|---|
| Intermittent missing results at high speed | Trigger | Trigger interval against job execution time; wired trigger pulse width |
| Pass rate shifts slowly over weeks | Acquire | Light level against a reference part; ambient light; bracket and focus |
| Wrong product inspected after a changeover | Tools | Which job is loaded; the job number the PLC requested |
| Result read but stale or doubled | Result | Whether the PLC reads on the results-valid signal and acknowledges it |
| Images missing or dated 2000 | Network and clock | FTP path and credentials; time server reachability after power cycle |
Lifecycle and the older families
The 7000 second generation (April 2017, trade press), the 8000, the 9000 (November 2018) and the 2000 are older families. We found no Cognex discontinuation notice for any of them. Cognex still hosts their manuals, and In-Sight Explorer 6.5.1 from October 2024 still lists the firmware of the 7000 second generation, 8000 and 9000; the 2000 appears in the CISA advisory but not in that list. In CISA advisory ICSA-25-261-06 of 18 September 2025, Cognex reports that “In-Sight Explorer based vision systems are legacy products not intended for new applications” and points to the 2800, 3800 and 8900 as the next generation; the advisory’s affected list is the 2000, 7000, 8000 and 9000 series and Explorer 5.x to 6.5.1 (CISA). The advisory lists nine vulnerabilities in these lines and in Explorer 5.x to 6.5.1, and Cognex’s response, as CISA relays it, points to newer products rather than to patches.
What that means in practice. We label these families mature to older, inferred, and suggest three actions for a line that depends on them: confirm spares with Cognex or a distributor, keep the cameras off shared networks, and plan a migration. The 2025 advisory page explains what the advisory says, and replacing older In-Sight cameras covers the move. The 3800 even ships converter brackets that match the 7000 mounting footprints, which is mechanical evidence of a migration path but not a statement that the 3800 replaces the 7000.
What we do here
Our team has programmed in-line inspection on Cognex In-Sight cameras at large food and consumer-goods manufacturers, and we integrate Cognex cameras and readers with PLCs, line controls and data systems as part of controls projects. We have no commercial relationship with Cognex and do not resell its products. On In-Sight work our scope is:
- Specification: turning an inspection requirement into resolution, optics, light and fixture requirements before a camera is chosen.
- PLC handshakes: trigger, result and job-change logic in the controller, as a documented sequence a technician can follow.
- Commissioning: a checklist run through network, time, trigger, lighting, calibration and archive before handover, with the commissioning support team.
- Troubleshooting: finding which of the five stages above has failed, usually from the PLC side first.
- Data and records: where images, results and timestamps land, so they stand up in a quality record.
We do not sell cameras, certify Cognex products or provide Cognex support. The systems integration page describes how we scope controls work.
Limits and open questions
As of November 2026:
- No lifecycle notice is readable. Cognex’s product-status pages were not reachable, so every “mature” and “older” label is inferred.
- The 3900 and 6900 are announced, not fully documented. No model numbers, prices or ship dates appeared in Cognex’s releases, and the 3900’s minimum software version was not stated. Its ingress rating is absent from the releases; Vision Systems Design quotes a Cognex product leader calling it IP67-rated, which we have not seen in a manual.
- The 8900 timeline conflicts. Vision Suite 24.4.0 supports it, while trade press dates the launch to March 2025.
- Edge AI availability by model is not published as a matrix in the sources we read, so confirm per camera.
- Job file formats for the current software may differ from the older
.jobfiles, and we have not verified the extension or conversion path.
Deeper
The three pages below take each decision further.
- Choosing an In-Sight camera: 3800 versus 3900 versus 8900, with 2800 and the 6900, as a decision tree.
- Vision Suite versus In-Sight Explorer: which software runs which camera, and what moved.
- EasyBuilder versus Spreadsheet: the two programming modes and who can maintain each.
For the next system up, see PLC integration, which covers the handshake in detail, and the sibling page on deep learning and AI, which covers the AI tools that run on many of these cameras.
Frequently asked questions
What is a Cognex In-Sight camera?
A Cognex In-Sight is a smart camera: the lens, image sensor, processor, vision tools and network and I/O connections in one body. It takes an image on a trigger, runs an inspection job stored on the camera, and sends a pass or fail and measured values to a PLC or other system. Current models are programmed with In-Sight Vision Suite.
What is the difference between the In-Sight 3800 and the In-Sight 3900?
The 3800, launched in April 2023, comes from 1.6 to 16 megapixels. The 3900, announced on 5 May 2026, goes up to 25 megapixels on a Qualcomm Dragonwing platform, and Cognex states it is up to 4X faster than previous-generation Cognex vision systems without naming the reference. As of November 2026 Cognex's releases give no 3900 prices or ship dates.
Which software programs an In-Sight camera?
The In-Sight 2800, 3800, 3900 and 8900 are programmed with In-Sight Vision Suite. Older families such as the 7000 second generation, 8000 and 9000 use In-Sight Explorer, whose last release we found was 6.5.1 from October 2024. The In-Sight SnAPP sensor is set up from a web browser and needs no installed software.
How do In-Sight cameras connect to a PLC?
Current In-Sight cameras list EtherNet/IP, PROFINET, SLMP, TCP/IP, OPC UA and FTP in Cognex manuals, with Modbus TCP and EtherCAT in Vision Suite help. A wired trigger input and discrete outputs are also available for tight timing. Check the current manual for your model.
Are the In-Sight 7000, 8000 and 9000 obsolete?
We found no Cognex discontinuation notice. Cognex still publishes their manuals, and Explorer 6.5.1 still lists the firmware of the 7000 second generation, 8000 and 9000. In a 2025 CISA advisory, Cognex reports that In-Sight Explorer based vision systems are legacy products not intended for new applications, and the advisory lists the 2000, 7000, 8000 and 9000 series as affected. We call them mature to older, inferred. Ask Cognex about spares and plan a migration for lines that depend on them.
Why does an In-Sight camera miss triggers or drift over time?
The common causes are lighting that changes, a lens or bracket that has moved, a trigger arriving faster than the job can finish, the wrong job loaded after a changeover, and network or clock problems. Cognex states that the trigger interval should be at least 1.5 times the job execution time. Most field failures are setup and maintenance issues, not defects in the camera.
References and further reading
- In-Sight 3800 Reference Manual (Vision Suite 25.3) · Cognex documentationModels, sensors, trigger input specification and the ingress rating conditions.
- In-Sight 8900 Reference Manual · Cognex documentation
- In-Sight 2800 Reference Manual · Cognex documentation
- Cognex launches highest performance embedded AI vision system, In-Sight 3900 · Cognex release, 5 May 2026
- Cognex launches In-Sight vision controller powered by NVIDIA (In-Sight 6900) · Cognex release, 28 April 2026
- Cognex enters new market with launch of In-Sight SnAPP vision sensor · Cognex release, 15 September 2023
- In-Sight Vision Suite EasyBuilder release history · Cognex documentationKnown issues such as the trigger interval rule, and which camera arrived in which release.
- CISA advisory ICSA-25-261-06 · CISACognex's wording on the older In-Sight families.
- In-Sight SnAPP Reference Manual · Cognex documentationThe 1.6 megapixel sensor.
- Scalable, PC-Free AI Inspection with Cognex In-Sight 3900 · Vision Systems DesignInterview with a Cognex product leader, 5 May 2026.