Cognex
Cognex PLC Integration: Protocols, Handshake and Failure Modes
Cognex PLC integration explained: protocols by In-Sight and DataMan model, the trigger and result handshake, discrete I/O, OPC UA and how it fails.
Cognex PLC integration is the work of making a camera or reader behave like a well-mannered I/O device: the PLC decides when to look, the Cognex device looks, and a result comes back that the PLC can trust and match to the right product. The hardware choices are few. The field problems come from the handshake, the data and the network. This page covers how Cognex In-Sight cameras and DataMan readers talk to PLCs, which protocols each model lists, the trigger, acquire and result sequence, and how it fails. It is current as of November 2026 and built from Cognex manuals. Every device and protocol list here is an example, so check Cognex’s current documentation for your exact model and firmware.
It sits under the Cognex hub and has three deeper pages, listed at the end. For the controls side of a Rockwell Automation network, see Rockwell networks.
Cognex PLC integration protocols by model
The protocol set depends on the model, not the family name. A DataMan DM380 and a DM390 are both fixed-mount readers, and Cognex’s manuals list different protocols for each. The table below is read from the December 2025 DataMan manuals and the 25.3 In-Sight manuals (published 31 October 2025). “No” means the protocol is not in that model’s manual list, which is not a statement that no configuration could ever offer it. We did not open the DM290 or DM580 manuals, so they are not in it.
| Protocol | DM380 | DM390 | DM280 | DM8700 (handheld) | In-Sight 2800, 3800, 8900 |
|---|---|---|---|---|---|
| EtherNet/IP | Yes | Yes | Yes | Yes | Yes |
| PROFINET | Yes (Class B) | Yes | Yes (Class B) | Yes | Yes (Class B) |
| SLMP (Mitsubishi) | Yes | Yes | Yes | No | Yes |
| Modbus TCP | No | Yes | Yes | No | Listed in the 8900 specification table and the Vision Suite 26.1 help (“Modbus TCP Server”), not in the 2800 or 3800 protocol lists |
| CC-Link IE Field Basic | No | Yes | Yes | No | No |
| EtherCAT | No | No | EtherCAT variant only | No | In 26.1 help, “not for all vision systems” |
| OPC UA | Not found | Not found | Not found | Not found | Yes |
| FTP or SFTP image transfer | Not checked | Yes | Yes | Not checked | FTP (SFTP on the 8900) |
| MQTT | Not found | Not found | Not found | Not found | Vision Suite release history lists MQTT connections from 25.3.0; model coverage not confirmed |
Three details matter more than the grid:
- DataMan protocols are off by default. Cognex’s Industrial Protocols Manual says all are disabled except EtherCAT on EtherCAT readers. A reader that “does not answer” on EtherNet/IP is often just not enabled.
- A wireless handheld runs its protocols from the base station. In Studio 5000 you select the reader but enter the base station’s IP address, and PLC triggering is not supported on wireless readers.
- DataMan SLMP reverses the roles. The reader is the scanner (client) and polls the PLC, so the PLC is passive.
Whether two protocols can run at the same time on one device is not stated in the pages we read, so do not design on the assumption either way.

Discrete I/O or fieldbus
Every Cognex camera and reader can be wired as well as networked, and most plants use both. The split is simple.
| Discrete wire | Industrial protocol | |
|---|---|---|
| Best for | Trigger, fast reject or strobe | Job change, results, pass/fail data, diagnostics |
| Timing | Set by the device input and your PLC scan | Set by the update rate (RPI or cycle time) and the PLC scan |
| Carries | One bit per wire | Strings, numbers, IDs, status |
| Cognex figures | In-Sight 3800 trigger input: 24 µs maximum from edge to acquisition start, pulse at least 1 ms; outputs 50 mA maximum per line | Assembly and result size limits by protocol (below) |
The In-Sight 3800 has one opto-isolated trigger input, up to three more general-purpose inputs and up to four high-speed outputs (IS3800 manual). The DM380 has one opto-isolated trigger input, up to three more inputs and up to four outputs, 50 mA per output (DM380 manual).
In our view, put the time-critical edge on a wire and everything with content on the network. A photoeye wired to the trigger input removes the scan and network update from the moment of capture. The protocol then carries the result, with IDs so the PLC can tie the result to the product. See Edge and I/O for the wider design questions.
The Cognex PLC integration handshake: trigger, acquire, result
The handshake below is the one Cognex documents in signal definitions for In-Sight (Explorer 5.x help, with the Vision Suite 25 table using matching names) and in the DataMan Industrial Protocols Manual. Cognex does not publish a single end-to-end timing diagram, so the figure shows the order of events that those definitions imply, not measured durations.
- Enable and wait. The PLC holds Trigger Enable high and waits for Trigger Ready. For In-Sight the camera must be online and its acquisition trigger set to the industrial protocol.
- Trigger. The PLC raises Trigger. The camera sets Trigger Ack and, for In-Sight, increments its Acquisition ID. Trigger Ack stays high until the PLC clears Trigger, so a PLC that never clears it never gets a second shot.
- Acquire and inspect. The camera runs the job. In-Sight can also set Exposure Complete so the PLC knows the product may move.
- Read. When Results Valid (In-Sight) or Results Available (DataMan) goes high, the PLC copies the result. Cognex says to use Results Valid, not only the toggling Inspection Completed bit, to decide when to read.
- Match. Compare the Inspection ID (In-Sight) or Result ID (DataMan) with the Acquisition or Trigger ID you latched. This is how a buffered or late result is not mistaken for the current one.
- Acknowledge. The PLC sets Results Ack. Even with buffering off, the acknowledge is what clears Results Valid. Buffering holds several results; Cognex documents up to 50 sets on a DataMan reader and 500 on a DM8000 base station.
The signal names and assembly layouts differ between In-Sight and DataMan. EtherNet/IP and Studio 5000 shows them side by side, and the ladder pattern is the same shape as any other request and acknowledge pair (see PLC programming).
Job change and result data
Job change. On In-Sight, the older Explorer 5.x documentation describes a command written to the output assembly: Execute Command with a Command ID equal to the job number loads the job whose file name carries that number. In that documentation the camera must be offline (an error code covers a job load requested while online), and Command Executing stays on for a maximum of two seconds. We did not confirm this against the current 3800 help. On DataMan, readers hold stored programs, and the Execute DMCC SoftEvent can send a DataMan Control Command from the PLC, but we did not read the per-protocol job-select mechanism in detail. Treat both as items to prove on the bench.
Result data. The result area has a protocol-dependent size limit, so a long string may not fit.
| Protocol (DataMan) | Result data limit per Cognex’s manual |
|---|---|
| EtherNet/IP | 470 bytes (fixed) |
| PROFINET | 246 bytes (largest result module) |
| EtherCAT | 478 bytes per frame |
| CC-Link IE Field Basic | 1,014 bytes (fixed) |
| SLMP | 3,820 bytes (configurable) |
| Modbus TCP | Up to 4,000 bytes (configurable) |
For longer strings, Cognex describes result fragmentation on PROFINET and CC-Link IE Field Basic, or a protocol with more room such as SLMP or Modbus TCP. The page numbers for these limits in the PDF are approximate, so confirm them in the manual for your firmware.
OPC UA and what it is for
The In-Sight 2800, 3800 and 8900 manuals list OPC UA, and the Vision Suite 26.1 help has an “Enable OPC-UA Server” checkbox in the Industrial Ethernet utility. The camera is the server. We found no OPC UA in any DataMan manual we searched. The Vision Suite release history also lists an Enterprise Connectivity utility for managing MQTT connections from release 25.3.0, and a later release added image offload to MQTT forwarding. We did not confirm which camera models support it.
In our view, OPC UA on a camera suits reading values into a historian, MES or Ignition, not the trigger-and-result handshake. That handshake needs the deterministic, bit-level behaviour of EtherNet/IP or PROFINET. See image archiving and data for how results and images leave the camera, and plant data for where they go.
How Cognex PLC integration fails
These are failure modes drawn from the manuals’ own warnings, with our reading where we say so.
- Trigger while not ready. A trigger raised when Trigger Enable is low, or the camera is offline or still busy, is missed. The In-Sight status flags it as a missed acquisition or acquisition error. Gate your trigger on Trigger Ready.
- Trigger never cleared. Trigger Ack stays high until the PLC clears Trigger, so the next trigger does not fire.
- Reading too early. Results are written to the stack slightly after the job finishes. Cognex says to use Results Valid.
- Stale or mismatched results. With buffering on, an unacknowledged result is presented again. Without ID matching, the PLC can act on an earlier product’s result. We see this as the most dangerous failure because it looks like a good read.
- Buffer overrun. Triggers arriving faster than the PLC acknowledges fill the result buffer. Both families have an overrun bit.
- RPI or cycle too slow. A time delay between the device and the PLC tag depends on the RPI or cycle time. For In-Sight over EtherNet/IP, Cognex recommends an RPI no more than half the time between the camera finishing its job and the PLC needing the data. Illustrative: if the job ends 80 ms after the trigger and the reject decision is due 150 ms after it, the data has a 70 ms window, so the RPI should be no more than 35 ms.
- IP address conflicts. Cognex’s network help strongly recommends disabling DHCP and assigning a static address after the initial configuration, to prevent intermittent DHCP traffic. An integrator’s write-up on a DataMan reader also reports that a subnet mismatch hides the reader in the setup tool.
- Firmware and profile mismatch. The Rockwell Add-On Profile depends on a major revision tied to the camera family. DataMan PROFINET differs by firmware: 6.1.7 or later is Class B and needs a newer GSD file, and Cognex says it is not a drop-in replacement for a Class A reader. After a firmware update or a replacement device, re-check the profile.
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.
- Specification: choosing wired against networked triggering, the protocol per PLC platform and the result size before devices are ordered.
- PLC handshakes: writing and reviewing the trigger, result and acknowledge logic with ID matching and fault handling.
- Commissioning: proving trigger timing, job change and result data on the line, through commissioning support.
- Troubleshooting: tracing missed triggers, stale results and addressing problems.
- Data and network: placing the device on the OT network and routing images and results to data systems, with OT network assessment where needed.
Limits and open questions
- Cognex’s gated downloads. The Rockwell Add-On Profile, the EDS and GSD bundles, the Siemens TIA Portal Integration Guide and firmware release notes are on Cognex’s support site behind a login or rate limit. We did not read them.
- Unread manuals. The DataMan DM290 and DM580 protocol lists were not read.
- Which protocols run together is not stated in the pages we read.
- DataMan job change per protocol and the SoftEvent numbers were not read in detail.
- Trigger latency for DataMan was not checked. The 24 µs figure is for the In-Sight 3800.
- No Cognex-authored timing diagram exists in the sources, so the figure above is derived.
- Omron: we found no Cognex DataMan guide for Omron NJ or NX controllers. Beckhoff coverage is one integrator blog.
Check Cognex’s current documentation and ask Cognex or an integrator for written answers before you rely on any of these.
Deeper
- EtherNet/IP and Studio 5000: In-Sight and DataMan assemblies, EDS against Add-On Profile, RPI and the handshake in ladder terms
- PROFINET and TIA Portal: GSDML import, Class B, cycle time and the Siemens-side handshake
- Image archiving and data: FTP and SFTP, file naming, storage sizing, OPC UA and Edge Intelligence
Across to a sibling: DataMan readers and In-Sight cameras, the devices on the other end of the wire. Back to the Cognex hub, or read about the company behind it.
Frequently asked questions
Which protocols do Cognex cameras and readers use to talk to a PLC?
It depends on the model. Cognex's December 2025 manuals list EtherNet/IP and PROFINET for the DataMan DM380, DM390, DM280 and DM8700, with SLMP, Modbus TCP, CC-Link IE Field Basic or EtherCAT on some of them. The In-Sight 2800, 3800 and 8900 manuals list EtherNet/IP, PROFINET, SLMP, TCP/IP, OPC UA and FTP or SFTP. Always check your model's manual.
Should I trigger a Cognex camera from the PLC or from a photoeye?
Use a wired trigger when the timing must be tight, because a wired trigger skips the PLC scan and network update. Use the protocol trigger when the PLC already knows the right moment and a few milliseconds of jitter is acceptable. Either way, send the results over the protocol and match them to the product with the IDs.
Does DataMan support OPC UA or MQTT?
We found no OPC UA or MQTT in the DataMan manuals we searched (the Industrial Protocols Manual, DM380, DM390, DM8700 and the Fixed-Mount WebUI manual). Cognex's Edge Intelligence box carries MQTT and Sparkplug forwarding for DataMan readers, and the In-Sight Vision Suite release history lists an MQTT connections utility from release 25.3.0. The In-Sight 2800, 3800 and 8900 manuals list OPC UA. Confirm against the current manual for your model.
Why does my PLC read the wrong result for a part?
The usual cause is reading before the camera has finished writing, or reading a buffered result that belongs to an earlier trigger. Cognex says to use Results Valid, not only Inspection Completed, to decide when to read. Compare the result ID with the trigger or acquisition ID you latched, and always acknowledge the result.
Is there a Cognex function block library for my PLC?
Cognex publishes an Add-On Profile for Rockwell ControlLogix and CompactLogix and a TIA Portal Integration Guide for Siemens, but both are on its support site behind a login, so we could not read them. We found no Cognex-authored function block library for Siemens. Ask Cognex or your distributor for the current downloads.
References and further reading
- DataMan Industrial Protocols Manual · CognexProtocol setup, assemblies, handshake and result limits for DataMan.
- DM380 Reference Manual · CognexProtocol list, trigger modes and discrete I/O for the DM380.
- DM390 Reference Manual · Cognex
- DM280 Reference Manual · Cognex
- DM8700 Reference Manual · Cognex
- In-Sight 3800 Reference Manual (Vision Suite 25.3) · CognexProtocol list, trigger input and output electrical limits.
- In-Sight 2800 Reference Manual (Vision Suite 25.3) · Cognex
- In-Sight 8900 Reference Manual (Vision Suite 25.3) · Cognex
- Industrial Ethernet utility help (Vision Suite 26.1) · CognexThe protocol list and the OPC UA server checkbox.
- EtherNet/IP object model and I/O assemblies (In-Sight Explorer 6.2.1 help) · CognexBit-level signal definitions for the In-Sight handshake.
- In-Sight Vision Suite release history · CognexThe 25.3.0 release adds an Enterprise Connectivity utility for MQTT connections.