Cognex PLC Integration: Protocols, Handshake and Failure Modes
Cognex FTP Image Archiving: File Naming, Storage and Data Paths
Cognex FTP image archiving: how In-Sight and DataMan write images and results, the file naming question, storage sizing, OPC UA and Edge Intelligence.
A Cognex FTP image archive is easy to start and easy to get wrong. Starting is one function in the job and a folder on a server. Getting it wrong means files that overwrite each other, an archive that cannot be searched, a disk that fills, or images that are skipped under load and nobody notices. This page covers how In-Sight cameras and DataMan readers write images and results out, the file naming question, storage arithmetic, OPC UA and Edge Intelligence, and the network and security side. It is current as of November 2026 and sits under Cognex PLC integration.
How a Cognex device writes images
In-Sight. The Vision Suite WriteImage function in the job takes a storage option: local device, FTP server, SFTP server or TCP server. Cognex recommends FTP or SFTP, not local storage, for large volumes, because continuous triggering can exhaust the camera’s memory. Other settings include the server (with an optional port), a user name (blank means admin), a file path, a file name, a file type (BMP, JPEG or PNG) and overlay graphics. Overlay graphics can be saved as a separate SVG file with the same name, or rendered onto the image. Cognex’s WriteImage help says you can save to the selected storage while Online or Offline. The older WriteImageFTP function and the EasyBuilder FTP export, by contrast, required the camera to be Online.
DataMan. The WebUI’s File Transfer settings send images, result data and verification reports to FTP, FTP for a Mitsubishi GOT, SFTP, TCP (the reader connects out) or a Local TCP Server (the reader listens, image only). Result transfer appends to a text file on the server and needs append permission, not just write.
| Storage option | Carries | Notes from Cognex |
|---|---|---|
| FTP | Images, results, reports | Not encrypted. Cognex recommends SFTP over untrusted networks or to the cloud |
| SFTP | Same | Manuals list FTP for the 2800 and 3800 and SFTP for the 8900. The WriteImage help lists an SFTP server, so confirm your model |
| TCP server (In-Sight) | Image with a header | Header holds image size, type and a 128-byte file name. Cognex’s sample server is not for production |
| Local storage (In-Sight) | Images in camera memory | Fills quickly with continuous triggering. Optional cleanup settings exist |
Three behaviours to test. On FTP, an invalid path or invalid credentials do not return an error from WriteImage, so check the folder rather than the cell. An invalid host can take up to about 30 seconds to time out in the older documentation, and trailing spaces in the host or user name break the write. And in the older WriteImageFTP function, Cognex says it does not guarantee every file is sent when the system is overloaded. We could not confirm that this limit applies to the current function, so prove it on your trigger rate.
File naming
The Vision Suite WriteImage page documents a counter format: a file name such as MyImage|03 gives a zero-filled three-digit counter. The counter ends at the Max Append Value, which defaults to 999, and then resets, so older files are overwritten unless you set it much higher or make names unique.
The timestamp and serial number question is open. The WriteImage page does not document a timestamp in the file name. Older In-Sight 6.1 EasyBuilder help offers Add Timestamp (several formats), Add Link to a string result and Add Counter, in a fixed order. We do not know whether Vision Suite 25 EasyBuilder keeps them, and we do not know whether the File Name parameter accepts a cell reference that builds a name from the time and a serial number. If you need <serial>_<date-time>.png style names, the options we see, all to be tested on the camera, are:
- Use the EasyBuilder link and timestamp options if they exist in your version.
- Build the name in the spreadsheet and test whether File Name accepts the cell.
- Use the TCP server option, where the receiver sets the final name.
- Rename on the server with a script.
Whichever you use, names cannot contain characters such as < > : " / \ | ? *. Note that timestamps depend on the camera clock, which is covered below.

Storage sizing
Cognex publishes no images-per-second limit for the 3800, so size from your own numbers. Illustrative arithmetic only: a 3-megapixel monochrome sensor at 2,048 by 1,536 pixels is 3,145,728 pixels. At one byte a pixel, an uncompressed image is about 3.1 MB.
| Scenario (illustrative) | Images per day | Approximate storage per day |
|---|---|---|
| Every image, 2 per second, 24 hours | 172,800 | About 544 GB |
| Rejects only, at a 2 percent rate | 3,456 | About 11 GB |
| Rejects only, 30-day retention | About 326 GB |
A colour sensor needs roughly three times as much uncompressed. Compressed formats are smaller, but Cognex’s older help says BMP is faster because there is no compression time. In our view, the retention rule is a quality decision (how long a complaint or audit can reach back) made before the storage decision.
OPC UA, Edge Intelligence and MQTT
OPC UA is in the In-Sight 2800, 3800 and 8900 manuals, with an “Enable OPC-UA Server” checkbox in the Vision Suite 26.1 help. In our view it suits values rather than images. We found no OPC UA in the DataMan manuals we searched.
MQTT. The In-Sight Vision Suite release history lists an Enterprise Connectivity utility for managing MQTT connections from release 25.3.0, with image offload added to MQTT forwarding in 26.1.0, and Cognex’s help describes brokers using MQTT v3.1.1 or v5 and certificate options. We did not confirm which In-Sight models support it, and we found no MQTT in the DataMan manuals. Edge Intelligence (EI) is a separate Cognex product, reported by trade press as introduced in March 2021 (Electropages): a hardware box (EI-200, EI-300 or EI-700, supporting about 5, 10 or 20 devices) with a browser interface that monitors and manages DataMan readers, and has built-in MQTT and Sparkplug forwarding, with Ignition and cloud brokers named. Its reference manual, version 1.4, is dated September 2022, and the compatibility list names the DM260, DM280, DM300, DM360, DM370, DM470 and DM503 series, on firmware 5.7.3 or later, and not the DM380 or DM390. We did not confirm its current status or support for newer readers outside Cognex’s Tunnel Manager.
See plant data for what happens to results after they leave the device, and edge and I/O for the gateway choices.
Network and security considerations
- Use SFTP where the model allows it. Cognex describes plain FTP as unencrypted. Credentials and images cross the network in clear text.
- Change the defaults. In-Sight’s default login is
adminwith a blank password. The camera is itself an FTP server, and its file server requires a client with TLS 1.3. The DataMan WebUI is plain HTTP by default, and HTTPS needs a certificate you upload. - Fix the clock. With no time server, the In-Sight clock sits at 1 January 2000 and returns there after every power cycle. Set an NTP or SNTP server and, if it is on another subnet, the default gateway. DataMan timestamps in output strings need an SNTP server too.
- Mind the ports. The 2020 In-Sight port list includes TCP 21 (FTP), TCP 23 (Telnet), 1069 (In-Sight protocol and discovery), 2222 and 44818 (EtherNet/IP), 8087 and 8443 (web HMI). CISA’s September 2025 advisory on older In-Sight Explorer-based systems (ICSA-25-261-06) includes credentials sent unencrypted on TCP 1069. Cognex’s manuals do not publish a DataMan port table that we found, so confirm with a scan.
- Keep it off the production VLAN. In our view, management and archive traffic belongs on an OT management segment. See OT networks and the IEC 62443 pillar. A network review is OT network assessment.
Where it gets hard
- Silent failures. FTP errors do not stop the job, so monitor the destination folder.
- Wrapped counters overwrite old images at the Max Append Value.
- Naming. The timestamp and serial question is unresolved in public documentation.
- Capacity. Storage and retention need an owner and a budget.
- Gated detail. Cognex’s firmware notes and integration downloads are behind its support login.
Back to the Cognex hub, or the sibling PROFINET and TIA Portal page.
Frequently asked questions
How does a Cognex camera save images to an FTP server?
On an In-Sight 3800, the WriteImage function in the job writes images to local storage, an FTP server, an SFTP server or a TCP server. You set the server, credentials, file path, name and file type, and Cognex's help says the file can be saved while the camera is Online or Offline. A DataMan reader does the equivalent through the file transfer settings in its WebUI or the Setup Tool.
Can a Cognex camera name image files with a timestamp or serial number?
We could not confirm it for the current In-Sight Vision Suite. The Vision Suite WriteImage page documents a counter format but not a timestamp. Older EasyBuilder help offered Add Timestamp and Add Link options, and we do not know whether they carry over. Test it on a camera, or let a TCP receiver or a server script set the final name.
Does a Cognex camera use FTP or SFTP?
It depends on the model and the page. Cognex's manuals list FTP for the In-Sight 2800 and 3800 and SFTP for the 8900, while the Vision Suite WriteImage help lists an SFTP server option. The DataMan WebUI offers both, and Cognex says plain FTP is not encrypted and recommends SFTP over untrusted networks or to the cloud.
Can Cognex devices send data over MQTT or OPC UA?
We found OPC UA in the In-Sight 2800, 3800 and 8900 manuals and none in the DataMan manuals we searched. We found no MQTT in the DataMan manuals. The In-Sight Vision Suite release history lists an Enterprise Connectivity utility for managing MQTT connections from release 25.3.0, and Cognex's Edge Intelligence box, a separate product, has built-in MQTT and Sparkplug forwarding, per its 1.4 manual from 2022. Check current status and model coverage.
How much storage do saved camera images need?
Multiply the image size by the images saved per day and the retention period. Uncompressed, one 3-megapixel monochrome image is about 3 MB, so saving every image at two a second is over 500 GB a day, while saving only rejects at a 2 percent rate is about 11 GB. Those are illustrative figures. Measure your own image size and reject rate.
References and further reading
- WriteImage function (Vision Suite 25.3) · CognexStorage options, file naming, counter and overlay settings.
- View files on the device (Vision Suite 25.3) · CognexThe camera as an FTP server, the TLS 1.3 requirement and default login.
- Exporting images via FTP in EasyBuilder (In-Sight 6.1 help) · CognexOlder help that lists timestamp and link naming options.
- Fixed-Mount WebUI Reference Manual (DataMan) · CognexFile transfer to FTP, SFTP and TCP, and the FTP encryption warning.
- Edge Intelligence Reference Manual 1.4 · CognexMQTT and Sparkplug forwarding, hardware models and compatible readers.
- Time Settings utility (Vision Suite help) · Cognex
- In-Sight ports (In-Sight Explorer 6.1.1 help) · CognexThe port list is from 2020; verify against your camera.
- Industrial Ethernet utility help (Vision Suite 26.1) · CognexThe OPC UA server checkbox.
- In-Sight Vision Suite release history · CognexMQTT connections from 25.3.0 and MQTT image offload in 26.1.0.
- Edge Intelligence platform connects customers with IIoT data · Electropages (trade press)Trade-press report of the March 2021 introduction.