Differences

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

--- en:sw:01-mervis:storing-data-to-mervis-db-hidden [2020/05/25 14:42]
avsetula
+++ en:sw:01-mervis:storing-data-to-mervis-db-hidden [2024/04/03 10:03] (current)
avsetula [Storing data into Mervis DB]
@@ Line 1: / Line 1: @@
 ====== Storing data into Mervis DB ======
+<WRAP group>
+<WRAP half column 81%>
 In this tutorial, we are going to demonstrate how to use history logs for long-term storing of data from Unipi controllers running Mervis OS.
+</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>
 <WRAP center round box>
 <html><span class="kbBlue-H4alt">Prerequisites</span></html>
   * Unipi controller running Mervis OS
-  * 24V power supply
+  * 24 V⎓ power supply
   * Mervis IDE project created according to [[storing-data-to-history-log-hidden|Storing data to history log]]
-  * [[en:sw:01-mervis:03-mervis-db|Mervis DB]] login info ([[en:sw:01-mervis:getting-mervis-licence-hidden|a tutorial]] how to obtain it)
+  * [[en:sw:01-mervis:03-mervis-db|Mervis DB]] credentials
 </WRAP>
+<WRAP center round info>
+The Mervis DB credentials are generated together with the Mervis SCADA project and are intended for all PLCs connected to this SCADA project.
+----
+If you are only interested in the Mervis DB without Mervis SCADA, please [[https://www.unipi.technology/contacts|contact our sales department]] for an individual offer.
+</WRAP>
 ===== PLC properties settings =====
 The first step is to  [[storing-data-to-history-log-hidden#memory_storage_settings|set up the storage]].
+/* Přeložit z CZ - rozděleno na dva odstavce */
 If you wish to use the Mervis DB service to back up variables using our servers, you need to set its communication parameters first. In the **left panel**, select PLC.
@@ Line 23: / Line 47: @@
   * **Communication period [min]**: this is the period in which the PLC will send the gathered data
   * **Certificate validation**: set to ''FALSE'' by default, more info in the [[en:sw:01-mervis:ssl-certification-validation-hidden|Certificate validation]]
-  * **Username**: the Mervis DB username you obtained from your account on [[http://unipi.technology|unipi.technology]]
+  * **Username**: the Mervis DB username
-  * **Password**: the Mervis DB password you obtained from your account on [[http://unipi.technology|unipi.technology]]
+  * **Password**: the Mervis DB password
-<WRAP center round tip 80%>
+<WRAP center round info 90%>
+Mervis DB credentials are available in the [[https://www.unipi.technology/customer/scada/|Mervis SCADA project administration]] (customer portal).
+</WRAP>
+<WRAP center round tip 90%>
 Observant users probably realized we just entered a second different time parameter, namely the **Communication period**.
@@ Line 38: / Line 65: @@
 </WRAP>
-Since we changed the configuration of the PLC, we need to upload it. Right click on the PLC in the **Left panel** and select the <html><span class="avBlueText">PLC Operation</span></html> -> <html><span class="avBlueText">PLC Setup</span></html> -> <html><span class="avBlueText">Upload configuration</span></html>. If you are not sure, check out the [[en:sw:01-mervis:updating-a-runtime-configuration-hidden|Uploading a RunTime configuration]] tutorial.
+Since we changed the configuration of the PLC, we need to upload it. Right click on the PLC in the **Left panel** and select the <html><span class="avBlueText">PLC Operation</span></html> -> <html><span class="avBlueText">PLC Setup</span></html> -> <html><span class="avBlueText">Upload configuration</span></html>. If you are not sure, check out the [[en:sw:01-mervis:updating-a-runtime-configuration-hidden|Uploading a RunTime configuration]] tutorial.
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-03-upload-configuration.png?direct |}}
-You will be asked how to connect to the PLC. If you are on the same network, you can select **UDP Broadcast**. If not (ie. you use a proxy connection), select **Use deploy parameters** and confirm by clicking on **OK**.
+You will be asked how to connect to the PLC. If you are on the same network, you can select **UDP Broadcast**. If not (ie. you connect to the PLC via Mervis Proxyn), select **Use deploy parameters** and confirm by clicking on **OK**.
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-04-probing-method.png?direct |}}
-Deploy the solution, start the Debugging Mode and open the **System status** tab located on the **main panel**. In the **MervisDB** section (or **RcWareDB** in older versions of the IDE), you can check if the PLC communicates with Mervis DB. If the **Communication interval [min]** is set to 1 minute, the **Saved logs** value will increase every 60 seconds.
+Deploy the solution, start the Debugging Mode and open the **System status** tab located on the **main panel**. In the **MervisDB** section (or **RcWareDB** in older versions of the IDE), you can check if the PLC communicates with Mervis DB. If the **Communication interval [min]** is set to 1 minute, the **Records saved** value will increase every 60 seconds.
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-12-system-status.png?direct |}}
 Let's move into the Mervis DB Viewer - a web tool for analyzing data stored by controllers. Open a web browser and enter [[https://db.unipi.technology/viewer|]] address. A login screen will appear - enter the login info used in the PLC settings. Upon entering them, click on **Set** and then on **Close**.
+<WRAP center round box>
+If Mervis DB fails to display data even if you configured everything correctly, it is probably caused by the fact Mervis DB does not have any logged data yet. Close the Mervis DB Viewer and wait until the first log is uploaded - the required time for this varies depending on communication intervals set for the PLC and DB, or on the history log interval. The interval can be synchronous (eg. with a fixed upload time) or asynchronous (the interval depends on how long it takes for data to be logged). If the issue persists even then, check Mervis DB login and password, make sure the address is set correctly and also make sure you [[en:sw:01-mervis:updating-a-runtime-configuration-hidden|uploaded the configuration into the PLC]] correctly.
+</WRAP>
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-10-mervis-db-viewer-login.png?direct |}}
-Mervis DB web interface will open. In its **left panel** your PLC should be visible, identified by the name you entered into **History runtime identification**. Click on it to display a list of variables selected in the History log. Select them all to start parsing their values.
+Mervis DB web interface will open. In its **left panel** your PLC should be visible, identified by the name you entered into **History runtime identification**. Check the box next to their names to start plotting their data in the graph.
 {{ :en:sw:01-mervis:storing-data-to-mervis-db-11-mervis-db-viewer-workspace.png?direct |}}
-You can visually check our simple temperature regulator project works. Using the cursor you can display parsed data values, set various different graph types and many more options.
+Using the cursor you can display parsed data values, set various different graph types and many more options.