| Include Page | ||||
|---|---|---|---|---|
|
Q: If I receive an alert for missing data, will the system still send out alerts if there is a temperature excursion as long there is a connection between logger and Gateway?
A: Yes.
Q: If the system is logging every 10 minutes, can I verify shorter excursions in the Web Interface?
A: The logger is measuring every minute but logging every 10 minutes to memory. Since the logging takes place every 10 min, excursions shorter than that will not be visible in Web Interface but alarms will be sent and the excursion will be in report.
Q: How are Temperature Warnings set?
A: See:1.4.5 Set Temperature Warnings
Q: How many recipents can receive alarms?
A: There can be 3 sms recpipents and 4 email recipents.
Q: Is it possible for persons to receive alerts at different hours?
...
A: There are no extra charges.
Q: Why is there data missing for a logger in my report?
...
Bad RF signal between a logger and a Gateway can be confirmed by looking at the logger connectivity in the device view.
If the RF signal is less then 50% for a logger, then the logger might be sending data irregularly.
Q. In some cases I don’t get Data Alarm (Data Warning – Lost connection to a logger) sent even though no measurement data is logged in the database and no measurements can be seen in the Controlant cloud multigraph or reports. Why?
Q. In some cases I can see temperature measurements from a logger and the logger is connected to the gateway but no data can be seen in the multigraph or report. Why?
A: Both of these questions can have the same root cause and is not related to any defect in the system. The reason is related current behaviour of the system or to so called 01 and 03 data package.
What is 01 and 03 Data packages?
01 data package A data packed that is sent from a logger and includes connection information to the gateway and temperature data. 01 data temperature information is NOT stored in the data base and NOT used to generate graph or report
03 data package A data package that is sent from a logger when it has been verified with 01 data package that the logger is in good connection with a gateway. The 03 data package includes measured temperature data that is stored in the data base.
Problem occurs in bad connection
When a logger is in a bad connection to a gateway (less than 50% signal strength) the gateway can receive the 01 data packages and show the measured temperature in the User interface. But the connection is not good enough for the logger to receive confirmation from the gateway so the logger doesn’t send the 03 data package to the gateway. There is a “signal strength” icon in the logger information bar that indicates the signal strength
In cases like this, the user can see, in the User Interface, that the Logger in connection to the gateway (1), receives temperature measurement (2) and shows signal strength (3) even though the signal strength is very low.
...
This is misleading information to the User, that can conclude that everything is fine. In reality, when a logger is in a bad connection to the gateway, the logger can’t deliver 03 data package with measurement data that will be logged in the data base and the connection is good enough for the gateway to think that the connection is good enough so no Data Warning is sent.
To avoid situation like this, it is important to make sure that every logger has a good connection to the gateway and the logger signal strength icon show more than 50% signal strength. Controlant is aware off this behaviour can be confusing for the User. This function will be improved and estimated timeline is before end of Q1, 2017