Data interfaces

USB

The Airleader has an USB interface, among other things, for data export. This can be used to save data archives on a USB stick, even if the visualization is not available. These data are used for offline visualization of the station on any computer, e.g. to analyze the running behavior or to carry out simulations with the measurement and simulation software. Firmware updates and add-ons are also installed via this interface.

MS Office

The compressor data and energy calculation table can be exported from the application to Excel / Word with a click of the mouse, so that they are immediately available for documentation.

CSV

The daily data contain all recordings and evaluations of the Airleader at 10-second intervals and are archived in a compressed file per day. A daily file can be generated using the CSV export button and can be processed further via Excel.

Modbus server

The Modbus server uses an open protocol to make all relevant data of the compressed air station available in a standardized protocol description via a software interface.

Modbus data integration

Data from external sensors such as kW measurement, flow sensors, pressure dew point sensors etc. are processed directly and evaluated and visualized in the visualization. Connection

  • via RS485 to the control unit or
  • TCP / IP address via the Ethernet.

 

OPC DA

The external OPC server makes the process data of the Airleader available to the second as OPC objects. The OPC client accesses the data provided by the OPC server and displays it graphically in the control station (BMS). Today, OPC is the standard for manufacturer-independent communication in automation technology. Without OPC, two devices required precise knowledge of the communication options of the other to exchange data. With OPC, it is sufficient to write an OPC-compliant driver exactly once for each device. The Airleader OPC driver can be integrated into control and monitoring systems of any size, such as B. Sauter NovaPro, WinCC, Kieback & Peter, Wonderware, Web Factory, ACRON (BDA from Videc) etc. or energy management system software such as B. Integrate MESSDAS, FRAKO, ECON Solutions.

OPC UA

The internal OPC server makes the process data available as OPC objects, regardless of Windows. The OPC client accesses the data provided by the OPC server and displays it graphically in the control station (BMS). Today, OPC is the standard for manufacturer-independent communication in automation technology. Without OPC, two devices required precise knowledge of the communication options of the other to exchange data. With OPC, it is sufficient to write an OPC-compliant driver exactly once for each device. The Airleader OPC driver can be integrated into control and monitoring systems of any size, such as B. Sauter NovaPro, WinCC, Kieback & Peter, Wonderware, Web Factory, ACRON (BDA from Videc) etc. or energy management system software such as B. MESSDAS, FRAKO, ECON Solutions.

OPC stands for Open Platform Communications and is one of the most important communication protocols for Industry 4.0 and the IoT (Internet of Things). With OPC, access to machines, devices and other systems in the industrial environment is standardized and enables the same type of and manufacturer-independent data exchange.

UA in OPC UA stands for “Unified Architecture” and denotes the latest specification of the standard. The difference to the predecessor lies in the platform independence due to the move away from COM / DCOM to purely binary TCP / IP or alternatively SOAP communication. In addition to many other improvements, OPC UA also supports a semantic description of data. During the development of the OPC UA standard, attention was paid to the highest level of security from the start. In contrast to OPC Classic, OPC UA was developed “firewall-fiendly”, which means that it can be controlled and directed using standard network technologies. Several protocols are available on the transport layer. A binary protocol can be used directly on TCP / IP for fast applications or the cross-platform SOAP with HTTPS. 128 or 256 bit encryption is used to secure the data during transmission, as well as message signing and packet sequencing and user authentication. For further security, a certificate exchange is used with OPC UA, so that every client has to authenticate itself with a certificate. In this way it can be controlled which client is allowed to connect to the server.

 

SOAP

JASON/P

AJAX

Plain XML

XML