Choosing a Datalogic Impact System: P2X/P3X Smart Camera or MX-E Vision Processor?
One Impact Platform for Machine Builders, Integrators and End Users
When configuring a Datalogic Impact system, the first decision is the system architecture. A single inspection position can often be solved efficiently with a P2X or P3X smart camera. When the machine has multiple inspection positions, line-scan requirements, higher resolution, or central PLC communication, an MX-E vision processor is usually the more logical architecture. The strength of Datalogic Impact is that both routes use the same software platform. The P2X and P3X smart cameras run the same Impact environment as the MX-E vision processors, including the MX-E25, MX-E45 and MX-E90.
For machine builders and integrators, this means that the same Impact knowledge remains usable across different machine configurations. A compact machine can be equipped with a P2X or P3X smart camera, while a more advanced version with multiple inspection positions can be built around an MX-E processor. The engineer continues to work with the same Impact tools, the same configuration logic and the same way of testing and diagnosing. This standardisation is also why we combine Datalogic Impact training within the Machine Vision Academy with practical choices around camera, lens, lighting, triggering and PLC communication.
For end users who want to work with Datalogic Impact themselves, this recognisable platform is just as important. Operators do not need to learn a different interface for every inspection cell. Maintenance technicians recognise the same diagnostic environment. Engineers can use the same configuration approach on a compact smart camera and on a high-end MX-E system. This reduces the training effort and makes it easier to build internal vision knowledge.
Impact works with configurable drag-and-drop tools. An inspection is built by placing tools, setting parameters, linking results and configuring communication with the machine. Classical software programming knowledge, as required for a fully custom vision application, is not required. The technical quality of the inspection is determined by the combination of camera, lens, lighting, triggering, processing and PLC communication. Impact makes the inspection configurable, but measurement reliability only occurs when these components are designed as one system.
The page about Datalogic Impact machine vision software explains the software environment in more detail. This page focuses on the system choice around Datalogic Impact: when a P2X or P3X smart camera fits, when an MX-E processor becomes the more logical choice, and which components together determine whether the inspection will remain reliable in production.
Datalogic Impact Smart Camera or MX-E Processor: Choose from the Inspection Positions
A Datalogic P2X or P3X smart camera is logical when one inspection position can operate independently. Sensor, processor, communication and optionally lighting are integrated in one compact housing. This keeps the mechanical and electrical integration straightforward. The camera is mounted directly at the product, processes the image locally and communicates the result to the machine. For presence checks, label inspection, code reading or simple measurement and position checks, this can be a very efficient setup.
A Datalogic MX-E system becomes interesting as soon as the machine has multiple inspection positions or when the inspection task requires more freedom in camera selection, lighting and processing. The MX-E processor is usually installed in or near the control cabinet. The GigE cameras are mounted at the inspection positions. This allows the right camera, lens and lighting to be selected for each position. One position may require a fast monochrome camera, while another position may need higher resolution, colour information or line-scan. Processing, diagnostics, recipe structure and PLC communication remain centralised in the same Impact environment.
From two inspection positions onwards, a Datalogic MX-E system often also becomes economically interesting. Multiple separate smart cameras each have their own processor, housing, connection structure, configuration and maintenance point. In an MX-E system, multiple GigE cameras are processed centrally on one industrial vision processor. The cameras primarily function as image acquisition devices, while software management, diagnostics and communication remain centralised. This can make the total system architecture more transparent, especially when the inspection positions are located within the same machine or the same part of the production line.
The choice should therefore not be based only on the price of one camera. With multiple inspection positions, cabling, spare parts, training, diagnostics, PLC connection, recipe management and future expansion also matter. A Datalogic P2X or P3X is strong for a compact and independent inspection point. A Datalogic MX-E25, MX-E45 or MX-E90 is a better fit when multiple cameras, central processing, line-scan or expandability become important.
Datalogic MX-E25, MX-E45 and MX-E90 as Central Vision Processors
The Datalogic MX-E series consists of industrial vision processors that run Impact and connect to external GigE cameras. The MX-E25 is intended for compact systems with up to two cameras. The MX-E45 supports up to four cameras and provides more performance margin for industrial multi-camera applications. The MX-E90 is intended for more demanding systems with higher resolution, higher speed, line-scan or multiple inspection positions and can support up to eight PoE GigE cameras, depending on the version. The MX-E series also supports industrial communication such as EtherNet/IP, Profinet, Modbus TCP and OPC, allowing OK/NOK signals, measurement values, status information and recipe data to be exchanged with the PLC.
| MX-E model | Typical role in the Impact system | Camera setup | Technical application |
|---|---|---|---|
| MX-E25 | Compact Datalogic Impact system | Up to 2 GigE/PoE cameras | For small multi-camera systems and straightforward inspection tasks |
| MX-E45 | Industrial multi-camera processor | Up to 4 GigE/PoE cameras | For multiple inspection positions with more processing margin |
| MX-E90 | High-performance Impact processor | Up to 8 GigE/PoE cameras | For high resolution, line-scan, higher speed and extended PLC integration |
The right MX-E model is not determined only by the number of cameras. Resolution, frame rate, inspection time, tool complexity and communication timing together determine how much processing margin is required. Two high-resolution cameras with extensive inspection tools can create more processor load than four simple low-resolution cameras. Line-scan applications create load in a different way, because a high line rate generates a continuous data stream that must be processed synchronously with encoder information and PLC results.
In an MX-E system, industrial integration must be included directly in the hardware choice. The processor is usually located in or near the control cabinet, while the cameras, lighting and triggers are mounted on the machine. As a result, cable lengths, PoE power, trigger/strobe signals, PLC interface and service accessibility become part of the same system architecture. A good MX-E system therefore does not consist only of a processor and cameras, but of a complete configuration with lenses, lighting, cabling, I/O and industrial communication.
GigE Cameras on MX-E: Resolution, Shutter and Colour Choice
External GigE cameras are connected to the MX-E series. In an industrial machine, compatibility is more important than theoretical freedom. Camera discovery, PoE behaviour, trigger lines, strobe outputs, firmware and Impact support determine how quickly a system can be built, tested and maintained. For this reason, Datalogic M and E series cameras are a logical choice for Datalogic MX-E systems when the application allows it.
The most commonly used area-scan cameras cover a practical range from VGA to 5 MP, in grayscale and colour. Monochrome is usually the best choice for shape, position, presence, contrast and measurement inspection. The camera directly records intensity information, which is often favourable for stable thresholds, edge detection and measurements. Colour is required when the inspection criterion is truly based on colour difference, for example in label inspection, product variant checking or verification of coloured parts.
| Grayscale model | Colour model | Resolution | Sensor | Shutter | Max. frame rate | Typical application |
|---|---|---|---|---|---|---|
| E101 | E101C | 640 × 480 | 1/4” CMOS | Global | 376 fps | Fast presence check, positioning or simple detection |
| E151 | E151C | 1280 × 1024 | 1/2” CMOS | Global | 88 fps | General inspection with a good balance between speed and detail |
| E181 | E181C | 1920 × 1200 | 2/3” CMOS | Global | 50 fps | Detail inspection with global shutter on moving products |
| M197 | M197C | 2592 × 1944 | 1/2.5” CMOS | Rolling | 14 fps | 5 MP inspection of stationary or controlled moving products |
| E198 | E198C | 2448 × 2048 | 2/3” CMOS | Global | 23 fps | 5 MP inspection where movement and geometry are critical |
The shutter choice must be directly linked to product movement and lighting. With global shutter, all pixels are exposed at the same time. This is beneficial for conveyor movement, vibration or short flash exposure. Rolling shutter can work well when the product is stationary or moves in a controlled way, but is less suitable when movement during exposure can cause geometric distortion. The correct camera therefore follows from the combination of product movement, exposure time, lens magnification and inspection tolerance, not only from the number of pixels.
Higher resolution only provides additional measurement information when the machine vision lens achieves the required object resolution across the full inspection field. The lens, working distance, aperture and depth of field determine whether the extra sensor pixels are actually usable. When the product moves outside the depth of field, the optics lose detail at the edge of the image field, or the exposure time causes motion blur, the result is a larger image file without higher measurement certainty. This is why camera selection must always be made together with machine vision lighting and lens selection.
Datalogic Line-Scan Cameras for MX-E Systems
Line-scan cameras are used when the product moves continuously, is very long, or must be inspected around a cylindrical object. The camera does not capture a full image at once, but builds the image line by line while the product moves. The image geometry is therefore determined by line rate, object speed, encoder resolution and lens magnification. A line-scan application is always a system of camera, mechanics, encoder, lens, lighting and processing.
| Line-scan model | Resolution | Max. line rate | Pixel size | Lens mount options | Typical application |
|---|---|---|---|---|---|
| M565 | 2048 pixels | 51 kHz | 7 µm × 7 µm | C, F, M42 | Fast inspection of narrower web widths |
| M570 | 4096 pixels | 26 kHz | 7 µm × 7 µm | F, M42 | Print, film or material inspection with higher resolution |
| M575 | 6144 pixels | 17 kHz | 7 µm × 7 µm | F, M42 | Wider webs where detail becomes more important than maximum speed |
| M580 | 8192 pixels | 12 kHz | 3.5 µm × 3.5 µm | F, M42 | Very high resolution over a large width with high optical demands |
In line-scan, the line rate determines how much exposure time is available per image line. A higher line rate requires shorter exposure and therefore more light output. With smaller pixels, such as an 8K camera with 3.5 µm pixels, the combination of lens quality and line lighting becomes even more important. The lens must deliver the required object resolution across the full sensor width, while the lighting must capture every line with comparable contrast.
Line-scan applications fit well with a Datalogic MX-E45 or MX-E90 architecture. The processor receives the data stream, performs the inspection, links results to product position and communicates with the PLC. When additional inspection zones are added later, the same Impact environment remains available and the system architecture can be expanded without moving to another software platform.
Datalogic P2X Smart Cameras for Compact Inspection Positions
The Datalogic P2X series is intended for compact inspection positions where camera, processor, lens and optional lighting can be combined in one smart camera. The series is available with qHD and 2 MP resolution, both in monochrome and colour. The qHD models use larger 5.6 µm pixels, while the 2 MP models use smaller 2.8 µm pixels. This difference affects the balance between detail, exposure time and light requirement.
| P2X version | Resolution | Mono/colour | Pixel size | Sensor frame rate | Lens options |
|---|---|---|---|---|---|
| P20M | qHD | Monochrome | 5.6 µm | 60 fps | Micro-video or C-mount |
| P20C | qHD | Colour | 5.6 µm | 60 fps | Micro-video or C-mount |
| P22M | 2 MP | Monochrome | 2.8 µm | 60 fps | Micro-video or C-mount |
| P22C | 2 MP | Colour | 2.8 µm | 60 fps | Micro-video or C-mount |
The P2X can be configured with micro-video lenses or C-mount optics. Micro-video is compact and practical when working distance and field of view remain within standard limits. C-mount becomes interesting when the optical requirements are higher, for example in measurement applications, small details, larger working distances, or when a telecentric lens is required to limit perspective errors. The software can only measure reliably when the required information is optically delivered to the sensor correctly.
The integrated lighting is available in compact and more powerful versions, with light colours such as white, red, infrared and blue. The choice of light colour and lighting geometry depends on material, surface and inspection objective. Red light is often strong for monochrome contrast tasks, blue light can emphasise surface details, infrared can suppress colour differences, and white light is logical when colour information is required. With glossy surfaces, relief, films or scratch detection, external lighting may be the better choice, because reflections, shadows or low-angle illumination can then be controlled more precisely.
For P2X systems, the CBX connection box is often a practical part of the system setup. Power, trigger, outputs, shielding and service-friendly cabling are connected in a clear way. This makes the installation more reproducible and easier to maintain, especially when the same inspection setup is used in multiple machines.
Datalogic P3X Smart Cameras When More Resolution Is Required
The Datalogic P3X series builds on the same smart camera architecture and adds, among other options, 5 MP versions. This makes the P3X interesting when one compact inspection position must be maintained, but more resolution or more processing margin is desired. The P3X is available in qHD, 2 MP and 5 MP, in monochrome and colour. The frame rate differs per resolution and colour version, so the system choice is again determined by detail, speed and light.
| P3X version | Resolution | Mono/colour | Max. frame rate | Lens mount |
|---|---|---|---|---|
| P30M | 960 × 540 | Monochrome | 120 fps | Micro-video or C-mount |
| P30C | 960 × 540 | Colour | 30 fps | Micro-video or C-mount |
| P32M | 1920 × 1080 | Monochrome | 60 fps | Micro-video or C-mount |
| P32C | 1920 × 1080 | Colour | 30 fps | Micro-video or C-mount |
| P35M | 2560 × 1936 | Monochrome | 26 fps | C-mount |
| P35C | 2560 × 1936 | Colour | 13 fps | C-mount |
The P3X fits inspection positions where more detail is required within a compact setup, for example code inspection, label inspection, presence of multiple small features or inspection of larger fields of view. The 5 MP version divides the same field of view over more pixels, making smaller details visible. With moving products, this requires a short exposure time to reduce motion blur, which makes lens aperture, lighting and product distance more important.
Higher resolution in the P3X should be treated as additional measurement space. A 5 MP sensor provides extra information when the lens achieves the required resolution on the object across the full inspection field. The lens, working distance, aperture and depth of field determine whether the extra sensor pixels are truly usable. When the optics lose detail at the edge of the image field, the product moves outside the depth of field, or exposure time causes motion blur, the result is a larger image file without higher measurement certainty. In that situation, a 2 MP P3X with a suitable C-mount lens and stable lighting can be technically stronger than a 5 MP version where optics or light become the limiting factor.
Datalogic Impact PLC Communication: 24 V I/O and Industrial Networks
A Datalogic Impact system only becomes part of the machine when communication with the PLC is designed correctly. For simple applications, 24 V digital I/O is often the most direct connection. The PLC sends a trigger, the vision system returns busy, ready, OK or NOK, and the machine can respond immediately. This is clear, fast and easy to diagnose.
When the machine needs more information, industrial Ethernet communication becomes important. Measurement values, error codes, product variants, recipe numbers and multiple inspection results require structured data exchange. The MX-E series supports EtherNet/IP, Profinet, Modbus TCP and OPC. The P2X supports, via Gigabit Ethernet, protocols including TCP/IP, EtherNet/IP, Profinet IO, Modbus TCP and MC protocol. The P3X also supports EtherNet/IP, Profinet and Modbus TCP.
The communication choice belongs to the inspection cycle. Trigger, exposure, processing time and PLC handshake together determine inspection timing. For a simple reject, discrete I/O may be sufficient. For multiple measurement points, recipe management or central diagnostics, Profinet, EtherNet/IP or Modbus TCP is a better fit. By including this choice early in the system setup, image processing and machine control connect logically.
Datalogic Impact Training and Project Support via the Machine Vision Academy
Datalogic Impact makes it possible to build inspections with configurable tools. The practical value increases when engineers not only operate the software, but also understand why an image becomes measurable or unstable. Camera resolution, pixel size, lens magnification, working distance, depth of field, lighting angle, exposure, triggering and PLC communication together determine how reliably an Impact tool can measure.
Within the Machine Vision Academy, we train machine builders, integrators and end users hands-on in applying Datalogic Impact systems. We use the strength of the Datalogic platform: the same software environment is used on smart cameras and MX-E vision processors. An engineer therefore does not only learn to operate a specific camera, but learns to work with a platform that can grow from a compact inspection to a multi-camera system.
The training focuses on practical application. Engineers learn how Impact tools are placed and configured, how results are linked to PLC communication, and how image quality is influenced by camera, lens and lighting. When a threshold changes due to product reflection, when a measurement varies due to depth of field, or when motion blur occurs due to excessive exposure time, the relationship between software settings and hardware choices becomes clear. This makes the platform usable for engineering, commissioning, maintenance and future expansion.
For new products, variable surfaces, high speed or small tolerances, vision consultancy can help assess the inspection task beforehand. Product variation, movement direction, required object resolution, minimum defect size, available installation space, ambient light, PLC architecture and required reject handling are evaluated. Based on this, it can be determined whether a P2X, P3X or MX-E system is the best foundation.
From Datalogic Impact Component Choice to Complete System
A reliable Datalogic Impact system is created by designing the components as one system. For an MX-E system, this means processor, GigE cameras, lenses, lighting, cables, trigger/strobe, 24 V I/O and industrial communication. For a P2X or P3X, this means smart camera, lens choice, integrated or external lighting, filters, CBX connection box, I/O and PLC connection.
The technical route starts with the application. The smallest detail that must be detected reliably determines the required object resolution. Product speed determines the permitted exposure time. Working distance and field of view determine the lens choice. The surface determines the lighting geometry. The number of inspection positions determines whether a smart camera or a central MX-E processor is more logical. The PLC interface determines how results, statuses and recipe data are exchanged.
The value of the Datalogic Impact platform lies in the combination of scalability, recognisability and training. Engineers can use the same software foundation on different hardware architectures, while operators and maintenance technicians continue to work in one familiar environment. For machine builders, integrators and end users who want to work with vision themselves, this provides a clear route: start with a compact Impact smart camera system where it fits, scale up to MX-E when the machine requires it, and keep using the same software knowledge. Combined with hands-on training through the Machine Vision Academy and project support during application assessment, this creates an engineering approach that goes beyond component selection.