access_via_api
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
access_via_api [2020/04/07 12:01] – [Getting meters log] emozolyak | access_via_api [2020/12/08 13:50] – [Getting data for events] emozolyak | ||
---|---|---|---|
Line 1624: | Line 1624: | ||
Content-Type: | Content-Type: | ||
| | ||
- | Consider an example of two events. Event number 1 is the parent event. It starts on the 5th second of every minute and ends on the 40th second of every minute. The log records data once for the entire event. The time of the beginning of the event and the last value of the interval register I60 are recorded in the log. Screenshots illustrate the setting of this event. | + | Please refer for events |
- | + | ||
- | {{:: | + | |
- | + | ||
- | {{:: | + | |
- | + | ||
- | The second event is the child event for the first event. Therefore, it can only be executed when the first event is executed. In addition, the condition is limited so that it starts at the 25th second of every minute and ends at the 35th. Data for it is written to the log every 2 seconds. The current value of the I60 register is written to the log. Screenshots illustrate the setting of this event. | + | |
- | + | ||
- | {{:: | + | |
- | + | ||
- | {{:: | + | |
- | + | ||
- | {{:: | + | |
Example of getting date about event #1: | Example of getting date about event #1: |
access_via_api.txt · Last modified: 2023/03/02 10:53 by emozolyak