| Page properties | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
InfluxDB databases
| Table of Contents | ||
|---|---|---|
|
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 Services (Reference).
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Overview
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.
NodesThestationparametersare:
| Note |
|---|
| Alwaysuse theTestbuttontoverifytheconnectionstatus. |
Theaddressparametersare:
IfPointisfromTagProviderandCheckBoxistrue,aColumncalledTagProviderPathwillbecreated with the path leading to the TagProvider asset.
Syntax: <ColumName>= <ColumnValue>
Youcanadd,removeoreditcustomcolumnsinthedialogwindowat’+’button.
Toillustratetheresultofasucessfullconfigurationwewillmakethefollowingassumptions.
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]
TheAddressisconfigured as:
Thisconfiguration willresult inthe followingTable insideInfluxDB:
ToReadbackthesevalues,allyouhavetodoisuseanotherTag,ofsame "Panel" Templateanduse the same Custom Column Configuration.
WhenTagAttributeisArray,anewcolumncalledArrayIndexwillbecreatedandpopulated 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.
| Page Tree | ||||
|---|---|---|---|---|
|