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:storing-data-to-history-log-hidden [2020/06/23 07:09] avsetula |
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%> | <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-neuron">Neuron</span></html> \\ | ||
| - | <html><span class="dev-tag dev-unipi11">Unipi 1.1</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> | ||
| Line 16: | Line 18: | ||
| <html><span class="kbBlue-H4alt">Prerequisites:</span></html> | <html><span class="kbBlue-H4alt">Prerequisites:</span></html> | ||
| - Unipi controller running the Mervis OS | - Unipi controller running the Mervis OS | ||
| - | - 24V power supply | + | - 24 V⎓ power supply |
| {{ :files:img_breakline_2.png?nolink |}} | {{ :files:img_breakline_2.png?nolink |}} | ||
| Line 31: | Line 33: | ||
| {{ :en:sw:01-mervis:storing-data-to-mervis-db-01-workspace.png?direct |}} | {{ :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 |}} | {{ :en:sw:01-mervis:storing-data-to-mervis-db-02-mervis-db-parameters.png?direct |}} | ||
| Line 69: | Line 72: | ||
| **Deploy Solution**. The PLC is now ready to store variable history locally. You can check the history log's configuration and other related info in the **Output** tab in the bottom panel after clicking on the Deploy solution. Here in the text logs look for ''history statistics''. | **Deploy Solution**. The PLC is now ready to store variable history locally. You can check the history log's configuration and other related info in the **Output** tab in the bottom panel after clicking on the Deploy solution. Here in the text logs look for ''history statistics''. | ||
| - | /* FIXME - překontrolovat podle CZ */ | ||
| <WRAP center round tip 95%> | <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. 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. | ||
