Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Introduction

In this section we will explain the sensor and device configuration of the Site Controller in regards of the automated rules which can be configured through the Engine or via the sensor XML file directly.

For your understanding, there is an Information flow, which describes how the the information flows from the sensors to the Site Controller and eventually to the Engine.

On this page:


Overview of an complete Configuration

A Site configuration consists of 4 different types of layers

We will go over them in the next pages.

<?xml version="1.0" encoding="UTF-8"?>
<component_template  config_version="1.1" schema_version="1.0">
 <description>Azeti Demo Container Kit Meeting Room</description>
 <vendor>azeti</vendor>
  <version>1.12</version>
  <class>multi sensor</class>
  <sensors>
    <sensor sensor_id="Name of Sensor">
      
    </sensor>
  </sensors>
  <devices>
    <device device_id="Name of Device">
 	.
    </device>
  </devices>
  <actions>
    <action action_id="Name of Action">
    .
    </action>
  </actions>
  <ac_rules>
    <rule="Name of Rule">	

    </rule>
  </ac_rules>
</component_template>




Information flow

This section describes how the information flow from the sensors to the Site Controller, and eventually to our Cloud server. This will be illustrated with examples and diagrams that will help you understand how are the events and results flowing in the system. The diagrams pretend to illustrate a concrete flow of information, therefore in each of them we will draw and describe the main modules and topics involved outlining their role in the information flow.

Flow of information when the system start

The starting script runs all processes simultaneously. Therefore, you may expect a load peak at the moment you are starting. All modules subscribe to their corresponding configuration topics in the mosquitto broker, and wait to receive their configuration. In case the mosquitto broker was not stopped, it will have the latest valid configuration for the modules, so it will be distributed to the modules immediately. In case there is no configuration (or the configuration file has changed), the module Configuration Provider will parse the configuration and distribute the configuration to all the modules using the topic /config/module/%NameOfModule. Once a module receives its configuration, it is ready to start performing its function.

Information flow for a Data Acquisition Module

The following diagram shows how the information flows across the system, from a sensing device to the cloud server.

Information flow for automatic control based on parameters

This is an example of the information flow of a system configured to perform a closed loop in temperature regulation. The system senses the temperature and, based on its readings, it will activate a pump for an air conditioning device.

Next Steps

  • No labels