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/06/01 10:13] avsetula |
en:sw:01-mervis:multiple-history-intervals-hidden [2021/05/03 09:46] avsetula |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| ====== Advanced history log configuration ====== | ====== Advanced history log configuration ====== | ||
| - | /* | + | <WRAP group> |
| - | 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 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. | 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 55: | Line 65: | ||
| <html><span class="kbBlueText">The first item is for enabling the logging</span></html> | <html><span class="kbBlueText">The first item is for enabling the logging</span></html> | ||
| - | ''FALSE'', nelze uložit záznam | ||
| * If set to ''FALSE'', the logging is disabled | * If set to ''FALSE'', the logging is disabled | ||
| * If set to ''TRUE'', the logging is enablůed | * 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> |
| * If set to ''FALSE'' - logging is disabled | * 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) | * When set to ''TRUE'', a log will be saved once a rising edge is detected (if the enable item is also set to TRUE) | ||
