Winery

From AirQ Networks wiki
Jump to: navigation, search
Winery tanks

The most critical factor in wine production, is to control the fermentation process. During this process you have to control tanks temperatures. You can use special tanks than contains must and have a cooling valve for temperature decreasing. Depending of the wine production methods you use, generally the control is made of:

  • Put must in a tank. this action causes a temperature increase;
  • If the temperature is over a certain threshold, you have to open cooling valve to decrease temperature;
  • When temperature is under the threshold, you have to close the valve.

You can set up an automated application using AirQNetworks products.

Suppose you have to control 8 tanks, the application allows user to:

  1. detect tanks temperature;
  2. control cooling valves;
  3. main power failure.

The application shows also how set up following alarm:

  • send SMS (text message) to mobile number and E-Mail if power is done.

Contents


Required stuff

We need following things to setup this application:

Note that for point 2 you can you use different AirQ_3x family products. For example you can use two AirQ 310 (each of these has 6 relays).

Since you can't put a sensor directly into a tank, for each of this you need to use a probe.


Step by step instructions

Next paragraphs will show how setup both hardware and software.

Hardware setup

First step is to setup AirQ300 boards. You have to link boards relays to relative valve and link boards to power adapters. You can setup a switchboard containing boards and power adapters.

How to connect valves to AirQ 300.Hwsetup 1.jpg
About this image
AirQ 300 boardsPower adaptersHwsetup 2.jpg
About this image
A cooling valve controlled by a board relayHwsetup 3.jpg
About this image

Note that for each relay you have to connect a valve For example, Board1.relay1 for tank1 and Board1.relay2 for tank2. So with 4 control boards you can control your eight cooling valves.

Second step is sensors placing. You have to:

  1. place a sensor on or near a tank;
  2. link the sensor to the probe;
  3. put the probe in tank.
Temperature sensorSensor-probe linkA probe putted in the tankHwsetup 4.jpg
About this image




Finally, AirQ 200 control unit must be installed close to a network outlet using an UTP cable and powered up using a switching power adapter.

Software setup

In order to configure software, you have to access to Pingu application, provided by the control unit. Pingu is a web application, so you can access to it by a browser typing in the address bar:

192.168.1.210:9090

The first screen is the login, for the first time use admin for user name and console for password.

After login, dashboard is showed. In the dashboard you can see real-time system status. You can see a box for every component you've installed.



Board 300 boxTemperature boxControl unit statusRename board/sensorRename relay/inputA relay switch (for cooling valve command)A manage rule link iconHistorical temperatures graph linkBoard 3x status history linkDashboard 1.jpg
About this image




In sensors boxes you can see the last data detected and the last detection time. For each control board box, you can command two linked cooling valves clicking on relative relays.

If you go in Setup page you can set a lot of configuration parameters, like Pingu user and password, system language etc...

Assign names

As shown in previous image, you can assign names to the sensors, to the boards and its inputs and relays.

To change the name of an AirQ 101 sensor, click on Name it and insert a name, for example tank 1.

To change the name of an AirQ 300 board, click on Name it and insert a name, for example valve 1-2 controller. Click to RELAY1 to assign name Valve 1 and on RELAY2 to assign name Valve 2.

Define system logic

You can set more complex behaviors by using Pingu rules. To add a new rule, from the dashboard click on the icon Rules.png of the rules of the board/sensors purchased.

For each tank, control the temperature

Suppose that tank temperatures must be in 14°C-15°C interval during fermentation. For each sensors, you must define two rules:

  1. If temperature is lower than 14, cooling valve must be open (tank temperature increase);
  2. If temperature is higher than 15, cooling valve must be closed (tank temperature decrease).

Since a valve is linked to a relay, in terms of relay rules are:

  1. If temperature is lower than 14, close relay linked to cooling valve (tank temperature increase);
  2. If temperature is higher than 15, open relay linked to cooling valve (tank temperature decrease).

From the dashboard, click on rule icon for the temperature sensor to access managing rules page grouped by the temperature sensor. In the add new rule box, you have to define a rule name, an expression and an action.

Rule name definitiondevice selectionValue type selectionComparison operator selectionNumber definition (for the threshold)Device selection for actionrelay selectionSwitching valueAdd rule buttonWineryrule1 1.jpg
About this image
Rule name definitiondevice selectionValue type selectionComparison operator selectionNumber definition (for the threshold)Device selection for actionrelay selectionSwitching valueAdd rule buttonWineryrule1 2.jpg
About this image


send SMS (text message) to mobile number and E-Mail if power is done. If you want to define this alarm, you have to define a rule:

  • Expression: if power is done;
  • Action: send SMS (text message) to mobile number and E-Mail
Manage rulesRule5 1.jpg
About this image
Expression: power is OFFAction: send SMSphone number and text definitioncopy text buttonWineryrule2 1.jpg
About this image
Action: send Email actionaddress and text definitionpaste text buttonWineryrule2 2.jpg
About this image


Data observing

Pingu application offers to you a lot of utilities for data observing. Read Pingu documentation for complete informations.

For example, you can observe temperature trend of a tank, status history of a couple of valves etc...

winery_history_1




winery_history_2

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox