USER MANUAL :
DOCUMENT NAME
The Wakeup Period refers to the time a logger remains asleep before waking and connecting to the server to upload its
data. The Datalog Period is the time between each recorded datalog entry.
Datalog timings are calculated forward from midnight of the day on which they are set. What this means is that if the
datalog period is set to 5 minutes for instance, the next log time will be calculated as 5 minute intervals starting from
midnight. This means that each entry would appear on the 5 minute interval of an hour.
Wakeup timings are calculated forward from the moment a
Stored locally on each logger is a 220 byte 'User Configuration Data' scratchpad area. This information is eventually carrie
back into the database and can be used for numerous functions. An example would be the storage of meter serial numbers
on a water metering application etc. This area could also contain a complex code that would perhaps give the backend
software more information as to how the data from this logger needs to be handled. For example, it could contain a code
which has the meter serial number plus other digits indicating whether it is a bulk or zonal meter.
Also, if there are multiple meters attached it could contain multiple serial numbers separated by a comma for instance. Any
data that is useful could be stored here.
The 'Engineering' box contains parameters involved with the setup of onboard functions of the logger. The are several
communications monitoring parameters that are set to ensure that the communications to the logger are functional and
stable.
Battery operated loggers will wake up, connect to the server and upload their data. Should this fail, it would be a large
drain on the battery of the logger to continually try and connect. For this reason, the logger has a single chance to wake up
and establish a connection. If that fails, it will return to sleep and a only reconnect at the next wakeup period. At the start
MANUAL : CDS546 NIMBUS LOOP LOGGER
NAME
CLASSIFICATION
DATE
PAGE
The Wakeup Period refers to the time a logger remains asleep before waking and connecting to the server to upload its
data. The Datalog Period is the time between each recorded datalog entry.
gs are calculated forward from midnight of the day on which they are set. What this means is that if the
datalog period is set to 5 minutes for instance, the next log time will be calculated as 5 minute intervals starting from
h entry would appear on the 5 minute interval of an hour.
Wakeup timings are calculated forward from the moment a logger goes back to sleep and not from the midnight point.
Stored locally on each logger is a 220 byte 'User Configuration Data' scratchpad area. This information is eventually carrie
back into the database and can be used for numerous functions. An example would be the storage of meter serial numbers
metering application etc. This area could also contain a complex code that would perhaps give the backend
software more information as to how the data from this logger needs to be handled. For example, it could contain a code
mber plus other digits indicating whether it is a bulk or zonal meter.
Also, if there are multiple meters attached it could contain multiple serial numbers separated by a comma for instance. Any
' box contains parameters involved with the setup of onboard functions of the logger. The are several
communications monitoring parameters that are set to ensure that the communications to the logger are functional and
wake up, connect to the server and upload their data. Should this fail, it would be a large
drain on the battery of the logger to continually try and connect. For this reason, the logger has a single chance to wake up
ails, it will return to sleep and a only reconnect at the next wakeup period. At the start
PAGE
The Wakeup Period refers to the time a logger remains asleep before waking and connecting to the server to upload its
gs are calculated forward from midnight of the day on which they are set. What this means is that if the
datalog period is set to 5 minutes for instance, the next log time will be calculated as 5 minute intervals starting from
goes back to sleep and not from the midnight point.
Stored locally on each logger is a 220 byte 'User Configuration Data' scratchpad area. This information is eventually carried
back into the database and can be used for numerous functions. An example would be the storage of meter serial numbers
metering application etc. This area could also contain a complex code that would perhaps give the backend
software more information as to how the data from this logger needs to be handled. For example, it could contain a code
Also, if there are multiple meters attached it could contain multiple serial numbers separated by a comma for instance. Any
' box contains parameters involved with the setup of onboard functions of the logger. The are several
communications monitoring parameters that are set to ensure that the communications to the logger are functional and
wake up, connect to the server and upload their data. Should this fail, it would be a large
drain on the battery of the logger to continually try and connect. For this reason, the logger has a single chance to wake up
ails, it will return to sleep and a only reconnect at the next wakeup period. At the start
