Hardware and software complex for monitoring the air conditioning systems

The complex is designed for remote monitoring and control of Daikin air conditioners.

Hardware developer: CJSC "Visat-service".

Software developer: LLC "Nevlabs".

Complex architecture

Key elements are shown in the figure:

Software complex architecture

"SRK-M" devices monitor air conditioners and the environment. Data accumulated by the devices is collected by a server app and stored in a database. The client application connects to the server and enables to view all the accumulated information and configure the system.

SRK-M and air-conditioners are connected through special-purpose adapters. SRK-M is connected to the server through TCP protocol (allowing to work both in the local network and via the Internet) or through COM port. In both cases, the Modbus command system is used. The client application is connected with the server through HTTP protocol.

Server application is designed as Windows Service. The client application is designed as a standard window app from Windows. Any version of Microsoft SQL Server including free SQL Express can be used as a database.

"SRK-M" devices

Physical interface with air conditioners is equipped with "SRK-M" device. Its basic functions include:

  • Switching air conditioners on /off (up to 3 pcs. per device);
  • Monitoring of air conditioners state (on, off, alarm signal, etc.);
  • "Rotational" operation of air conditioners for even wear (alternate operation of 2 air conditioners out of 3);
  • Environment monitoring: room temperature, supply voltage 220 V, external alarm signals, etc .;
  • Storage of monitoring data in internal memory.

The device looks like this:

Appearance of SRK-M device
Appearance of SRK-M device

Server app

Server app connects with SRK-M devices with specified frequency and requests the following data:

  • Current state of air conditioners (on, off, presence of alarm signal, etc.);
  • Current state of environment (temperature, supply voltage, etc.);
  • History of states accumulated by the device in internal memory.

Thus, the server performs monitoring both by its own means (by periodic polling for the current state) and by means of SRK-M. This enables to detect problem situations even if there was no connection between the server and the SRK-M when they occurred.

All received data is stored in the database.

In addition, in case of emergenciy, devices initiate connection with the server independently (for example, in case of fire or power failure). Such data is immediately sent by the server to the client application.

Client application

The main screen is shown below:

Main screen of the software

On the left, there is the common tree of devices installed in the system. Devices can be grouped by levels.

In the top right corner, there is a map (uploaded by the user in as a picture) showing all devices and device groups.

The point color on the map indicates the current state:

  • Green - normal state;
  • Blue - connection lost;
  • Red - emergency.

If the point on the map indicates not a device but a group of devices, then its color is formed by "worst state" principle.

By clicking on the map point, the user opens a new level:

By clicking on the map point, the user opens a new level

If a user clicks on device the information about its status appears:

Viewing device status in the program

Main screen of device shows its current status: operating time of air conditioners and their current mode, room temperature, and other technical parameters. Pressing "Emergency poll" button enables to perform off-schedule monitoring of the device.

The other tab shows the following monitoring data in a graphical form:

Information on device monitoring

Air conditioners' state is shown in the temperature chart below: it indicates when a certain air conditioner was enabled/disabled; whether there were any alarms, etc.

Data can be exported in form of image or Excel file.

The monitoring history recorded by the device in internal memory can be viewed on "Log" tab:

Viewing the history in software

"Events" tab displays all changes associated with alarms sent by the devices:

Viewing the received events in the app

"Connection settings" tab allows to set the parameters of connection with the device and the preferred polling frequency:

Settings of connection with the devices

Device settings are set on a specific tab:

Device settings in the software

Server setup

To configure the server we developed a special configurator app allowing to perform complex settings and verify their correctness. So, for example, once incoming server ports are specified, their availability is automatically checked:

Server settings
Server settings
Server settings

Once the configuration is completed, the user is offered to print the client app settings (connection address, etc.):

Printing the server software settings

Notification on events

The server enables to execute any random executable file (exe, cmd, vbs, etc.) after receiving events from devices:

Software development - launch of script for events

Sending of notifications by e-mail can be configured in the same way:

Sending emails after receiving the event

User prompts

To test the server functionability in the client app, there is a special-purpose module checking availability of the server:

Checking server software functionability

The system provides a clear display of the most common failures. For example, the following message is displayed if the client connection to the server is incorrect:

If the user clicks on prompt (displayed in blue font), a short instruction for checking the system settings appears:

Help in troubleshooting software problems