Differences

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

--- en:sw:01-mervis:storing-data-to-history-log-hidden [2020/06/19 12:53]
tomhora
+++ en:sw:01-mervis:storing-data-to-history-log-hidden [2021/08/05 14:50] (current)
avsetula
@@ Line 6: / Line 6: @@
 <WRAP half column 15%>
 ;;#
-<html><span class="dev-tag dev-axon">Axon</span></html> \\
+<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-unipi11">Unipi&nbsp1.1</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>
@@ Line 16: / Line 18: @@
 <html><span class="kbBlue-H4alt">Prerequisites:</span></html>
   - Unipi controller running the Mervis OS
-  - 24V power supply
+  - 24 V⎓ power supply
 {{ :files:img_breakline_2.png?nolink |}}
@@ Line 31: / Line 33: @@
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-01-workspace.png?direct |}}
-Start by selecting the PLC in the **left panel**. In the **Properties** menu, you need to change **Runtime ID for History** attribute, which is used as identification of the PLC's history. If the PLC will be connected to the Mervis DB service the identification will be also used in the Mervis DB viewer visualisation tool. Enter a descriptive name, such as the PLC's location or its function.
+<html><div class="directTag" id="runtime-set"></div></html>
+Start by selecting the PLC in the **left panel**. In the **Properties** menu, you need to change **History Runtime Identification** attribute, which is used as identification of the PLC's history. If the PLC will be connected to the Mervis DB service the identification will be also used in the Mervis DB viewer visualisation tool. Enter a descriptive name, such as the PLC's location or its function.
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-02-mervis-db-parameters.png?direct |}}
@@ Line 51: / Line 54: @@
   * **Type**:''Asynchronous'' enables logging based on an event triggered by a selected variable
-**History log** is now defined and we can add variables into it. On the **main panel** you should see the main workspace. Simply right-click on ''office_Temperature'' global variables and in the context menu click on **Add to History**. Using a similar method you can add variables into history also from the **Variable browser**.
+**History log** is now defined and we can add variables into it. On the **main panel** you should see the main workspace. Simply right-click on ''office_Temperature'' global variables and in the context menu click on **Add to History**.
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-07-add-to-history.png?direct |}}
+Using a similar method you can add variables into history also from the **Variable browser**.
+{{ :en:sw:01-mervis:storing-data-to-mervis-db-07b-add-to-history.png?direct |}}
 **Add to history** window will appear. Choose the correct history log and confirm by clicking on **OK**.
@@ Line 66: / Line 73: @@
 <WRAP center round tip 95%>
-This statistic also displays the period for which the history log will be stored in the PLC before being overwritten by new logs. The value is influenced by logging intervals and the number and data type of logged variables. To maximize the storage period we recommend optimizing these parameters to log values only when a variable change is detected (asynchronous mode). If you want, for example, to log an outdoor temperature value, most applications should be able to make away with a 1-hour interval. Another option is to create a program (block) that compares temperature values to the most current logged ones, and triggers logging in asynchronous mode when the difference is greater than 1°C.
+This statistic also displays the period for which the history log will be stored in the PLC before being overwritten by new logs. The value is influenced by logging intervals and the number and data type of logged variables. To maximize the storage period we recommend optimizing these parameters. If you want, for example, to log an outdoor temperature value, most applications should be able to make away with a 1-hour interval. Another option is to create a program (block) that compares temperature values to the most current logged ones, and triggers logging in asynchronous mode when the difference is greater than 1°C.
 </WRAP>