Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
en:sw:01-mervis:multiple-history-intervals-hidden [2020/05/27 11:21] avsetula |
en:sw:01-mervis:multiple-history-intervals-hidden [2021/05/03 09:46] avsetula |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ /* FIXME - upraven nadpis článku */ | + | ~~NOTOC~~ |
| - | ====== Multiple history log intervals ====== | + | ====== Advanced history log configuration ====== |
| - | This tutorial describes how to store values into a PLC in different save periods. By doing so you can save a lot of memory space reserved for data, increasing the PLC’s backup storage time. This feature is useful especially for backing up a large amount of data. The solution is also suitable for PLCs connected to the Mervis DB through a connection billed per amount of data used. | + | <WRAP group> |
| - | + | <WRAP half column 81%> | |
| - | /* FIXME - upravený úvod článku | + | 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. |
| - | V tomto návodu se dozvíte jak ukládat záznamy hodnot do PLC v [[#vice_intervalu_pro_zapis_do_historie|různých intervalech]] a také jak nastavit a použít [[#asynchronni_zapis_do_historie|asynchronní režim zápisu]] do databáze. Tím můžete výrazně ušetřit prostor vyhrazený pro ukládání dat a prodloužit tím dobu zálohování na PLC, zvláště pokud zálohujete velké množství dat (proměnných). Máte-li PLC připojeno k Mervis DB a připojení k internetu účtováno podle objemu dat, je pro vás toto řešení také výhodné. | + | </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 1.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. | 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 13: | Line 22: | ||
| - [[en:sw:01-mervis:creating-new-project-hidden|created a project and attached a PLC to it]] | - [[en:sw:01-mervis:creating-new-project-hidden|created a project and attached a PLC to it]] | ||
| - [[en:sw:01-mervis:creating-new-project-hidden#securing_the_controller|secured the PLC]] | - [[en:sw:01-mervis:creating-new-project-hidden#securing_the_controller|secured the PLC]] | ||
| - | - entered **History Runtime Identification** in the PLC’s settings | ||
| - switched the Mervis IDE to [[en:sw:01-mervis:creating-new-project-hidden#switching_from_simple_mode_to_full_mode|Full mode]] | - switched the Mervis IDE to [[en:sw:01-mervis:creating-new-project-hidden#switching_from_simple_mode_to_full_mode|Full mode]] | ||
| + | - entered **History Runtime Identification** in the PLC’s settings | ||
| - the complete project can be seen on a picture below the article | - the complete project can be seen on a picture below the article | ||
| Line 21: | Line 30: | ||
| {{:en:sw:01-mervis:01_multiple-history-intervals_en.png?direct|}} | {{:en:sw:01-mervis:01_multiple-history-intervals_en.png?direct|}} | ||
| + | |||
| + | ===== Multiple logging intervals ===== | ||
| Right-click on **History**. A menu will open - click on **Add New History**. | Right-click on **History**. A menu will open - click on **Add New History**. | ||
| Line 39: | Line 50: | ||
| {{:en:sw:01-mervis:05_multiple-history-intervals_en.png?direct|}} | {{:en:sw:01-mervis:05_multiple-history-intervals_en.png?direct|}} | ||
| - | If you did everything correctly, you now have 5 different history save periods. | + | If you did everything correctly, you now have 5 different history log save periods. |
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| Line 47: | Line 58: | ||
| You can now import the required variables into the **History log**. You can change the save periods later with the already imported variables. | You can now import the required variables into the **History log**. You can change the save periods later with the already imported variables. | ||
| - | /* FIXME - přidána kapitola | + | ===== Asynchronous history logging ===== |
| - | ===== Asynchronní zápis do historie ===== | + | Right-click on **History** and in the menu select **Add New History**. If you already have a history log created, click on it. |
| - | Klikněte pravým tlačítkem myši na položku **Historie**, otevře se nabídka, zde zvolte **Přidat novou historii**. Pokud již máte záznam historie vytvořen, klikněte na něj. | + | {{:cs:sw:01-mervis:06_multiple-history-intervals_cz.png?direct|}}. |
| - | + | ||
| - | {{:cs:sw:01-mervis:06_multiple-history-intervals_cz.png?direct|}} | + | |
| - | V pravém sloupci se zobrazí vlastnosti označeného záznamu, zde zvolte typ **Asynchronous**. Na další položky mapujte proměnné typu bool. | + | In the right column properties of the selected log will appear. Select **Asynchronous** as its type. Map bool variables to the remaining items. |
| - | <html><span class="kbBlueText">První položka slouží k povolení záznamu.</span></html> | + | <html><span class="kbBlueText">The first item is for enabling the logging</span></html> |
| - | * Je-li hodnota ''FALSE'', nelze uložit záznam | + | * If set to ''FALSE'', the logging is disabled |
| - | * Je-li hodnota ''TRUE'', je povoleno ukládat záznamy | + | * If set to ''TRUE'', the logging is enablůed |
| - | <html><span class="kbBlueText">Druhá položka slouží ke spuštění zápisu hodnot:</span></html> | + | <html><span class="kbBlueText">The second item serves for starting the history log</span></html> |
| - | * Hodnota ''FALSE'' - neukládá se | + | * If set to ''FALSE'' - logging is disabled |
| - | * Nastane-li hodnota ''TRUE'', tak s náběžnou hranou se záznam uloží (pokud je i položka povolení TRUE) | + | * When set to ''TRUE'', a log will be saved once a rising edge is detected (if the enable item is also set to TRUE) |
| {{:cs:sw:01-mervis:07_multiple-history-intervals_cz.png?direct|}} | {{:cs:sw:01-mervis:07_multiple-history-intervals_cz.png?direct|}} | ||
| <WRAP center round info 85%> | <WRAP center round info 85%> | ||
| - | Typickým případem použití je čidlo teploty (např. venkovní), u kterého nepotřebujeme ukládat zcela přesnou hodnotu a můžeme tak hodnotu do historie ukládat až ve chvíli, kdy je změněna o ± 1°C od poslední uložené hodnoty. tím zajístíme, že se budou ukládat pouze relevantní údaje. | + | 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> | ||
| - | */ | ||
