text.skipToContent text.skipToNavigation

Integration in Third-Party Software

Machine vision sensors generate large amounts of data with each measurement, such as image data, height profiles, intensity values or 3D point clouds. The easy integration of machine vision sensors into image processing software is made possible by standard interfaces such as GenICam and powerful software development kits.

What Are Interfaces?

An interface is the clearly defined connection between two systems. It defines how data is transferred, in which format it is available and via which communication channel it is exchanged. A smooth data exchange is only possible if both sides comply with these rules.

Ein reibungsloser Datenaustausch wird über die passende Schnittstelle sichergestellt.

Image acquisition (machine vision sensor)

Data stream

Parameter access

Image accessing (machine vision software)

Data transmission (interface)

Image Acquisition

Capture large amounts of data per measurement
Generation of 2D height profiles or 3D point clouds and intensity values

Data Transmission

Fast and as delay-free data transfer as possible
Provision of data in standardized formats
Secure and stable communication between sensor and system

Image Accessing

Direct further processing of the data by the image processing software
Analysis and interpretation of the recorded measurement data
Output clear and actionable results for the application

Why Are Interfaces So Important?

Choosing the right interface is a key factor in how quickly a sensor can be commissioned, how efficiently data is transferred and how future-proof a plant is. Depending on the camera or sensor, the type and scope of the data generated differs.

2D Camera

A 2D camera captures the surface of an object as a high-resolution image. This image data is then evaluated for presence and position checks, identification tasks or quality controls.

2D/3D Profile Sensor

A 2D/3D profile sensor projects laser light onto the surface of an object. The reflected light is captured and evaluated by a camera, creating precise 2D profiles or detailed 3D elevation images or point clouds for measurement and inspection tasks.

3D Sensor

A 3D sensor projects a defined stripe pattern onto the surface of an object. A camera records the deformation of this pattern and evaluates it. This creates high-resolution 3D point clouds for precise measurement and inspection tasks.

Benefits of a Powerful Interface

Separate data and control channel

High transfer speeds

Stable and reliable communication

Supported data formats

Easy integration into existing systems

Who Benefits from High-Performance Interfaces?

Machine Builders and Integrators

Less development effort
Quicker initial start-up
Sensors from different manufacturers can be operated in the same software environment

End Customers

Manufacturer-independent
Easy replacement in case of defects or system upgrades
Full compatibility with existing systems

Evaluate Image Data Directly in uniVision

Interfaces enable the integration of sensors into third-party software or in-house applications as well as the reliable transfer of the captured image and profile data to software for direct further processing.

With the uniVision image processing software, wenglor offers a solution for easy parameterization of machine vision cameras and sensors, visualization and analysis of measurement and image data, and use for inspection, measurement and automation tasks.

Interface Levels

An interface always consists of two levels: the physical level and the logical level. For example, two devices may have the same plug and not be able to communicate if they use different protocols.

Physical Level – the Hardware Connection

The physical level provides the hardware connection and describes how data is transferred between the sensor and the system. This includes the transmission medium and plug connectors.

Logical Level – the Protocol

The logical level determines how the devices communicate with each other, while the protocol defines how data is constructed, transmitted and interpreted.

Comparison of Standard and Proprietary Interfaces

Standard Interfaces

Open interfaces are standardized and continuously developed by independent organizations.

Components from different vendors can be used in the same software environment.

Open standards simplify integration into existing systems and allow easy hardware replacement.

The use is not bound to a specific manufacturer.

Proprietary Interfaces

The interface is specially tailored to the products and system architecture of a manufacturer.

Thanks to the close meshing, device-specific functions can be used particularly efficiently.

Hardware, software and support come from a single source and are optimally coordinated.

Proprietary interfaces often offer advantages when maximum performance or special device requirements are in focus.

To ensure maximum flexibility in a wide range of application environments, wenglor offers both standardized and proprietary interfaces. Depending on requirements, users can choose between open integration and performance-optimized system solutions.

Overview of Typical Standard Interfaces

GenICam – the Standard Interface for wenglor Machine Vision Products

Generic Interface for Cameras (GenICam) is an open standard of the European Machine Vision Association (EMVA) that standardizes communication between sensors and image processing software. This allows GenICam-compatible devices from different manufacturers to be integrated and controlled via the same software.

How GenICam Works

Each GenICam-compatible sensor provides a standardized XML description. It defines all available functions and parameters, such as exposure time, trigger or image resolution.

When connecting, a GenICam-enabled software automatically reads out this information. This allows it to recognize which functions the sensor supports and how these are addressed. The sensor and software can then communicate with each other regardless of the manufacturer.

The GenICam Architecture at a Glance

Producer

The producer is provided by the device manufacturer and acts as a driver between the sensor and the application software. It takes over the connection of the hardware, provides the image data and GenICam-compliant interfaces.

Consumer

The consumer is the application software that accesses the producer via this interface. It reads the standardized device description and controls the sensor without having to know manufacturer-specific details.

The interplay between producer and consumer ensures a clear separation between hardware and software and enables the easy integration of GenICam-compatible sensors from different manufacturers.

The Three Parts Standards

GenApi – Device description

Describes all available device functions and parameters in a standardized XML file.

GenTL – Data transmission

Defines the interface for data exchange between producer (sensor/driver) and consumer (software).

SFNC – Uniform designation

SFNC (Standard Features Naming Convention) ensures that identical features have the same names for all manufacturers.

Advantages of the GenICam Interface

Manufacturer independent

Software that was developed for a GenICam-compatible sensor can also be used with other GenICam sensors from different manufacturers.

Fast integration

Standardized interfaces reduce development and commissioning times.

Reusable software

Already developed applications can often continue to be used in the event of hardware changes.

Hardware can be expanded or replaced without making any major software changes.

Validation According to EMVA Standards

Adherence to the GenICam specification is the basis for reliable communication between the sensor and software. The validation tools provided by EMVA can be used to check whether an implementation meets the requirements of the standard.

What Is EMVA?

The European Machine Vision Association (EMVA) is the leading European industry association for image processing and machine vision. It develops and maintains international industry standards such as GenICam, GigE Vision and USB3 Vision, thus contributing to manufacturer-to-manufacturer compatibility in machine vision.

As a member of the GenICam Working Group, wenglor actively participates in the further development of the standard and ensures that machine vision products comply with the current specifications. Implementation is verified by extensive internal tests and additionally validated by independent third-party providers and manufacturers of image processing software. In this way, wenglor ensures that the interface not only meets the specifications, but also functions reliably in real applications.

What Are the Benefits for Users?

High integration security
Easy integration into existing image processing systems
Future-proof solution with long-term stability
Orientation to current market and international standardization requirements

Software Development Kit

A Software Development Kit (SDK) is a software package that contains all necessary components for communication and seamless integration of a sensor into its own applications. These include program libraries, application programming interfaces, documentation as well as code examples and demo applications. In addition, it contains all the necessary tools for efficient connection and use of the sensor. This enables maximum performance and tight system integration.

Manufacturer-Specific SDK

A manufacturer-specific SDK provides access to the sensor’s proprietary application programming interface (API). Sensors can be connected, controlled and read out via the API.

The software contained in the SDK performs central tasks in the background:

Establishing and managing the connection to the sensor
Transferring measurement data
Preparation and provision of data for the application

This allows developers to directly access relevant information such as profile data, intensity values or full 2.5D depth images without having to implement data communication.

What Is Included in the SDK?

Program library

The program library forms the central component of the SDK. It contains all functions for communication with the sensor and can be integrated directly into your own programs. Depending on the operating system, it is available under Windows as a DLL (Dynamic Link Library) or under Linux as a shared object.

Header files and API description

Header files and the API descriptions define all available functions and their use. They also facilitate integration with programming languages such as C or C++.

Code examples and demo applications

Pre-prepared example projects show typical use cases in practice, such as establishing a connection or reading out measurement data. They serve as a template and enable a quick introduction without extensive training.

Documentation

The documentation describes all functions, parameters and procedures of the SDK and supports developers in the implementation and subsequent expansion.

Supported operating systems

The SDK is available for Windows and Linux (x86) and can be used flexibly on common industrial and development platforms.

Benefits of the SDK

Fast integration

With the help of pre-built functions and sample code, an application can be set up in a short time.

High flexibility

The SDK can be used to perform a wide range of tasks – from reading out individual measured values to complex real-time applications.

Reliable communication

The network-based connection via established standards ensures stable and robust data transmission.

Integration support

If you have any questions or challenges, our support team is available to help you quickly and competently with integration and implementation.

FAQs

What Differentiates Standard Interfaces from Proprietary Interfaces?

Standard interfaces such as GenICam are based on open, manufacturer-independent standards. This allows compatible devices to be integrated into corresponding software environments regardless of the manufacturer. Proprietary interfaces, on the other hand, are based on manufacturer-specific SDKs and enable integration tailored to the respective devices.

How Does GenICam Facilitate the Integration of Different Sensors?

The sensor describes itself via a standardized XML file, which is automatically read out by the software. As a result, no device-specific code is required and the integration of different sensors takes place according to a uniform scheme.

Which Components Are Included in an SDK?

A Software Development Kit (SDK) contains the necessary tools for integrating and programming a device. This includes drivers, application programming interfaces (APIs), sample code, documentation and a viewer for parameterization.

Product Comparison

3/4

4/4

5/4

6/4