Manual
LCom
Page 77 of 158
Note: the bigger the value for the reporting interval is, and the more Sensor
OIDs are configured for the data store, the longer it takes for the rpu to read
and calculate the aggregated data for each OID (which is calculated
depending on the statistics Type settings for the respective OID in the
historySensors table). Calculating the data might take up to several minutes!
The maximum number of entries in the resultsTable is 255
– so if more than
255 rows are to be expected, the status reported above will be
“dataPartialReady”.
f) Read the number of valid rows in the results table through reading the
dataStore.numRowsInResult.0
OID
Note: if the query was successful (no error occurred), but there are no values
available in the given interval, the number of rows in the result will be reported
as 0.
g) Read the resultsTable
–
dataStore.queryResultsTable.queryResultsEntry.rowMeasureT
ime.x
will provide the UTC timestamp of the measure values reported by the
corresponding
dataStore.queryResultsTable.queryResultsEntry.rowValues.x
OID.
h) Read
the “dataStore.resultEndTime.0” parameter. This reports the end of the
interval analyzed for the current result set. If the data provided does not cover
all the time period needed (the
dataStore.queryCommandAndStatus.0
value will be dataPartialReady (4) if more data is available in the
data store), re-calculate a new startTime timestamp and repeat
from step c) !
i) After all values have been retrieved, clear the result set (and query
parameters) by writing a value of 7 (done) to the
dataStore.queryCommandAndStatus.0
OID.
