Book a consultation

Cognex PLC Integration: Protocols, Handshake and Failure Modes

Cognex EtherNet/IP with Studio 5000: Assemblies, EDS and AOP

Cognex EtherNet/IP in Studio 5000: In-Sight and DataMan assemblies, the 470-byte DataMan result cap, EDS against Add-On Profile, RPI and the handshake.

Vladimir Romanov


Cognex EtherNet/IP setup in Studio 5000 comes down to one decision and one habit. The decision is whether to add the camera or reader through the Cognex Add-On Profile (AOP) or through its EDS file. The habit is to treat the camera as an I/O module with a handshake, not as a source of values you can read at will. This page covers both In-Sight cameras and DataMan readers, because the two families use different EtherNet/IP layouts and mixing them up is a common source of dead tags. It is current as of November 2026 and sits under Cognex PLC integration.

Cognex EtherNet/IP assemblies: In-Sight against DataMan

Both families are EtherNet/IP servers that exchange an input assembly (device to PLC) and an output assembly (PLC to device). The layouts differ.

In-Sight (2800, 3800, 8900 generation)DataMan fixed-mount and handheld
Object modelIdentity, Ethernet Link, TCP/IP, Assembly and a Vision ObjectVendor-specific ID Reader Object (class 0x79)
Input assemblyInstance 13, up to 500 bytesInstance 11, 500 bytes
Output assemblyInstance 22Instance 21, 500 bytes
Result areaBytes 16 to 499, inspection results (484 bytes)Bytes 16 to 499, but the maximum result string is 470 bytes
Correlation fieldsAcquisition ID, Inspection ID, Current Job IDTrigger ID, Result ID
PLC to device dataUser Data from byte 8User Data from byte 8 (492 bytes), with option and length fields
Control bitsTrigger Enable, Trigger, Buffer Results Enable, Inspection Results Ack, Execute CommandTrigger Enable, Trigger, Buffer Results Enable, Results Ack, SoftEvent
Buffered resultsDocumented as up to 8 sets in the 5.x firmware helpUp to 50 sets on a reader, 500 on a DM8000 base station
Input assembly layouts compared: In-Sight and DataMan Two horizontal bars of byte ranges. The In-Sight input assembly has status bytes 0 to 3, then error ID, command result code, current job ID, acquisition ID, inspection ID and inspection result code, each two bytes, then inspection results from byte 16 to 499. The DataMan input assembly has status bits in bytes 0 to 1, SoftEvent acknowledge in byte 2, bytes 3 to 5 unlisted, then trigger ID, result ID, result code, extended result and data length, each two bytes, then result data from byte 16 to 499 with a maximum string of 470 bytes. In-Sight input assembly, Vision Suite 25.x table (camera to PLC) Bytes 0-3 Status bits 4-5 Error ID 6-7 Cmd result 8-9 Job ID 10-11 Acq ID 12-13 Insp ID 14-15 Code 16-499 Results (484) DataMan input assembly, instance 11 (reader to PLC) Bytes 0-1 Status 2 SoftEvent 3-5 unlisted 6-7 Trigger ID 8-9 Result ID 10-11 Code 12-13 Extended 14-15 Length 16-499 Data (max 470) Both are 500-byte inputs with result data from byte 16. The status bits, the ID fields and the cap differ, so tags are not interchangeable.
The result data sits at byte 16 in both layouts, which makes them look alike. The fields in front of it do not match, and the DataMan string stops at 470 bytes.

The In-Sight layout above is the Vision Suite 25 table, published on the In-Sight 2800 page. We inferred bit positions from the older, bit-level Explorer 5.x table, so confirm bit-level names against the tags Studio 5000 generates for your camera.

The practical consequence: a PLC routine written for a DataMan result block will not work on an In-Sight, and the reverse. The result bytes start at the same offset, but the status bits and ID fields in front of them do not match.

EDS or Add-On Profile

There are three ways to add the device in Studio 5000. They are not equivalent.

RouteWhat you getCognex’s notes
Add-On Profile (AOP)Named tags, adjustable data size, module defined in the Studio 5000 treeOnly for ControlLogix and CompactLogix. A Cognex download, installed with its own setup program. If installed, the EDS-generated profile is hidden
EDS-generated profileA module from the registered EDS fileIn-Sight in Studio 5000 versions 21 to 25: input and output assemblies fixed at 496 bytes each. Use the Logix5000 EDS installer, not the RSLinx one
Generic Ethernet ModuleYou enter the assembly instances and sizes yourselfRequired for Studio 5000 (RSLogix 5000) version 19 and earlier. Input 13 and output 22 for In-Sight 5.x and later firmware

AOP downloads are gated. Cognex hosts the AOP installer on its support site, which asks for a login and, when we tried, rate-limited automated access. We could not read or test it, and Rockwell’s public site does not carry it. Cognex’s In-Sight documentation says the AOP installs a major revision tied to the camera family, and the 3800 is not named in the page we read, so ask Cognex which revision applies to your camera and firmware. For DataMan, Cognex’s manual says to select the Add-On Profile and Samples when installing the Setup Tool, and to redo the EDS install if the reader shows as a question mark in RSLinx.

Cognex also ships L5X copy-rung files with In-Sight Explorer that map the generic tags into structured ones. Whether Vision Suite 25 still ships them is not confirmed.

Rack of network cables in teal and yellow lit by green light
The module is only as dependable as the cable and switch port behind it: label the port, and fix the IP address before the PLC download.

RPI and module settings

For an In-Sight camera, Cognex supports cyclic connections of 2 to 8000 ms and recommends an RPI no more than half the time between the camera finishing its job and the PLC needing the data. Illustrative: a job that finishes 60 ms after the trigger and a reject gate that needs the answer at 140 ms leaves an 80 ms window, so an RPI of 40 ms or less. In our reading, each handshake step also costs up to one RPI in each direction, so a request and acknowledge pair can add roughly two RPIs before the PLC acts.

Other module settings Cognex documents for the AOP: a name (the tags derive from it, and Cognex suggests using the camera’s name), IP address, an optional “Major Fault on Controller if connection fails”, and an inhibit option. Toggling the module’s inhibit can recover a camera stuck in “Standby”. The PLC must be offline to add the connection. For a DataMan, the manual lists connection types including input-only and exclusive owner, and notes that the delay between reader and PLC tag values depends on the RPI. Add UserData manually to the output assembly in the module definition.

The handshake in ladder terms

The sequence is in Cognex PLC integration. As ladder, it is five small routines, and each is a request and acknowledge pair of the kind covered in PLC programming.

  1. Arm. Hold Trigger Enable on while the cell is in production. This is a plain output, OTE, from your run permissive.
  2. Request. An XIC on Trigger Ready, ANDed with your product-present condition, latches the request. Do not raise Trigger unless Trigger Ready is high.
  3. Release. An XIC on Trigger Ack unlatches the request, so Trigger falls. Trigger Ack stays high until you do, so skipping this rung blocks the next trigger.
  4. Capture. On Results Valid (In-Sight) or Results Available (DataMan), copy the result block with COP into a UDT with a layout that matches your format, and store the Inspection ID or Result ID. Studio 5000 types the whole array as one type, so mixed data needs this copy.
  5. Acknowledge. After the copy, set Results Ack for one scan, then clear it. Compare the stored ID with the trigger’s ID before the result is allowed to release or reject a product.

For more depth on how this style of logic fits with the rest of the controls design, see Rockwell networks.

Where it gets hard

  • The right AOP for the firmware. Cognex ties the AOP to the camera family and revision, and the profile has to match. We could not confirm which revision the 3800 uses. After a camera swap or firmware update, check the profile again.
  • Assembly sizes. The EDS profile’s fixed 496 bytes and the 500-byte assembly limit mean a long result does not fit. DataMan’s string stops at 470 bytes.
  • Wireless handhelds. A DataMan 8000-series or 8700 runs its protocols from the base station, so you enter the base station’s IP address, and PLC triggering is not supported on wireless readers.
  • Bit positions inferred. For In-Sight, our bit-level names for the 25.x table are inferred from the 5.x table. Read the generated tags.
  • No public sample logic. We found no Cognex or Rockwell sample Add-On Instruction for In-Sight. Cognex ships DataMan samples with its Setup Tool, which we did not open.
  • Other PLC brands. For Omron we found no Cognex DataMan guide. One integrator write-up covers a DataMan with a Beckhoff scanner terminal. See the PROFINET and TIA Portal page for the Siemens route.

Back to the Cognex hub and the Rockwell Automation hub.

Frequently asked questions

How do I add a Cognex camera to Studio 5000?

Install either the Cognex Add-On Profile or the device's EDS file, then add the device as a module under the EtherNet/IP bridge with a name, IP address, data size and RPI. The PLC must be offline to add the connection. The Add-On Profile is a Cognex download behind its support login, so ask Cognex or your distributor for the current version.

What are the DataMan EtherNet/IP assembly instances?

Cognex's Industrial Protocols Manual describes a vendor-specific ID Reader Object with one input assembly, instance 11, and one output assembly, instance 21, both 500 bytes. Result data is capped at 470 bytes. In-Sight cameras use a different layout, instances 13 and 22 in the documentation we read, so the two families' tags are not interchangeable.

Should I use the EDS file or the Add-On Profile?

The Add-On Profile creates named tags and lets you change the data size. The EDS route works without it but, for In-Sight in Studio 5000 versions 21 to 25, Cognex documents fixed 496-byte input and output assemblies. The Add-On Profile is only for ControlLogix and CompactLogix. Pick one: Cognex says installing the profile hides the EDS-generated one.

What RPI should I use for a Cognex camera?

For In-Sight, Cognex supports cyclic connections of 2 to 8000 ms and recommends an RPI no more than half the time between the camera finishing its job and the PLC needing the data. DataMan's manual notes that the delay between reader and PLC tag depends on the RPI. Set it from your timing budget, not the default.

Why does the PLC trigger my Cognex camera but never see a result?

Common causes are the acquisition trigger not set to the industrial protocol, the camera offline, results not acknowledged, or reading before Results Valid. For a wireless DataMan handheld, PLC triggering is not supported at all. Check the module status and the Trigger Ready bit first, then the acknowledge.

References and further reading

  1. In-Sight EtherNet/IP connection using the Add-On Profile (Vision Suite 25.3) · CognexModule settings, RPI guidance and the inhibit tip.
  2. Install the Add-On Profile (Vision Suite 25.2) · CognexThe installer is on Cognex's support site.
  3. Install the EDS file (Vision Suite 5.0 help) · Cognex
  4. EtherNet/IP object model and I/O assemblies (In-Sight Explorer 6.2.1 help) · CognexBit-level signal definitions and the handshake.
  5. Communicate with a Rockwell ControlLogix PLC (In-Sight Explorer 5.7.3 help) · CognexThe Add-On Profile major revision note and the statement that the AOP hides the EDS-generated profile.
  6. Input assembly 13, Vision Suite 25 table · Cognex
  7. Output assembly 22, Vision Suite 25 table · Cognex
  8. DataMan Industrial Protocols Manual · CognexThe ID Reader Object, assemblies 11 and 21, and the Studio 5000 procedure.
  9. Importing the EDS-generated profile with L5X files (In-Sight Explorer 6.1.1 help) · Cognex

← PLC Integration

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.

The Plant-Side Brief

The weekly brief for the people who own a plant’s control systems.

One email every Wednesday for engineering and operations leaders responsible for controls, SCADA, MES and OT networks. Skim the top in two minutes; read the Deep Dive when you have fifteen.

  • One modernization problem, worked through to cost, risk and a schedule you can defend. The Deep Dive.
  • End-of-support dates before they reach your plant Windows, servers, controllers and HMI software. Lifecycle Watch.
  • A checklist your engineers can run that week not a framework to admire. Field Kit.
  • Every number sourced, no vendor agenda we are paid by plants, never by vendors.