Book a consultation

Cognex

Cognex DataMan Barcode Readers: Lineup, Protocols and Selection

Cognex DataMan readers explained: fixed-mount and handheld models, current vs mature lineup, protocols by model, selection and how readers fail.

Vladimir Romanov


Cognex DataMan is the company’s family of image-based barcode readers: fixed-mount readers that watch a conveyor, handheld readers that an operator points, and verifiers that grade print quality. Cognex says the line reads “1D, 2D, label-based, and direct part mark (DPM) codes” (10-K for fiscal 2025). For a plant the important questions are which model fits the code and the line speed, which industrial protocol it speaks to your PLC, and what breaks after commissioning.

This page covers the lineup as of November 2026, protocols by model, selection and field failure modes. It sits under the Cognex hub, which is the technology view of Cognex Corporation. The three pages in “Deeper” go further on direct part marks, verification and logistics.

What the Cognex DataMan line is

Image-based, not laser. Every fixed-mount DataMan in the 2025 manuals is an area-scan camera that takes a picture and decodes the code from it. We found no laser-scanner DataMan models in the current documentation, though Cognex has not said so in words we could find. An image-based reader can read several codes in one frame, read 2D symbols, and save the image of a failed read, which is how a no-read gets diagnosed.

Three kinds of device. Fixed-mount readers are mounted over a conveyor and triggered by a photoeye or the PLC. Handheld readers, the DM8700 and older 8000-series models, are used at manual stations and for fallback scanning. Verifiers, covered in barcode verification, measure print quality against a standard instead of just decoding.

Software around the reader. Setup is done in the DataMan Setup Tool on Windows or, for the newer fixed-mount models, in a browser through the WebUI. Cognex states the WebUI “offers the same functionality as the DataMan Setup Tool, with the following differences” (WebUI manual). Edge Intelligence, a separate hardware box, manages and monitors many readers.

The DataMan lineup compared

“Current” below means the model appears in Cognex’s December 2025 documentation set and has 2025 or 2026 launch coverage or a recent manual revision. “Mature” means the manual is still published but the launch was earlier, and we could not find a Cognex end-of-sale or legacy notice. Cognex product pages were not reachable when we researched this, so mature does not mean discontinued. The status column is as of November 2026.

FamilyTypeWhat the sources showStatus
DM290FixedLaunched 14 January 2025. Cognex states AI-powered one-click setup, an all-in-one light and a web interfaceCurrent
DM390FixedDM394 (2048 x 1536) and DM395 (2448 x 2048); AI tuning and an AI Enhancer for damaged codes; manual revised April 2026Current
DM380FixedThree resolutions up to 16 megapixels, IP67; the base of Cognex’s Modular Vision TunnelCurrent
DM580Fixed9 megapixel reader for logistics sorting, designed for Cognex’s Modular Vision Tunnel; released February 2023 per trade pressCurrent
DM280 / DM282FixedCompact, up to 45 Hz; no AI Enhancer; an EtherCAT variant existsMature
DM80 / DM70FixedSmall, low-cost readers; we did not read their detailsMature
DM150, 260, 300, 360, 370, 470FixedEarlier generations; the 300 line introduced changeable lighting and opticsMature
DM8700HandheldIntroduced September 2020; Ethernet through a base station; EtherNet/IP and PROFINETCurrent
DM8600, 8050, 8072HandheldThe DM8600 manual in the December 2025 set is still the 2021 revisionMature
MX-1000, MX-1502, MX-100MobileSmartphone-based terminals from 2016 to 2018; no recent coverage foundMature

Sources: Cognex DM290/390 release, DM390 manual, DM380 manual, DM8700 manual and the DataMan fixed-mount reference. Model digits carry meaning on the 380 and 390: “QL” appears to mean omnidirectional 1D and “X” omnidirectional 1D and 2D. That is our reading of the manual’s table, not a quotation.

Printed label with a barcode and date code stuck on a blue painted wall
A printed label with a linear barcode and a date code: the reader sees a picture, and image quality decides the read.

Algorithms as Cognex names them

Cognex markets its decoders by name, and the names appear on the trademark pages of the December 2025 manuals. 1DMax with Hotbars locates 1D codes at any orientation using texture analysis, then extracts a high-resolution signal to decode, per trade-press coverage of the DataMan 300 launch (Vision Systems). 2DMax with PowerGrid reads 2D matrix and direct part mark codes “inside out”, finding the pattern of modules rather than starting from the finder pattern, so Cognex states it can read codes with a damaged finder pattern, clock pattern or quiet zone (Vision Systems). The newest feature is the AI Enhancer, which Cognex states improves decoding of damaged and degraded codes on the DM290 and DM390. Its WebUI manual says the DM80 and DM280 do not support it.

We found only marketing-level descriptions of how these algorithms work. Treat them as vendor claims and test on your own worst labels.

Protocol support varies by model

The protocol set follows the model, not the family name. This table comes from the December 2025 manuals. We did not open the DM290 or DM580 manuals, so they are absent.

ProtocolDM380DM390DM280DM8700
EtherNet/IPYesYesYesYes
PROFINETYesYesYesYes
SLMP (Mitsubishi)YesYesYesNot listed
Modbus TCPNot listedYesYesNot listed
CC-Link IE Field BasicNot listedYesYesNot listed
EtherCATNot listedNot listedEtherCAT variant onlyNot listed

Three details matter at commissioning. All protocols are disabled by default, except EtherCAT on EtherCAT readers (Industrial Protocols Manual). A wireless DataMan 8000 or 8700 runs its protocols from the base station, so you enter the base station’s address in the PLC, and PLC triggering is not supported on wireless readers. And we found no MQTT or OPC UA in any DataMan manual: Edge Intelligence forwards MQTT with Sparkplug, but that is a separate box. In-Sight is different, so do not assume tags and assemblies carry over between the two families (see EtherNet/IP and Studio 5000).

How the PLC handshake works

On EtherNet/IP a DataMan presents a vendor-specific ID Reader Object with one input assembly and one output assembly. The sequence below is our summary of the manual’s wording. Cognex does not publish an end-to-end timing diagram, so check the manual for your model.

PLC and DataMan trigger handshake over EtherNet/IP Two lanes, the PLC on the left and the reader on the right, with six numbered steps. One: the PLC sets Trigger Enable. Two: the reader signals Trigger Ready. Three: the PLC raises Trigger from 0 to 1. Four: the reader signals Trigger Ack and acquires and decodes. Five: the reader sets Results Available, and the PLC matches the Result ID to its Trigger ID. Six: the PLC sets Results Ack to clear the result. PLC DataMan reader 1 Trigger Enable set 2 Trigger Ready 3 Trigger goes from 0 to 1 4 Trigger Ack, then acquire and decode 5 Results Available (match Result ID to Trigger ID) 6 Results Ack clears the result
The handshake is six steps, and the failure to design for is step 5: the PLC must match the result to the trigger that caused it, or a late result gets attached to the wrong product.

The input assembly carries the status bits, a Trigger ID, a Result ID and the result data. The manual caps EtherNet/IP result strings at 470 bytes and PROFINET at 246 bytes for the largest module, so a long GS1 string may need result fragmentation or a protocol with more room (Industrial Protocols Manual). Siemens and Mitsubishi readers are covered in PROFINET and TIA Portal.

How to select a DataMan reader

  1. Start with the code and the mark. Printed label, inkjet date code or a mark on metal? Metal marks push you toward lighting choices, see DPM reading.
  2. Work out pixels on the narrowest bar. Sources quote 3 to 5 pixels across the narrowest element as design margin, which sets the resolution for your field of view. That is margin, not a standard.
  3. Check line speed against exposure. Motion blur in pixels equals speed times exposure divided by pixel size. At an illustrative 0.5 metres per second, a 100 microsecond exposure and a 0.2 millimetre pixel footprint, blur is about 0.25 pixel. Slow the exposure and the same line blurs.
  4. Pick the lighting package. Integrated lights, external lights and polarising covers each change what the camera sees.
  5. Confirm the protocol for your PLC in that model’s manual, not the family datasheet.
  6. Decide about damaged codes. If labels arrive scuffed, the AI Enhancer is on the 290 and 390 and not on the 80 or 280.
  7. Check for tunnels. Multi-side reading on a conveyor starts from the 380 or 580, see logistics scanning.

How a DataMan fails in the plant

Code quality. The print passes in the print room and fails at line speed because contrast, quiet zone or ribbon wear has drifted. A reader that decodes a poor code today may not tomorrow. Grade the print, do not only read it.

Glare and lighting. Shrink film, wet product and metal return light straight into the lens. Polarisation, a dome or a changed angle fixes it. Ambient light from windows or forklift lights breaks a setup that worked at commissioning.

Motion blur and line speed. The line speeds up by 10 percent after commissioning and the exposure that worked now blurs. The reader reports no-reads and nobody checks the image.

Mounting. A loosened bracket or a knocked lens changes focus and angle. Mount rigidly and photograph the setup.

Trigger and result mismatch. A late result attached to the wrong carton, or a PLC that reads results before Results Available is set.

Protocol and firmware surprises. Older firmware uses a different PROFINET stack, so a replacement reader is not drop-in, and the GSD file and hardware configuration must change. A wireless handheld cannot be triggered from the PLC. After a reader swap, the configuration may not come across unless backed up.

Plain FTP on the plant network. Cognex’s own manual notes that FTP is not encrypted and recommends SFTP over untrusted networks or to the cloud. The WebUI also runs over HTTP unless you upload a certificate.

Lifecycle: what Cognex has and has not said

The mobile SDK has a reported end date. Search excerpts of Cognex’s developer portal state that the Cognex Mobile Barcode SDK, from the Manatee Works acquisition, was discontinued with an official end date of 30 September 2025, and a software vendor’s migration guide also gives 30 September 2025 as the end-of-life date (Scanbot SDK, a competitor, not a Cognex source). We could not open the Cognex portal itself, so treat the date as reported, not confirmed. It is the only DataMan-adjacent end-of-life statement we found.

Everything else is unstated. Cognex has not published a lifecycle table we could reach without a login. Older fixed-mount and handheld families still have manuals, which is not a lifecycle statement. If you run a 370 or 470, ask Cognex or your distributor about repair and spares before you need them. Edge Intelligence has a 2022 manual and does not list the newest readers in its compatibility list, so confirm current support.

What we do here

Our team integrates 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. In practice that means:

  • Specifying readers from the code, line speed, lighting and protocol, before anyone orders hardware.
  • PLC handshakes: trigger, results, result matching and job change, written and tested against the model’s manual.
  • Commissioning: lighting, focus, mounting and read-rate checks on real production product.
  • Troubleshooting no-reads from stored images, not from guesses.
  • Backups and configuration control so a reader swap takes minutes.

For the programming side, see PLC programming and systems integration.

Limits and open questions

  • We did not open the DM290 or DM580 manuals, so their protocols are unconfirmed.
  • Lifecycle status of the 150, 260, 300, 360, 370, 470 and 475 is unconfirmed.
  • Cognex’s job-change mechanism over each protocol and the DataMan network port list were not found.
  • We cannot say which models read and parse GS1 Digital Link URLs, see barcode verification.
  • Algorithm performance claims are Cognex’s and untested by us.

Deeper

For code on a vision camera instead of a reader, see the PLC integration page.

Frequently asked questions

What is a Cognex DataMan?

DataMan is Cognex's family of image-based barcode readers. Cognex says the line reads 1D, 2D, label-based and direct part mark codes and includes fixed-mount readers, handheld readers and barcode verifiers. Image-based means the reader captures a picture of the code and decodes it in software, rather than sweeping a laser across it.

Which DataMan models are current in 2026?

As of November 2026 the newest fixed-mount models are the DM290 and DM390, launched in January 2025, plus the high-resolution DM380 and DM580 for logistics. The DM8700 is the handheld with a current manual. Older families still have manuals, but we found no Cognex lifecycle table, so ask Cognex or your distributor before relying on spares.

Do DataMan readers support EtherNet/IP and PROFINET?

Cognex's December 2025 manuals list EtherNet/IP and PROFINET for the DM380, DM390, DM280 and DM8700. Other protocols vary by model: SLMP, Modbus TCP and CC-Link IE Field Basic appear on some, and EtherCAT only on the DM280 EtherCAT variant. Check the manual for your exact model before you buy.

Can a DataMan reader send data over MQTT or OPC UA?

We found no MQTT or OPC UA support in the DataMan manuals we read. Cognex's Edge Intelligence box can forward reader data over MQTT with Sparkplug, but that is a separate device. In-Sight cameras, by contrast, list an OPC UA server. Confirm current capability with Cognex before designing around either.

What happened to the Cognex Mobile Barcode SDK?

Excerpts of Cognex's developer portal, as returned by search in November 2026, state that Cognex discontinued the Cognex Mobile Barcode SDK and the Manatee Works Barcode Scanner SDK, with an official end date of 30 September 2025, and that existing subscriptions ended then with no updates or support afterward. The excerpts add that teams wishing to keep using the SDK should contact Cognex about a no-cost licence. We could not reopen the portal itself (its address did not resolve for us on 20 November 2026), so confirm the status with Cognex before relying on it.

References and further reading

  1. DataMan Industrial Protocols Manual (release 25.4.1.1) · Cognex documentationEtherNet/IP assemblies, PROFINET, SLMP, Modbus TCP, EtherCAT and the result-size limits.
  2. DataMan 380 Reference Manual · Cognex documentationTrigger modes, I/O, resolutions and the protocol list for the high-resolution reader.
  3. DataMan 390 Reference Manual · Cognex documentation
  4. Fixed-Mount WebUI Reference Manual · Cognex documentationAI Enhancer, file transfer to FTP and SFTP, HTTP and HTTPS behaviour.
  5. Cognex DataMan 290 and 390 launch release, January 2025 · Cognex (release reprint)
  6. Cognex Form 10-K for fiscal 2025 · Cognex / SEC filingHow Cognex describes the DataMan line and its image-based readers.

← Cognex

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.