> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-lorawan-devices/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-vicki-lorawan/vicki-lorawan-device-communication-protocol/temperature-control/deprecated-temperature-control-algorithms.md).

# Deprecated temperature control algorithms

## Proportional control algorithm

{% hint style="info" %}
This algorithm is available for devices with firmware version >= 4.0
{% endhint %}

{% hint style="danger" %}
Devices with firmware version >=4.3 have this algorithm removed as the Proportional Integral control algorithm has been deemed superior due to delivering better results.
{% endhint %}

### **Algorithm logic**

This control algorithm is used by the device to achieve the desired target temperature. Each time the algorithm logic is executed, the motor position is adjusted, so the target temperature is reached. The following block diagram explains the requirements in order for the proportional algorithm logic to be executed.

![](/files/tPSL62UXT1hit9xaeUcL)

The proportional algorithm logic calculates new motor position using the expression:

$$MP\_{new} = MP\_{old} - \cfrac{c\*(T\_{set} - T\_{measured})\*MR}{100}$$, where:

$$MP\_{new}$$: New motor position in steps.

$$MP\_{old}$$: Old motor position in steps.

$$c$$: Proportional algorithm coefficient.

$$T\_{set}$$: Target temperature in Celsius degrees.

$$T\_{measured}$$: Measured temperature in Celsius degrees.

$$MR$$: Motor range in steps.

Note that the algorithm check period and coefficient parameters can be configured by radio commands.

### **Proportional temperature control algorithm parameters**

{% tabs %}
{% tab title="SET" %}

<table><thead><tr><th width="115.05745554035565">Byte index</th><th>Hex value - Meaning</th></tr></thead><tbody><tr><td>0</td><td>2A – The command code.</td></tr><tr><td>1</td><td>XX – Value for the proportional algorithm coefficient to be set. Maximum acceptable value is 20.</td></tr><tr><td>2</td><td>XX – Value of the proportional algorithm control period, in minutes.</td></tr></tbody></table>

**Example command:** `0x2A040C` – Set the proportional algorithm coefficient to 4 and the check period to 12 minutes.
{% endtab %}

{% tab title="GET" %}

<table><thead><tr><th width="135">Byte index</th><th width="157">Sent request</th><th>Response - Meaning</th></tr></thead><tbody><tr><td>0</td><td>29 – The command code.</td><td>29 – The command code.</td></tr><tr><td>1</td><td> </td><td>XX – Value of the proportional algorithm coefficient. Maximum acceptable value is 20. Default value is 3.</td></tr><tr><td>2</td><td> </td><td>XX – Value of the proportional algorithm control period, in minutes. Default value is 10 minutes.</td></tr></tbody></table>

**Example command:** `0x29`

**Example response:** `0x29030F` – Coefficient: 3, control period: 15 minutes.
{% endtab %}
{% endtabs %}

## Equal directional control algorithm

{% hint style="danger" %}
This algorithm is NOT available in f.w. >= 4.2
{% endhint %}

{% hint style="info" %}
This algorithm is the **only** algorithm available for f.w. < 4.0.
{% endhint %}

### Internal temperature control algorithm parameters

This command must be used carefully and according to the used online temp. control algorithms. Be sure that the default command parameters aren’t satisfactory before overwriting them. The following parameters are introduced for ease of command explanation:

* Pfirst/last: Indicate the first motor position change in valve opening direction and the last motor position change in valve closing direction;
* Pnext: Indicate the next motor position change in valve opening/closing direction;
* Talg: The period for motor position change decisions depending on the desired and measured temperatures;
* Tdiff open/close: Temperature difference between the target $$T\_{target}$$ and measured $$T\_{measured}$$ temperatures, to be surpassed, to get decision for valve movement. This parameter is set with separate command for compatibility with older device software versions.

Check Figure 1 for command and entire internal algorithm operation understanding. The example scenario shown on the figure is for heating primary device mode. The algorithm operation is analogical for cooling device primary mode with the only difference that under cooling mode the valve is opened in order to lower the ambient temperature, not to rise it. Check the table below for additional algorithm understanding under different device primary modes.

<table data-header-hidden><thead><tr><th>Device primary mode</th><th width="283.66666666666663">Heating</th><th>Cooling</th></tr></thead><tbody><tr><td><strong>Device primary mode</strong></td><td><strong>Heating</strong></td><td><strong>Cooling</strong></td></tr><tr><td><strong>Valve opened if</strong></td><td> <span class="math">(T_{target}-t_{measured}) > T_{diff  open}</span> </td><td><span class="math">(T_{target} - T_{measured}) &#x3C; -T_{diff open}</span> </td></tr><tr><td><strong>Valve closed if</strong></td><td><span class="math">(T_{target}-T_{measured}) &#x3C; -T_{diff close}</span> </td><td><span class="math">(T_{target} - T_{measured}) > T_{diff closed}</span> </td></tr></tbody></table>

! **Important note on the algorithm operation.**

{% hint style="warning" %}
The implemented temperature control algorithm is compliant with the stepper motor mechanical system. It's mandatory the valve to be opened and later closed with same number of movements per direction. Also, each movement at one of the directions must be with equal number of steps, to the corresponding movement to the other direction. This fashion of motor control is needed, to struggle the loss of generated steps, due to the motor mechanical system backlash. It can be observed in the image below.
{% endhint %}

If Vicki works in mode at which the motor position is set through the server, it is mandatory the server moves the valve with same number of steps, as the internal algorithm (Pfirst/last, Pnext). Also, Pfirst/last/next values less than 16 steps are meaningless.

![](/files/-McO5BkcctbU9c-AK1Fe)

The table below described the commands to SET/GET the device internal temperature control algorithm parameters, except the Tdiff open/close which is set with separate command.

{% tabs %}
{% tab title="SET" %}

<table data-header-hidden><thead><tr><th width="135.20724027353867">Byte index</th><th>Hex value - Meaning</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Hex value - Meaning</strong></td></tr><tr><td>0</td><td>0C – The command code.</td></tr><tr><td>1</td><td><p>XX – Internal algorithm temperature check period in minutes – Talg. </p><p>Default value for firmware &#x3C;3.5 is 20min.<br>Default value for firmware >=3.5 is 10 min.</p></td></tr><tr><td>2</td><td>XX – Internal algorithm first/last opening/closing steps – Pfirst/last. Default value 20 steps.</td></tr><tr><td>3</td><td>XX – Internal algorithm next opening/closing steps – Pnext. Default value 20 steps.</td></tr></tbody></table>

**Example command:** `0x0C131111`

With the example command, the internal temperature control algorithm parameters are set as follows: Talg = 19 minutes, Pfirst/last = 17 steps, Pnext = 17steps.

{% hint style="danger" %}
For f.w. version <= 4.0: The minimum applicable value for Pfirst/last and Pnext is 17 steps!

For f.w. version >= 4.1: The minimum applicable value for Pfirst/last and Pnext is 8 steps!

**If you set a lower value, the device will misbehave!**
{% endhint %}
{% endtab %}

{% tab title="GET" %}

<table data-header-hidden><thead><tr><th width="131.66666666666666">Byte index</th><th width="150">Sent request</th><th>Received response</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Sent request</strong></td><td><strong>Received response</strong></td></tr><tr><td>0</td><td>16 – Command code.</td><td>16 – The command code.</td></tr><tr><td>1</td><td></td><td>XX – Internal algorithm temperature check period in minutes – Talg.</td></tr><tr><td>2</td><td></td><td>XX – Internal algorithm first/last opening/closing steps – Pfirst/last.</td></tr><tr><td>3</td><td></td><td>XX – Internal algorithm next opening/closing steps – Pnext.</td></tr></tbody></table>

**Example command:** `0x16`

**Example response:** `0x16141111` – Talg=20 minutes, Pfirst/last=17 steps,

Pnext=17 steps.
{% endtab %}
{% endtabs %}

### Internal temperature control algorithm parameters – Tdiff only

These commands are used to SET/GET the Tdiff open/close parameters.

{% tabs %}
{% tab title="SET" %}

<table data-header-hidden><thead><tr><th width="132">Byte index</th><th>Hex value - Meaning</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Hex value - Meaning</strong></td></tr><tr><td>0</td><td>1A – The command code.</td></tr><tr><td>1</td><td>XX – Tdiff open value, [°C]. The resolution is 1°C. Default value is 0x01 (1°C) for firmware &#x3C;3.5.<br>Default value is 0x00 (0°C) for firmware >= 3.5. </td></tr><tr><td>2</td><td>XX – Tdiff close value, [°C]. The resolution is 1°C. Default value is 0x01 (1°C) for firmware &#x3C;3.5.<br>Default value is 0x00 (0°C) for firmware >= 3.5. </td></tr></tbody></table>

**Example command:** `0x1A0201`

With the example command, Tdiff open is set to 2°C and Tdiff close is set to 1°C.&#x20;
{% endtab %}

{% tab title="GET" %}

<table data-header-hidden><thead><tr><th width="132.66666666666666">Byte index</th><th width="145">Sent request</th><th>Received response</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Sent request</strong></td><td><strong>Received response</strong></td></tr><tr><td>0</td><td>17 – Command code.</td><td>17 – The command code.</td></tr><tr><td>1</td><td></td><td>XX – Tdiff open value, [°C]. The resolution is 1°C.</td></tr><tr><td>2</td><td></td><td>XX – Tdiff close value, [°C]. The resolution is 1°C.</td></tr></tbody></table>

**Example command:** `0x17`

**Example response:** `0x170201` – Tdiff open=2°C, Tdiff close=1°C.
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-vicki-lorawan/vicki-lorawan-device-communication-protocol/temperature-control/deprecated-temperature-control-algorithms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.