It is not required to integrate our web platform into the company firewall.
The sensors and gateways connects to the Controlant cloud via cellular network and has no connection to the company IT structure
When configuring the system or looking at the data through browser, you just go to Controlant web and log in to the relevant user interface. The interface works in the same way as other web services that one use.
Installation is simple. The devices, loggers and gateways, is delivered configured and seen in the user interface for the relevant company. One user for administrator has been open when delivered. Further information about installation and configuration can be found in the Installation section
...
| Include Page | ||||
|---|---|---|---|---|
|
Q: Logger does not connect to Gateway. Why?
A: We recommend you go through this checklist:
Is the antenna on the logger?
Is the antenna orientation optimal? See 1.3.6 Troubleshooting for guidelines.
Is anything obstructing the signal path between loggers and Gateway?
Is there GPRS connection in the facility?
Do other loggers get connection?
Do cell phones work?
Q: What is the difference between:
03.01 logger
03.02 logger
Logger 03.01 is an internal temperature logger.
Logger 03.02 is an internal temperature and humidity logger.
Q: Logger does not deliver data but appears to have good communication with Gateway.
A: Logger may appear to have good contact with Gateway but when looking at historical data points nothing appears. This could indicate that the communication between logger and Gateway is marginal. Under marginal signal conditions the loggers is able to see the Gateway but unable to lock on and deliver its data. Try to improve communication link between logger and Gateway (see recommendations in 1.3.1 General Wireless Setup). If problem persists please contact support@controlant.com.
Q: When there is an alert, does the logger send an update to the cloud immediately and send the email alert to the customer or does it wait till the hourly upload?
A: Please refer to: 1.4.5 Set Temperature Warnings.
Q: Why there is a difference in receiving data when it comes to temperature and humidity?
A: When there is bad signal quality the temperature signal has priority over the humidity signal.
Q: For how long does a temperature logger store data?
A: For up to 27 days.
Q: For how long does a temperature/humidity logger store data?
A: For up to 14 days.
Q: How long is battery life in loggers?
A: Environment conditions affect the battery life but they should last for 3 to 4 years depending on the device. See 1.2 Specifications for details. If the voltage drops below 3.4 the battery needs replacement. Under this value, the battery drains faster and stops recording temperature and sending an alert.
Q: How often do the loggers have to be calibrated?
A: This depends on the application. Some customers require yearly calibration.
Q: What is the minimum signal strength between "CO11 Gateways" and "CO13 Loggers"?
A: To securely get data up to the cloud 30% is needed, however, the aim should be to have at least 50% to leave room for variations.
Q: Can I assign a logger to a specific gateway?
A: The loggers connect to the gateway which is easiest for them to connect to, usually the one which is closest. It is not possible to assign a logger to a gateway. If a user wants to make a change and the logger keeps on logging to the "wrong" gateway it has to be removed from the room/space.
Q: How do the loggers handle water?
A: The loggers are somewhat water-resistant but cannot be submerged in water.