registers
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
registers [2021/11/01 15:37] – [Basic tab] emozolyak | registers [2021/12/09 16:35] – [Log tab settings] emozolyak | ||
---|---|---|---|
Line 34: | Line 34: | ||
***Address** The address in the address space of this connection. While entering value, the address validation is being made. Address assignment format depends upon protocol type and usually comprised of a ' | ***Address** The address in the address space of this connection. While entering value, the address validation is being made. Address assignment format depends upon protocol type and usually comprised of a ' | ||
***Description** - description field for the register | ***Description** - description field for the register | ||
+ | <wrap em>As of 4.1 fw version, the description is also shown right on the register tree when hovering mouse pointer over the registers' | ||
+ | {{ :: | ||
+ | |||
***Category** - the name of the group to which the register will be included. | ***Category** - the name of the group to which the register will be included. | ||
+ | |||
+ | <wrap em>As of 4.1 fw version, there is inline category renaming option</ | ||
+ | |||
+ | The ability to set categories for objects has existed in WebHMI for a long time and is a convenient tool for structuring a project. As a rule, if you enter the correct name for a category right away, it remains unchanged. However, it turned out that renaming categories is not a very simple matter, especially when you need to do a lot of renaming – for this you had to create another category and transfer the necessary objects to it. (in this case, the project was also reinitialized). Now this can be done by simply clicking on the edit icon in the category name. | ||
+ | |||
+ | {{ : | ||
+ | |||
***Priority** - polling priority. This option is used in conjunction with the Strict scan function. Registers with high priority will be polled first, registers with priority normal in the second turn. If part of the registers with normal priority does not fit during the scan, this part is polled in the next scan, etc. Registers from internal connections are polled last (after registers on external connections) regardless of this setting, since they are read quickly on the local bus of the WebHMI device. If you do not need read current register in normal operation mode you can select "Read on demand" | ***Priority** - polling priority. This option is used in conjunction with the Strict scan function. Registers with high priority will be polled first, registers with priority normal in the second turn. If part of the registers with normal priority does not fit during the scan, this part is polled in the next scan, etc. Registers from internal connections are polled last (after registers on external connections) regardless of this setting, since they are read quickly on the local bus of the WebHMI device. If you do not need read current register in normal operation mode you can select "Read on demand" | ||
***Script alias** - This name can be used in lua scripts. | ***Script alias** - This name can be used in lua scripts. | ||
Line 41: | Line 51: | ||
***Send real time data to WebHMI cloud** checknox - Specifies whether to send data to the cloud-based level2 system. | ***Send real time data to WebHMI cloud** checknox - Specifies whether to send data to the cloud-based level2 system. | ||
- | <wrap em>Startging | + | <wrap em>Starting |
+ | === Read/Write mode settings === | ||
There is now a convenient function for assigning register access mode – “read / write”, “read-only”, | There is now a convenient function for assigning register access mode – “read / write”, “read-only”, | ||
Read-only mode is also useful for distributed systems with shared data. For example, this situation can arise when using the MQTT protocol, when the user can inadvertently override the data of another device. | Read-only mode is also useful for distributed systems with shared data. For example, this situation can arise when using the MQTT protocol, when the user can inadvertently override the data of another device. | ||
{{ :: | {{ :: | ||
+ | |||
+ | === Save and Apply === | ||
+ | |||
+ | When editing a project, it is often necessary to make several edits in different places in the project. Before, each small change was accompanied by re-initialization of the system, which in turn caused a heavy load on the processor in large projects. Now, there is a tool that allows you to make many edits and then apply them in one go, which ultimately speeds up the time to complete these operations. | ||
+ | |||
+ | {{ :: | ||
+ | |||
===== Value tab settings ===== | ===== Value tab settings ===== | ||
Line 156: | Line 174: | ||
**Send log data to Level2 system** | **Send log data to Level2 system** | ||
+ | |||
+ | == Register' | ||
+ | Refer to the [[registers_log? | ||
+ | |||
+ | |||
+ | |||
===== Resources tab ===== | ===== Resources tab ===== |
registers.txt · Last modified: 2024/04/11 08:13 by emozolyak