Cognex PLC Integration: Protocols, Handshake and Failure Modes
Cognex PROFINET with Siemens TIA Portal: GSDML, Class B and Cycle Time
Cognex PROFINET in TIA Portal: GSDML import, device name, Class B firmware and GSD conditions, cycle time and the Siemens-side handshake.
Cognex PROFINET setup in Siemens TIA Portal is a GSD file, a device name and a cycle time, and then the same trigger-and-result handshake you would write on any other fieldbus. Most problems come from using the wrong GSD file for the device’s firmware, an unnamed or misnamed device, or a result that does not fit the module. This page covers In-Sight cameras and DataMan readers. It is current as of November 2026, built from Cognex manuals, and sits under Cognex PLC integration. The Cognex TIA Portal Integration Guide, which would be the first stop, is on Cognex’s support site behind a login. We could not read it, so what follows is from Cognex’s public manuals.
Cognex PROFINET support by device
Cognex’s manuals list PROFINET Class B for the In-Sight 2800, 3800 and 8900 and for the DataMan DM380 and DM280, and PROFINET for the DM390 and the DM8700 handheld. Examples only: check your model’s current manual. For DataMan, the Class (A or B) depends on firmware, covered below.
GSDML import in TIA Portal
1. Get the file. For In-Sight, Cognex says the GSDML ships inside the Vision Suite install, in the FFP\GSD folder. The file we found in the 25.2 install path is an In-Sight 2800 Class B file, GSDML-V2.42-Cognex-IS2800ClassB-20211119.xml. Whether a separate 3800 file exists is not confirmed. For DataMan, the Setup Tool install offers to download the industrial protocol tools and samples, including GSD files.
2. Install it. In TIA Portal, use Options, then Manage general station description files (GSD), as the DataMan manual describes. In SIMATIC Manager the path is Options, Install GSD File. Cognex’s In-Sight page uses the equivalent “install general station description file” step.
3. Add the device and modules. Drag the device into the network view and assign the I/O modules for result data, SoftEvent and user data.
4. Name it. PROFINET identifies a device by its device name, not its IP address, and the controller can assign the IP at start-up. The name in the project must match the name stored on the device. We did not find Cognex’s own steps for assigning the name in the public manuals, so use the standard TIA Portal “assign device name” function and confirm with Cognex.
5. Download and test. Watch the module diagnostics before testing the handshake.
Class A, Class B and the firmware conditions
This is the part that trips up replacements. Cognex’s Industrial Protocols Manual states the following for DataMan.
| Firmware 6.1.7 or later | Earlier firmware | |
|---|---|---|
| PROFINET stack | New stack, Class B | Siemens stack, Class A |
| GSD version | 2.34 or later, configurations suffixed “CC-B” (for example “DataMan 470 CC-B”) | 2.31 or earlier |
| SNMP | SNMP v2 supported only with the 2.34 GSD file | Not stated |
| Default cycle time | 4 ms | 8 ms |
Cognex says the new stack is “not a drop-in replacement” for a Class A reader, so a reader with newer firmware needs its hardware configuration updated in TIA Portal. If you have a mixed fleet, install both GSD files. Check the firmware before commissioning with the Setup Tool’s System Info view.

Cycle time and network load
Cognex states that the new GSD defaults to a 4 ms cycle, down from 8 ms, and that “while this shortens the network update interval, it also doubles the amount of PROFINET traffic”. Treat that as a design input. On a dedicated machine network it is usually fine. On a shared line network with many devices, review the update time and the switch load. Illustrative: at a 4 ms cycle, a device is updated 250 times a second in each direction (1,000 divided by 4). Twenty readers on one controller at that rate is 5,000 cyclic updates a second each way, so count devices rather than assuming each one is small.
In our view, the update time should come from your timing budget: the trigger-to-result window on the line, as in the RPI example on the EtherNet/IP page, not from the default.
Modules, result size and the Siemens-side handshake
The DataMan PROFINET device exposes I/O modules for result data, SoftEvent and user data. The largest result module gives 246 bytes, so a long string needs result fragmentation, which Cognex describes for PROFINET, or a protocol with more room (see the limits table in Cognex PLC integration). Component Based Automation (CBA) is not supported. To send a DataMan Control Command from the PLC, the Execute DMCC SoftEvent needs the User Data module loaded with the command string.
The handshake is the same sequence as on EtherNet/IP, carried in module bits: Trigger Enable high, wait for Trigger Ready, raise Trigger, see Trigger Ack, release Trigger, read the result when it is available, check the result ID, acknowledge. For In-Sight, Cognex’s PROFINET module tables are in the older Explorer help, and the signal names match the EtherNet/IP ones.
In our view, two Siemens-side habits matter. Copy the result module into a data block once, after the valid bit is set and in a single pass, rather than reading fields piecemeal across scans. And store the ID with the copy. The DataMan manual includes S7-1200 and TIA Portal examples whose project archive TIA Portal extracts, which we did not open. We found no Cognex-authored function block library. The PROFINET Tag Generator in the gated integration guide is the closest thing.
A pre-download checklist
- Read the firmware version on the device and write it on the commissioning sheet.
- Confirm the GSD file version against the firmware class in the table above.
- Confirm the device name in the project, and how it will be written on a spare.
- Check the result module size against the longest string the job can produce.
- Review the cycle time against your timing budget and the network load.
- Test the full handshake with a forced fault: trigger while not ready, and an unacknowledged result. Both should fail in a way the PLC detects.
Where it gets hard
- Wrong GSD for the firmware. The file has to match the firmware class. After a replacement device or a firmware update, confirm which GSD the reader needs.
- Device name mismatches. A device replaced in the field has no name until it is assigned. Plan how the name is written when a spare is fitted.
- Result larger than 246 bytes. The string is cut or needs fragmentation. Size the result before you design the data block.
- Traffic from the 4 ms default. The cycle time doubles traffic against the old default. Check it on shared networks. See OT networks.
- Gated integration guide. The Cognex TIA guide and its tag generator need a Cognex support login. We could not verify their contents.
- In-Sight 3800 details. A separate 3800 GSDML was not confirmed, and the PROFINET result module sizes for In-Sight were not read.
For design and commissioning of a Siemens controls network around a vision device, see commissioning support and controls. Back to the Cognex hub, or the sibling image archiving and data page.
Frequently asked questions
How do I add a Cognex device to TIA Portal over PROFINET?
Install the device's GSD file in TIA Portal through Options, Manage general station description files, then add the device in the hardware configuration, assign its modules and device name, and download. For DataMan, the file you need depends on the firmware: Class B firmware uses GSD version 2.34 or later. Cognex's TIA integration guide is gated behind its support login.
What is the difference between PROFINET Class A and Class B on a Cognex DataMan?
Per Cognex's Industrial Protocols Manual, DataMan firmware 6.1.7 or later installs a new PROFINET stack that is Class B and uses GSD version 2.34 or later with configurations suffixed CC-B. Earlier firmware is Class A on the Siemens stack and uses GSD 2.31 or earlier. Cognex says the new stack is not a drop-in replacement for a Class A reader.
What is the PROFINET result data limit on a Cognex DataMan?
Cognex's manual gives 246 bytes for the largest PROFINET result module, against 470 bytes on EtherNet/IP. For longer strings Cognex describes result fragmentation on PROFINET. Check the manual for your firmware, because the page reference for that limit in the PDF is approximate.
What cycle time does the Cognex PROFINET GSD use?
Cognex states that the new GSD, for firmware 6.1.7 or later, defaults to a 4 ms cycle, down from 8 ms. Cognex also says this shortens the network update interval but doubles the amount of PROFINET traffic. On a busy line network, treat the setting as a change to review, not a default to accept.
Is there a Cognex function block library for Siemens?
We found none. Cognex offers a TIA Portal Integration Guide for In-Sight and DataMan, with a PROFINET Tag Generator file, on its support site behind a login, so we could not read it. The DataMan manual also includes S7-1200 and TIA Portal examples. Ask Cognex for the current download.
References and further reading
- DataMan Industrial Protocols Manual · CognexPROFINET Class A and B, GSD versions, cycle time, modules and result limits for DataMan.
- DM380 Reference Manual · CognexLists PROFINET (Class B) for the DM380.
- DM390 Reference Manual · Cognex
- In-Sight 3800 Reference Manual (Vision Suite 25.3) · CognexLists PROFINET (Class B) for the 3800.
- Import the GSD file for TIA Portal (Vision Suite help) · Cognex
- PROFINET I/O module reference (In-Sight Explorer 5.9.2 help) · CognexOlder module tables for In-Sight.