events_in_machine_monitoring
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
events_in_machine_monitoring [2020/12/02 16:05] – emozolyak | events_in_machine_monitoring [2022/01/15 19:06] (current) – ↷ Links adapted because of a move operation 127.0.0.1 | ||
---|---|---|---|
Line 4: | Line 4: | ||
The task was to create a report in WebHMI for each machine with these figures for the given period. | The task was to create a report in WebHMI for each machine with these figures for the given period. | ||
- | {{ :: | + | {{ network: |
There is an event report builder, but it in this application it would had the following drawbacks: | There is an event report builder, but it in this application it would had the following drawbacks: | ||
Line 13: | Line 13: | ||
Because all data were logged and existed in the DB, a self-evident appeal arised for the solution or tool, which just would made a request for the required data in the DB and showed them. | Because all data were logged and existed in the DB, a self-evident appeal arised for the solution or tool, which just would made a request for the required data in the DB and showed them. | ||
- | After considering possible solution, the following WebHMI' | + | After considering possible solution, the following WebHMI' |
| | ||
- | *Lua script which makes API request to itself for the run, stop, performace counter values and calculates the differences | + | *Screen widgets: register value to show perfomance data and pie chart to show percentage of run/stop hours |
+ | *Lua script which makes API request to WebHMI | ||
| | ||
*JS to modifiy graph properties (parameter to show and time axis settings) | *JS to modifiy graph properties (parameter to show and time axis settings) | ||
- | {{ :: | + | {{ network:solution_structure.png? |
+ | |||
+ | {{ network: | ||
events_in_machine_monitoring.txt · Last modified: 2022/01/15 19:06 by 127.0.0.1