Differences

This shows you the differences between two versions of the page.

--- en:sw:01-mervis:multiple-history-intervals-hidden [2020/06/01 13:24] – jan_kozak
+++ en:sw:01-mervis:multiple-history-intervals-hidden [2025/07/09 13:45] (current) – added warning about history and ram ofojt
@@ Line 1: / Line 1: @@
 ~~NOTOC~~
 ====== Advanced history log configuration ======
+<WRAP group>
+<WRAP half column 81%>
 This guide demonstrates how to log historic values in [[#multiple_logging_intervals|different intervals]] and also how to set up and use the [[#asynchronous_history_logging|asynchronous history logging]] into a database. By using this feature you can considerably decrease the memory space needed for history logs, increasing the duration of PLCs backup - this is useful especially in case of backing up a large amount of data (variables). The solution is also a good choice for projects in which the PLC is connected to Mervis DB via connections charged by used data volume.
+</WRAP>
+<WRAP half column 15%>
+;;#
+<html><span class="dev-tag dev-patron">Patron</span></html> \\
+<html><span class="dev-tag dev-neuron">Neuron</span></html> \\
+<html><span class="dev-tag dev-gate">Gate</span></html> \\
+<html><span class="dev-tag dev-unipi11">Unipi&nbsp1.1</span></html> \\
+<html><span class="dev-tag dev-axon">Axon</span></html>
+;;#
+</WRAP>
+</WRAP>
 Generally speaking, we recommend setting the save periods as long as possible to save up the PLC’s memory and decrease the load on both your network and servers.
@@ Line 17: / Line 30: @@
 {{:en:sw:01-mervis:01_multiple-history-intervals_en.png?direct|}}
+{{page>en:sw:01-mervis:store-history-in-ram-hidden}}
 ===== Multiple logging intervals =====
@@ Line 39: / Line 54: @@
 If you did everything correctly, you now have 5 different history log save periods.
-<WRAP center round important 60%>
+<WRAP group center round box 95%>
+{{ :files:img_warning-line_b.png?nolink |}}
+<WRAP half column 13%>
+{{ :en:hw:09_safety-instructions_pseudo-ISO-7010-attention.png?nolink |(!)}}
+</WRAP>
+<WRAP half column 83%>
+**Attention:** \\
 Do not mistake these **save period** settings with those for configuring the **communication period** for storing into the Mervis DB.
+</WRAP>
 </WRAP>
@@ Line 61: / Line 83: @@
 {{:cs:sw:01-mervis:07_multiple-history-intervals_cz.png?direct|}}
-<WRAP center round info 85%>
+<WRAP group center round box 95%>
-A typical application is a temperature sensor (ie. an outdoor thermometer), for which we do not need to store its exact value. Instead, we can log the temperature value only if it changes by more than ± 1°C compared to the last logged value. By doing so, we can ensure only relevant data will be logged.
+{{ :files:img_warning-line_b.png?nolink |}}
+<WRAP half column 13%>
+{{ :en:hw:08_safety-instructions_pseudo-ISO-7010-info.png?nolink |(!)}}
+</WRAP>
+<WRAP half column 83%>
+**Note:** \\
+A typical application is a temperature sensor (ie. an outdoor thermometer), for which we do not need to store its exact value. Instead, we can log the temperature value only if it changes by more than ±1 °C compared to the last logged value. By doing so, we can ensure only relevant data will be logged.
+</WRAP>
 </WRAP>