Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:sw:01-mervis:multiple-history-intervals-hidden [2020/05/27 11:16] avsetula |
en:sw:01-mervis:multiple-history-intervals-hidden [2021/08/05 14:52] avsetula [Asynchronous history logging] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Multiple history log intervals ====== | + | ~~NOTOC~~ |
- | 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. | + | ====== Advanced history log configuration ====== |
- | + | <WRAP group> | |
- | /* FIXME - upravený úvod článku | + | <WRAP half column 81%> |
- | 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é. | + | 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 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 12: | 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 20: | 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 38: | 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 45: | Line 57: | ||
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. | ||
+ | |||
+ | ===== Asynchronous history logging ===== | ||
+ | Right-click on **History** and in the menu select **Add New History**. If you already have a history log created, click on it. | ||
+ | {{:cs:sw:01-mervis:06_multiple-history-intervals_cz.png?direct|}}. | ||
+ | |||
+ | 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">The first item is for enabling the logging</span></html> | ||
+ | * If set to ''FALSE'', the logging is disabled | ||
+ | * If set to ''TRUE'', the logging is enablůed | ||
+ | |||
+ | <html><span class="kbBlueText">The second item serves for starting the history log</span></html> | ||
+ | * If set to ''FALSE'' - logging is disabled | ||
+ | * 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|}} | ||
+ | |||
+ | <WRAP center round info 85%> | ||
+ | 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> |