Gantner Logger
Purpose of this plugin is to read from Gantner loggers (See: https://www.gantner-instruments.com).
Usage
This plugin will read data from Gantner loggers, via he user web (http) port. There must be a config file when running log
. When running discover
, a config file is optional. The config file defines which variables need to be collected, what names they appear on the the Ardexa cloud, units and scaling. Example file as follows:
NOTES:
Anything that starts with
#
is a comment line, and will be ignoredThe
Type
can be either:decimal
,integer
,bool
,keyword
The
Gantner Variable Name
name MUST be as it appears in the logger, when doing adiscovery
Units
andScale
can be empty
You can do a discover
without a configuration file. In this case, all the variables are displayed. along with the current value. If you have a configuration file when running discover
, then the variables of interest are displayed, and everything else is ignored. ALWAYS run discover
first to see which variables are available, before developing the config file. Please take note of the first line returned from the logger, which should be something like: Data retrieved from Gantner logger via the CSV method: 192.168.2.101
. The methods to query the Gantner logger are either CSV method
or JSON method
. You will need to note this when logging data. See Arguments
below.
Arguments
IP Address = ..something like: 192.168.1.4
{Configuration File full path} groups the items of interest, and is required for logging data
Optional:
--extraction_method
is eithercsvmethod
orjsonmethod
. This means that data is derived from the logger either by downloading the CSV file or getting JSON data from a specific URL.
Last updated