system_settings
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
system_settings [2020/04/07 15:59] – [Trial Mode] emozolyak | system_settings [2023/03/23 09:56] (current) – [System settings storage tab] emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{ network: | ||
+ | |||
====== System settings ====== | ====== System settings ====== | ||
+ | System settings page specify the following: | ||
+ | *Project' | ||
+ | *Depth & limit of data storage in log | ||
+ | *ModBus/TCP server configuration | ||
+ | *Enabling/ | ||
+ | *MQTT server configuration | ||
+ | |||
+ | {{ : | ||
- | System settings | + | ===== System settings |
- | {{settings_new_ready.png? | ||
- | ===== Language | + | ==== Language ==== |
- | 4 languages are available | + | For the |
- | ===== Communication interval | + | *Ukrainian |
+ | *English | ||
+ | *German | ||
+ | *Polish | ||
+ | *Portuguese | ||
+ | *Russian | ||
+ | |||
+ | And you can select ' | ||
+ | |||
+ | ==== Communication interval ==== | ||
Specifies the period of data exchange with the connected devices. WebHMI reads all registers from all devices one by one. One such cycle is named scan. When possible WebHMI will insert delays between scans so they will run with specified interval. | Specifies the period of data exchange with the connected devices. WebHMI reads all registers from all devices one by one. One such cycle is named scan. When possible WebHMI will insert delays between scans so they will run with specified interval. | ||
Line 17: | Line 35: | ||
This settings should be set reasonably. If you need to 'have time' to query a large amount of data for a second, first you need to increase the speed of communication with devices, use the priority of reading the registers in conjunction with the option ' | This settings should be set reasonably. If you need to 'have time' to query a large amount of data for a second, first you need to increase the speed of communication with devices, use the priority of reading the registers in conjunction with the option ' | ||
- | ===== Strict scan ===== | + | ==== Strict scan ==== |
This option allows to get a time-determined scan. It is usable for projects with hundreds and thousands of registers on slow serial connections. | This option allows to get a time-determined scan. It is usable for projects with hundreds and thousands of registers on slow serial connections. | ||
Line 24: | Line 42: | ||
Critical registers should be given high priority in the register properties. And registers with normal priority should be set individually significantly longer polling time than the default scan interval. This will make WebHMI poll them less frequently and make Strict Scan feature possible. | Critical registers should be given high priority in the register properties. And registers with normal priority should be set individually significantly longer polling time than the default scan interval. This will make WebHMI poll them less frequently and make Strict Scan feature possible. | ||
- | ===== Interface refresh | + | ==== Interface refresh ==== |
WebHMI uses Comet technology to push register value changes into browser at the end of every scan where it was changed. Sometimes register value changes too often. To save traffic and resources you can throttle send interval. You can tell WebHMI send these update not often than some interval. This setting is adjustable between 100 ms. up to 5 sec. | WebHMI uses Comet technology to push register value changes into browser at the end of every scan where it was changed. Sometimes register value changes too often. To save traffic and resources you can throttle send interval. You can tell WebHMI send these update not often than some interval. This setting is adjustable between 100 ms. up to 5 sec. | ||
- | ===== Hide menu ===== | + | ==== Override screen resolution ==== |
+ | |||
+ | Some devices’ OS, like smartTV, may report wrong resolution for the browser, lowering it for a convenient view. In most cases this is not desired behaviour in the monitoring systems, because the visualization is developed for the specific display resolution. Now you can force screen resolution to desired. | ||
+ | |||
+ | {{ network: | ||
+ | |||
+ | |||
+ | ==== Hide menu ==== | ||
For some projects it makes sense to hide side menu. This option allows to hide menu by default. | For some projects it makes sense to hide side menu. This option allows to hide menu by default. | ||
- | ===== Log level ===== | + | ==== Log level ==== |
- | This option sets level of the system | + | |
+ | There is a communicacion log to analyze system' | ||
+ | |||
+ | {{ network: | ||
+ | |||
+ | This option sets the log's levels, possible values | ||
* **Disable log** - disabled | * **Disable log** - disabled | ||
* **Errors** - errors only | * **Errors** - errors only | ||
Line 38: | Line 69: | ||
* **Trace+Debug+Info+Errors** - previous with trace data | * **Trace+Debug+Info+Errors** - previous with trace data | ||
- | ===== Keep data in log for ===== | + | **Clear comm log from page** |
- | This option sets the depth of storage of the stored | + | |
+ | The amount of data in the communication | ||
+ | |||
+ | {{ network: | ||
- | ===== Battery power mode ===== | + | ==== Battery power mode ==== |
3 various actions on external power outage: | 3 various actions on external power outage: | ||
* shutdown immediately | * shutdown immediately | ||
Line 47: | Line 82: | ||
* work as long as possible (until battery will be discharged) | * work as long as possible (until battery will be discharged) | ||
+ | ===== Storage settings ===== | ||
+ | |||
+ | These settings affect storage scenario. | ||
+ | ***Disk**: For WebHMI, | ||
+ | ***Limit log storage time & Log disk space limit** settings control when the log data will be automatically deleted from the database - either on aging above set storage time, or when free room on the volume will critically shrink. | ||
+ | |||
+ | {{ : | ||
===== Modbus TCP server ===== | ===== Modbus TCP server ===== | ||
**MobBus server** - when turned on, allows external client to poll the project register using Modbus/TCP protocol. (see [[modbus_tcp_server | function]] description) | **MobBus server** - when turned on, allows external client to poll the project register using Modbus/TCP protocol. (see [[modbus_tcp_server | function]] description) | ||
- | {{modbus_tab2.png? | + | {{ network:modbus_tab2.png? |
+ | |||
+ | ===== Services ===== | ||
+ | |||
+ | In this tab, you can switch on/off several services. Disabling services, that you won't need in the project frees up some OS resources what might be of use in very big projects where the WebHMI is heavily loaded. | ||
+ | |||
+ | ***FTP server** | ||
+ | ***MQTT server** | ||
+ | ***Zabbix agent** - this one is for internal use and had been activly in use during early WebHMI installatoin commissioning purposes. May be switched off. | ||
+ | ***Virtual COM port server** - this one enables a " | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== MQTT server ===== | ||
+ | You can read more about MQTT on [[iot: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | You can add several listeners on different TCP/IP ports which will handle MQTT connections to the WebHMI broker. | ||
+ | |||
+ | |||
+ | |||
===== Trial Mode ===== | ===== Trial Mode ===== | ||
Line 57: | Line 121: | ||
You can protect your project with a trial mode. | You can protect your project with a trial mode. | ||
- | {{ :: | + | {{ network: |
Use this mode with care, otherwise you can lose access to your project. | Use this mode with care, otherwise you can lose access to your project. | ||
- | {{ :: | + | {{ network: |
system_settings.1586275145.txt.gz · Last modified: 2020/04/07 15:59 by emozolyak