faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faq [2021/08/27 10:19] – emozolyak | faq [2021/12/14 14:01] – [Responsive design with screens] emozolyak | ||
---|---|---|---|
Line 2: | Line 2: | ||
===== Screens, Dashboard visualization ===== | ===== Screens, Dashboard visualization ===== | ||
+ | |||
+ | ==== Responsive design with screens ==== | ||
+ | |||
+ | Question: Is it possible to make a responsive visualizatoin with WebHMI? | ||
+ | |||
+ | Starting from 3.6 version and [[screens? | ||
+ | |||
+ | Please follow the screen documentaion page to make an idea of its possibiliies. | ||
+ | |||
+ | E.g. if your screen looks like this one on the desktop large monitor: | ||
+ | {{ :: | ||
+ | |||
+ | then on the mobile device it will fold in into these: | ||
+ | |||
+ | {{:: | ||
==== Screen text widget ==== | ==== Screen text widget ==== | ||
Line 10: | Line 25: | ||
<WRAP center round tip 100%> | <WRAP center round tip 100%> | ||
- | The register values in the WebHMI are coloourized | + | The register values in the WebHMI are colourized |
- | it is either default value color, or the color defined in the register [[registers? | + | So, to make your register value of a desired colour, set a STATE for the register with the colour you want. |
- | there is a default | + | |
- | the value colour can be either STATE COLOR or DEFAULT VALUE color. | ||
- | |||
- | So, to make your register value of desired colour, set a STATE for the register with the colour for this state. Then the register will have the colour you want | ||
</ | </ | ||
+ | {{ :: | ||
+ | ===== Performance issues ===== | ||
+ | ==== My WebHMI is slow ==== | ||
+ | There are many reasons why your device may slow down, a " | ||
+ | |||
+ | Below a summary of the possible causes is provided: | ||
+ | |||
+ | == Screens / Dashboards == | ||
+ | |||
+ | * Use screens wherever is possible for visualisation, | ||
+ | * Avoid using bulky DASHBOARDS (too rich in elements, having heavy-weight pictures , trends with long time window etc. ) , normal dashboard is about tens of KB, not MB! | ||
+ | * Set appropriate refresh time in the settings. | ||
+ | * Keep the number of open tabs minimal for the current sessions. If you need multiple tabs, use auto-close session checkbox to prevent unattended access. | ||
+ | |||
+ | === Scripts === | ||
+ | |||
+ | *Avoid using many scripts (like dashboards scripts or upon change value scripts). The better way is using a few big scripts or scripts with libraries | ||
+ | *Run scripts upon changing value, minimize the number of scripts, running in each scan | ||
+ | *Minimize " | ||
+ | |||
+ | === Communication === | ||
+ | *Group register to read on external device and use group reading. | ||
+ | *Decrease timeout and tries in external connections | ||
+ | *Organize and set different reading periods for variables. | ||
+ | *Keep the actual T1 time less than system scan set in the settings. this will give more " | ||
+ | |||
+ | === Writing to log === | ||
+ | *Minimize logging many registers to DB, | ||
+ | *Set appropriate log speed for the registers.check you don't have many events logged each scan. | ||
+ | |||
+ | === Development process === | ||
+ | *Keep the number of registers in the project below 2-3K | ||
+ | *During development, | ||
+ | *Avoid making simultaneous changes at once, like turning OFF-ON many regs, connection, scripts etc. Use save & apply feature of the latest fw. (apply all changes at once, instead of creating a queue for changes..) | ||
+ | *In the comm. log, you can set TRACE level and see what times each operation takes (each connection, script, communication with device etc.), checking timestamps | ||
- | {{ :: |
faq.txt · Last modified: 2024/08/05 13:14 by emozolyak