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 15:34] – 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: | ||
+ | *N reports would have to be configured. | ||
+ | *For each N several events would have to set up - for day, night, shifts, weeks etc reports | ||
+ | *There reports would likely be occasionally broken at the times when admin changes something in the project. | ||
+ | |||
+ | 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' | ||
+ | | ||
+ | | ||
+ | *Lua script which makes API request to WebHMI itself for the run, stop, performace counter values and calculates the differences | ||
+ | | ||
+ | *JS to modifiy graph properties (parameter to show and time axis settings) | ||
+ | |||
+ | {{ network: | ||
+ | |||
+ | {{ network: | ||
- | There is an event report builder, but it in this application it would lead to overhead : duplication of N report |
events_in_machine_monitoring.txt · Last modified: 2022/01/15 19:06 by 127.0.0.1