How much data be recorded?

When the monitoring system is set into service it will store all of the measured data in its 1.5 Mb memory module. In most cases this capacity is satisfactory for many days worth of information. The amount of data that can be stored is determined by the number of input signals and how frequently each signal is recorded. Recordings can be made from 1 every second to 1 every 86,400 seconds (per input signal). At specific times as define by the user the stored data is emailed to specific email addresses. All the data for the specified period is tabulated into a single file and saved in .csv format which is easily opened by MS Excel and or imported into data bases such as SQL Server and the like. Whilst the unit will hold many days worth of data, typically data is sent to the monitoring base every 3 hours. (Note, this frequency is user defined) Regular transimission of stored data therefore allows for an unlimited amount of data to be recorded, and it also ensures that data is backed up.

How frequently can data be recorded?

Data from each input signal which has been selected to be recorded can be written to the data storage file every second to every 86,400 seconds (24hrs). This frequency is user selectable in 1 second increments.

How is the recorded information provided & in what format?

The logger collates the information defined by the user’s set of criteria and is written into a .csv file which is emailed directly from the data logger to the email address or addresses as predefined by the user. The data logger can store measurements in the engineering units defined by the user and or raw sensor values.

How frequently is the logged data sent?

The user can program the logger to send out data once every minute to once every 31 days, selectable is 1 minute increments. For example; the user can program the logger to send say 1 hours worth of data every hour if it’s necessary to know just what’s happened recently. If on the other hand he wants to be updated say every half hour and also wants to quickly see what’s been happening for the last 8 hours, the logger would be programmed to send him 8 hours worth of data every 30 minutes.

Can data be sent to a number of people?

Yes, very easily, and the data package sent does not necessarily need to be the same. The logger can be programmed to send different data (as well as different time ranges) to different people and also at different intervals.

Once the data is sent, is the data deleted from the logger?

No. Data is retained within the logger. The data that is sent is only a copy of the data corresponding to the period of time defined by the user.

Example: Logger connected to 10 instruments (flow rate, pressure, reservoir level) and having measurements recorded every 5 minutes. The logger’s 1.5 Mb of memory is sufficiently large to hold all of those measurements for 35 days and 10 hours. The logger is programmed to send the latest data every three hours. The latest data, as well as all of the preceding data is still retained within the logger and if the user wishes any other period of data, whether previously sent or not, it can be re-collated as required and sent again. E.g. - For process operation purposes it might be necessary to email a series of recorded measurements every hour to a control room operator, but for regulatory recording purposes another email could be sent to the QA department at HQ once every 24 hours. If any emailed data is lost, you'll still have the ability to retrieve any portion or all of the last 35 days worth of data from the logger.

Does all the connected input signals need to be recorded?

No. The configuration software allows you to select which inputs are recorded. You may decide that some inputs need not be recorded, but simply used for control purposes. When connecting a PLC to the logger you have total control of what signals are passed to the logger.

How secure is it?

Access to the logger and its configurations is protected by encrypted password security.

What are its control capabilities?

The logger is also capable of receiving SMS messages and converting those messages into control instructions that are output via the output devices connected to the logger.

Example – A farm manager monitors the soil moisture levels, dam water levels and weather conditions on contract farms which are remote from his primary operations. His collected data shows that his dams have enough water, the soil is dry, no rain is likely and that the crops hasn’t been watered in two days. The farm manager can then send an SMS to the remote logger to say turn on Pump 1, Pump 4 & Pump 7. When the logger receives the SMS and has turned on the pumps it will send back a confirmation SMS, and since the logger was programmed to also SMS the water flow rate values from the flow meters attached to each pump line, the manager will be able to see that pumps are delivering as expected. The logger also has alarm scenarios stored that will send the manger an SMS if any of the water flow rates fall below their set-point values. The manager can turn off any or all of the pumps, again just by sending an SMS. Alternatively the pumps can be automatically turned off when any pre-programmed condition is met, such as when a certain amount of water has been pumped. When the pump turns off, again a notification SMS is sent to the manager.

How many remote systems can monitored?

As many as you like, which means collected data from all your sites can be quickly delivered and processed at a single, central location without having to pass through the hands of numerous people and or systems.

Every input signal can have an alarm trigger value or formula assigned to it. When an input signal’s value matches the trigger value or condition defined by an assigned formula an alarm output is initiated. A user adjustable stability timer is included for each alarm scenario to cater for spurious spike conditions that may occur.

How are alarm conditions reported?

The logger sends an SMS message an or email when an alarm condition is fully met. When defining the alarm condition the user will also define;

• To whom the message will be sent.

• An ID tag to identify to the recipient where the message is coming from.

• The warning statement that needs to be conveyed to the recipient.

• What measurement information should be included in the message.

• How many times the message should be resent.

• Any alternative back-up recipients.

The logger can also send different alarm messages to different people and the basis for sending messages is all fully customisable by the user.

The user lso defines whether messages are sent as an SMS or email or both.