Easy data transfer to InfluxDB
The Influx database is a powerful BigData / NoSQL database for time series data from InfluxData. Due to new non-relational database concepts, InfluxDB is able to store large amounts of time related data very quickly and efficiently and to load and make them available again.
With its plug-ins, the OPC Router has connections to various industrial infrastructure systems and thus has access to their data. With the InfluxDB plug-in it is possible now to transfer this data directly to the Influx database and make it available to BigData and analysis applications. Data sources are connected to InfluxDB as usual in a graphical configuration of Drag&Drop.
Achieve more with combined Systems
With InfluxDB Plug-in you provide your BigData application with even more data from your production environment. The analyses have even more possibilities to view the entire context.
Industry 4.0 and InfluxDB
The idea of Industry 4.0 drives networking in industry forward. More and more components and systems can be connected and queried. For InfluxDB, the OPC router as the central industry 4.0 data hub forms the bridge to data of these devices and systems.
About OPC Router
OPC Router helps you to connect your systems as data hub. Numerous plug-ins are available, which make OPC Router the ideal middleware in industrial settings.
That’s how easy it is.
The transfer object of the Influx plug-in enables transfer of data to an Influx database.
Each transfer object is assigned to an InfluxDB connection, depending on the database to be written to.
InfluxDB Measurement, Tag and Fields
During data transfer, the measurement can be transferred from the data source or set statically. The measurements build the data pool in InfluxDB, comparable to a table in classic SQL.
The tag can also be determined statically or dynamically. Tags are used to group data in the InfluxDB to create a context for later queries.
The fields to be transferred are configured in the transfer object. In the connection, these are graphically connected with data points from the source. Fields are the individual fields of a data record. Compared to the classic SQL, the fields can be seen as columns of the tables.
The Influx Plug-in does not have its own trigger. The data transfer into the database can be triggered by different basic triggers or triggers from other plug-ins.
Browsing is supported by the InfluxDB Plug-in in several places.
When configuring the database connection, the databases of an InfluxDB server can be browsed.
To set up the connection configuration, the available measurements, tags and fields can be loaded from the database in the transfer objects.
InfluxDB Plug-in Application Examples
Process value data acquisition
Due to its networking in production environment, OPC Router has access to valuable production data. This data is very well suited to be transferred as time series data to Influx BigData database system. This opens up new analysis possibilities for the production data, but data already in the database can also be viewed in new contexts. The various plug-ins allow you loading data from various systems and transfering to InfluxDB. A typical example of data collection for process data acquisition is control and sensor data from PLC systems. Controllers are connected via standardized OPC UA protocols (with the OPC UA Client Plug-in).
MQTT to InfluxDB transfer
More and more systems in industry are able to send their data via MQTT. Especially the constantly growing IoT (Internet of Things) is strongly based on this simple and light protocol. With its MQTT Client Plug-in, OPC Router can receive messages from an MQTT Broker and thus obtain data from any source as MQTT Subscriber. In combination with InfluxDB plug-in, data can then be transferred to InfluxDB directly or after a previous transformation. It is possible to use the OPC Router as an MQTT to InfluxDB Gateway with graphical configuration.
How do Transfer Objects, Trigger and Browsing work?
The OPC Router establishes connections between systems that address core functions of the OPC Router.
Functions of the respective plug-ins may vary, due to the different nature of each connected system.
Sources and Destinations
Transfer objects are the sources and destinations inside the OPC Router. They contain data fields with read and write functions. Depending on the respective interconnected system, the possible configuration scope of sources and destinations may vary.
Homegenity on the Outside – Heterogeinity on the Inside
Inside the OPC Router configutation, the Transfer Object abstracts the respective system context of any connected system into a simple data input and data output block. Thus, the functions can be treated in the same way although each connected system has very individual features.
Triggers determine execution time of data transfers. Various Triggers can be active, independent of source or destination. Various Triggers can be used in combination via AND/OR-connections. Triggers can also serve as data sources if the prompting event is coupled with receiving data.
Searching and Finding Data Fields
The configuration of sources and destintions is simplified. Differing browsing mechanisms are available, depending on the type of system and/or plug-in.
Reading out Structures
Even complex structures can be selected without requiring detailed knowledge about subsystems. The plug-ins presents structures of data sources according to the specification of the respected plug-in.