There are 2 independent ways to use this protocol, using a TagProvider or as a DeviceChannel in the Module Device.
This document has only the specific information about the device connection settings and its address syntax.
Refer to the User Guide for more information on the Device Module or on UNS TagProvider Connections.
On this page:
Communication Driver Information | |
---|---|
Driver name | InfluxDB |
Assembly Name | T.ProtocolDriver.InfluxDB |
Assembly Version | 1.0.0.0 |
Multiplatform | False |
Supported versions | InfluxDB 2.x |
Manufacturer | InfluxData |
Supported protocols | Proprietary for custom, non-standardized communication and REST API for HTTP-based standardized interaction. |
PC Requirements | Ethernet port |
There is no configuration settings necessary for this interface.
The station parameters are:
Always use the Test button to verify the connection status. |
The address parameters are:
If Point is from TagProvider and CheckBox is true, a Column called TagProviderPath will be created with the path leading to the TagProvider asset.
Syntax: <ColumName> = <ColumnValue>
You can add, remove or edit custom columns in the dialog window at ’+’ button.
To illustrate the result of a sucessfull configuration we will make the following assumptions.
Panel1 [Tag of Template 'Panel']
Motor1 [Tag of Template 'Motor']
AMP [Final Attribute of 'Double' Type]
RPM [Final Attribute of 'Double' Type]
Motor2 [Tag of Template 'Motor']
AMP [Final Attribute of 'Double' Type]
RPM [Final Attribute of 'Double' Type]
The Address is configured as:
This configuration will result in the following Table inside InfluxDB:
To Read back these values, all you have to do is use another Tag, of same "Panel" Template and use the same Custom Column Configuration.
When Tag Attribute is Array, a new column called ArrayIndex will be created and populated with the indexes. An example is illustrated below:
The status of the driver execution can be observed through the platform built-in diagnostic tools. Refer to Devices - Using Diagnostic Tools.
In this section: