27
GATEWAY SPECIFICATION - WebdynPulse
WebdynPulse – Gateway specification - Version 2.0
Example:
•
Configuration:
Connection_OnDataAcquisition=1
Connection_WaitBeforeCloseDelay=5
Connection_Period=0
Connection_Hour=23
Connection_Minute=0
And the data acquisition period is defined as 2 minutes:
DAQ_Period=2
•
Connection times:
Connection kept open with data being uploaded every 2 minutes
Time synchronization and configuration checking occurs at 23:00 every day.
6.4.6 Optimizing the connection
To avoid excessive GPRS consumption, it is possible to enable an optimization option for FTP
communications. This is specified through the variable
Connection_CheckConfigPeriod
in the
configuration file
prefixID
_var.ini.
When this optimization is enabled, the gateway can be programmed not to analyses the
configuration and definition directories on every connection.
Where the variable
Connection_Period
is zero, the time for the analysis is defined by the variable
Connection_Hour
. If it is not, the gateway will launch the analysis during the first connection of the
day.
6.5 Acquisition period and time slots
The role of the WebdynPulse is to collect data from different sources (inverters, meters, sensors,
etc.), and then to write them periodically to CSV files for provision via a remote FTP server.
Data collection is scheduled using the variables DAQ_Period and DAQ_PeriodSec in the configuration
file
prefixID
_daq.ini.
Variable
Definition
Default value
Connection_CheckConfigPeriod
0: Disabled
n: Number of days between 2 analyses.
Note:
When the gateway processes a
command file, it goes on to analyses the
configuration and definition directories
regardless of whether optimization has
been enabled.
0
