USER MANUAL :
DOCUMENT NAME
Cloudworks loggers support the use of simcard pin codes. How this works is
will request the pincode when the modem powers up and starts connectin
populated, the logger will offer this code to the network, allowing it to connect. Failure of the pincode will cause the
logger to abort the connection attempt and shutdown.
If you are using a foreign simcard on a network, the logger will need to be told that it is allowed to use data roaming.
Without that, the logger will shutdown.
For the datalogger setup, 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.
MANUAL : CDS543 NIMBUS PULSE LOGGER
NAME
CLASSIFICATION
DATE
PAGE
Cloudworks loggers support the use of simcard pin codes. How this works is - should a simcard have a pincode activated, it
will request the pincode when the modem powers up and starts connecting to the network. If the pincode field here is
populated, the logger will offer this code to the network, allowing it to connect. Failure of the pincode will cause the
logger to abort the connection attempt and shutdown.
d on a network, the logger will need to be told that it is allowed to use data roaming.
For the datalogger setup, the Wakeup Period refers to the time a logger remains asleep before waking and connecting to
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
ance, 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 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
PAGE
should a simcard have a pincode activated, it
g to the network. If the pincode field here is
populated, the logger will offer this code to the network, allowing it to connect. Failure of the pincode will cause the
d on a network, the logger will need to be told that it is allowed to use data roaming.
For the datalogger setup, the Wakeup Period refers to the time a logger remains asleep before waking and connecting to
Datalog timings are calculated forward from midnight of the day on which they are set. What this means is that if the
ance, the next log time will be calculated as 5 minute intervals starting from
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
