WebHMI Docs

User Tools

Site Tools

registers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
registers [2020/02/11 15:07] – [Creating a register, basic settings] emozolyakregisters [2024/04/11 08:13] (current) – [Log tab settings] emozolyak
Line 1: Line 1:
 +{{ network:menu-icon-registers.png?nolink&40|}}
 ====== Working with registers ====== ====== Working with registers ======
 ===== General information ===== ===== General information =====
- 
- 
 In the world of industrial automation, //Registers// are understood as units of data that are attributes of automation equipment. They can describe some external parameters of technological processes (the value of temperature, pressure, flow, state of actuators, etc.) or internal states of the devices themselves (parameters of regulators, filters, alarms etc.). In the world of industrial automation, //Registers// are understood as units of data that are attributes of automation equipment. They can describe some external parameters of technological processes (the value of temperature, pressure, flow, state of actuators, etc.) or internal states of the devices themselves (parameters of regulators, filters, alarms etc.).
  
 Registers in the WEBHMI project correspond to similar concepts in automation systems - 'tag', 'variable' and indicate what data from the respective devices we are going to work on (read / write), in addition, they have additional attributes controlling how they will be displayed and processed by the system settings of these registers. The registers can be of two types - Registers in the WEBHMI project correspond to similar concepts in automation systems - 'tag', 'variable' and indicate what data from the respective devices we are going to work on (read / write), in addition, they have additional attributes controlling how they will be displayed and processed by the system settings of these registers. The registers can be of two types -
-  ***internal** (from internal WebHMI memory) +  ***internal** (from internal WebHMI memory, see the [[webhmi_internal_registers|options]]) 
   ***external** (containing data from connected devices).    ***external** (containing data from connected devices). 
  
 Register settings in WebHMI arranged in 6 tabs, which will be explained later in details: Register settings in WebHMI arranged in 6 tabs, which will be explained later in details:
-{{::reg_tabs2.png?direct&800|}}+ 
 +{{ network:reg_settings_tabs.png?direct&600 |}}
  
   ***Basic info** tab - specifies key addtibutes like name of the register, its connection, memory address etc.    ***Basic info** tab - specifies key addtibutes like name of the register, its connection, memory address etc. 
Line 17: Line 17:
   ***Resources** - explicitly sets a special attribute, if the register contains data of a resource meter (heat, electricity etc.). Then the user can use ready tools for analytics in Level2 based on this data.     ***Resources** - explicitly sets a special attribute, if the register contains data of a resource meter (heat, electricity etc.). Then the user can use ready tools for analytics in Level2 based on this data.  
   ***States** - set alarm status (colorising) for registers - off, normal, warning, alert. In this case, visual elements (text, icons) and data in the log change color according to the register's state.   ***States** - set alarm status (colorising) for registers - off, normal, warning, alert. In this case, visual elements (text, icons) and data in the log change color according to the register's state.
-  ***Alerts** - if the register has alert bits set, then the system automatically shows alert status and saves them in a alert log.  
   ***Cross reference** - to quickly find places of usage of a register   ***Cross reference** - to quickly find places of usage of a register
-===== Creating a register, basic settings =====+===== Creating a register =====
  
 ---- ----
  
-To create a register, go to the //Setup//-> //Registers// menu and click the Add New Register button.+To create a register, go to the //Setup//-> //Registers// menu and click the Add New Register button (or '+' sign in the connection name end). 
 + 
 +{{ network:add_register_methods.png?direct&600 |}}
  
-{{create_reg_1.png}}+===== Basic tab =====
  
-Then in the Basic info tab it will indicate: +{{ network:basic_tab_overview.png?direct&600 |}}
  
   ***Connection** the registers belongs to    ***Connection** the registers belongs to 
Line 33: 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 'letter + digit' sequence. The letter indicates memory address space and the digit is an offset in this memory. See [[supported_protocols]].   ***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 'letter + digit' sequence. The letter indicates memory address space and the digit is an offset in this memory. See [[supported_protocols]].
   ***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' title </wrap>
 +{{ network:title_hint.png?direct&600 |}}
 +
   ***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</wrap>
 +
 +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.
 +
 +{{ network:rename_cat_inline.gif?direct |}}
 +
   ***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. In this case register will be read only when operator will request it manually.   ***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. In this case register will be read only when operator will request it manually.
   ***Script alias** - This name can be used in lua scripts.   ***Script alias** - This name can be used in lua scripts.
Line 39: Line 50:
   ***Communication interval override** - Override the default polling time for this register (Setup / Settings menu). Adjustable in steps of 500 ms. Up to 1 hour.   ***Communication interval override** - Override the default polling time for this register (Setup / Settings menu). Adjustable in steps of 500 ms. Up to 1 hour.
   ***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.
-{{::basic_tab_overview.png?direct&600|}}+ 
 +<wrap em>Starting from 4.1 fw there are extra functions:</wrap> 
 +=== Read/Write mode settings === 
 + 
 +There is now a convenient function for assigning register access mode – “read / write”, “read-only”, “write-only”. There are devices for some registers of which only writing is possible, for example, the control word of some frequency converters, refrigeration controllers, etc. For these devices a custom protocol. 
 +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. 
 +{{ network:rw_mode_.png?direct&600 |}} 
 + 
 +=== 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. 
 + 
 +{{ network:save_apply.png?direct&400 |}} 
  
 ===== Value tab settings ===== ===== Value tab settings =====
Line 46: Line 70:
  
 Value tab of the register edit page is used to set the type and format of register data. These settings affect how the read binary data from the registers of the connected device are interpreted for display or recording.  Value tab of the register edit page is used to set the type and format of register data. These settings affect how the read binary data from the registers of the connected device are interpreted for display or recording. 
-{{::value_tab_full.png?direct&800|}} 
  
-=== Data type === +{{ network:value_tab_new.png?direct&600 |}} 
 + 
 +==== Data type ====
 The possible options are:  The possible options are: 
   *Bit - for reading bits of discrete inputs, outputs, single memory bit etc. However, for internal WebHMI registers bit register will occupy byte.    *Bit - for reading bits of discrete inputs, outputs, single memory bit etc. However, for internal WebHMI registers bit register will occupy byte. 
Line 54: Line 79:
   *Double word - reading in double words. For double words there is an option to change normal word order to reverse:   *Double word - reading in double words. For double words there is an option to change normal word order to reverse:
  
-{{::revers_order_for_dw.png?direct&500|}}+{{network:revers_order_for_dw.png?direct&500|}}
  
   *Unix time - format used in PHP, is set as Y-m-d H:i:s, e.g., to display the date as day - month - year (DD-MM-YYYY), you set format string like this d-m-Y.     *Unix time - format used in PHP, is set as Y-m-d H:i:s, e.g., to display the date as day - month - year (DD-MM-YYYY), you set format string like this d-m-Y.  
   *String - the system will treat data in the register as string data. Intended mainly to use with internal Sxx registers.     *String - the system will treat data in the register as string data. Intended mainly to use with internal Sxx registers.  
  
-=== Value format ===+==== Value format ====
 Specifies the format of the read data. Possible options are: Specifies the format of the read data. Possible options are:
   *Unsigned integer    *Unsigned integer 
Line 70: Line 95:
   *Singned Floating Point 24 bit(such format is used in OWEN devices e.g.)    *Singned Floating Point 24 bit(such format is used in OWEN devices e.g.) 
  
-=== Bit mask ===+==== Bit mask ====
 Bit mask allows to conviniently check the state of individual bits in a source register.  Bit mask allows to conviniently check the state of individual bits in a source register. 
 When setting the bitmask to the register, the value from the register will be compared with the sum of corresponding weights 2^p (p - bit position, starting from 0) of the selected bits.  When setting the bitmask to the register, the value from the register will be compared with the sum of corresponding weights 2^p (p - bit position, starting from 0) of the selected bits. 
  
-{{::bit_mask_1.png?direct&600|}}+{{network:bit_mask_1.png?direct&600|}}
  
 In the above picture 2 highest bits are selected, so when there is a value greater or equal to 128 (2^7) + 64 (2^6) = 192 in the source register, WebHMI's copy of this register will have 3. Usually this feature is used to check only one bit, so WebHMI register has either 0 or 1 value clearly indicating if certain bit in the source register is reset or set.  In the above picture 2 highest bits are selected, so when there is a value greater or equal to 128 (2^7) + 64 (2^6) = 192 in the source register, WebHMI's copy of this register will have 3. Usually this feature is used to check only one bit, so WebHMI register has either 0 or 1 value clearly indicating if certain bit in the source register is reset or set. 
Line 80: Line 105:
 But sometimes it is neccessary to write a defined mask (group of bits) to the end device. In this case remember how the number in WebHMI register is obtain. E.g. to set 7th and 6th bit (started from 0) in the source register, 3 value has to be written in WebHMI register. Or if 7th and zero bits were checked in the mask, 129 would have to be written to set these bits. But sometimes it is neccessary to write a defined mask (group of bits) to the end device. In this case remember how the number in WebHMI register is obtain. E.g. to set 7th and 6th bit (started from 0) in the source register, 3 value has to be written in WebHMI register. Or if 7th and zero bits were checked in the mask, 129 would have to be written to set these bits.
  
-=== Delta format ===+==== Delta format ====
 Allows you to convert register data into increment or derivative.  Allows you to convert register data into increment or derivative. 
-{{::delta_format.png?direct&600|}}+{{network:delta_format.png?direct&600|}}
  
 In the first case (delta value), the register will be equal to the difference of the current subtracted value and the previous one. In the second (Delta value / Delta time) - delta value, divided by the time between polls, i.e. Derivative with respect to time. In the first case (delta value), the register will be equal to the difference of the current subtracted value and the previous one. In the second (Delta value / Delta time) - delta value, divided by the time between polls, i.e. Derivative with respect to time.
  
-=== Display as time duration ===+==== Display as time duration ====
 Show the number in seconds in the format of the length of the time interval (hours, days, etc.). The format is useful, for example, when displaying the duration of events. Show the number in seconds in the format of the length of the time interval (hours, days, etc.). The format is useful, for example, when displaying the duration of events.
  
-=== Dictionary ===+==== Dictionary ==== 
 +{{ network:menu-icon-dictionaries.png?nolink&40|}} 
 Contains the enumeration of pairs 'value, text word(s)', when you select a dictionary for the register, the values ​​read from the device are compared with the data of the dictionary and, if the word matches, the word corresponding to the value will be found. If there is a mismatch, the register will contain the value itself. The dictionaries are created and edited in the menu Setup -> Dictionary. Contains the enumeration of pairs 'value, text word(s)', when you select a dictionary for the register, the values ​​read from the device are compared with the data of the dictionary and, if the word matches, the word corresponding to the value will be found. If there is a mismatch, the register will contain the value itself. The dictionaries are created and edited in the menu Setup -> Dictionary.
-{{::dictionary.png?direct&800|}} 
  
-If third element in a row is set (e.g. "1, ON, client:dashboards.divider.on"), Level2 cloud system can interpret it like a tag and use its own dictionary with multilanguage support. +{{ network:dict_menu_entry_fw40.png?direct&600 |}}
  
-=== Units of measurement ===+{{ network:dict_example.png?direct&600 |}} 
 + 
 +<WRAP center round info 60%> 
 +If third element in a row is set (e.g. ''1, ON, client:dashboards.divider.on''), Level2 cloud system can interpret it like a tag and use its own dictionary with multilanguage support.  
 +</WRAP> 
 + 
 + 
 +==== Units of measurement ====
 Indication of engineering units for the register data. The string specified in the field will be displayed after the text string with the register value on dashboards.  Indication of engineering units for the register data. The string specified in the field will be displayed after the text string with the register value on dashboards. 
  
-=== Value Calculations ===+==== Value Calculations ====
 Show the result of the formula: Show the result of the formula:
 result = value_read х **multiplier** + **shift value** result = value_read х **multiplier** + **shift value**
 Scaling value with offset in the register to convert raw value from ADC to engineering units. The result is shown with the set **precision**. Scaling value with offset in the register to convert raw value from ADC to engineering units. The result is shown with the set **precision**.
-=== Min/Max Allowed Value For Operator === +==== Min/Max Allowed Value For Operator ==== 
 These fields allow you to limit the min. and max. possible value for the register, which can be changed by the user from the dashboard. These fields allow you to limit the min. and max. possible value for the register, which can be changed by the user from the dashboard.
-=== Min/Max Reasonable Value ===+==== Min/Max Reasonable Value ====
 These fields allow to designate a zone of unreliable values ​​of the register, thus it is possible to judge the sensor failure. When reading the value outside the zone, a nil will be written to the register, which in turn can be defined as a 'failed state'.  These fields allow to designate a zone of unreliable values ​​of the register, thus it is possible to judge the sensor failure. When reading the value outside the zone, a nil will be written to the register, which in turn can be defined as a 'failed state'. 
  
Line 114: Line 147:
 === Graph data setup === === Graph data setup ===
 Simplest way is to set up register write at regular intervals of time and view them on graphs. Then it is enough to enable this option, select color and choose time intervals: Simplest way is to set up register write at regular intervals of time and view them on graphs. Then it is enough to enable this option, select color and choose time intervals:
-{{::setup_only_graph_data.png?direct&800|}}+ 
 +| {{ network:setup_only_graph_data.png?direct&600 |}} | 
  
 This method suitable for slowly changing parameters like temperature, pressure, humidity etc. which are the most typical parameters in a system monitored with WebHMI.  This method suitable for slowly changing parameters like temperature, pressure, humidity etc. which are the most typical parameters in a system monitored with WebHMI. 
 But sometimes there is a need to track values more precisely, e.g. to view signal transitions, rising or falling edges of the discrete signals etc. Then there is an option to use log data.  But sometimes there is a need to track values more precisely, e.g. to view signal transitions, rising or falling edges of the discrete signals etc. Then there is an option to use log data. 
  
-=== Writing registers to the log === +=== Writing registers to the log ===
 In this section 'Log' means a separate part of a database which saves register values and: In this section 'Log' means a separate part of a database which saves register values and:
   *it can be a source of data for graphs   *it can be a source of data for graphs
   *has special analytic tool to view when and how register changed. After selecting the option 'Enable Log', you can track register changes in the menu item Analytics / Registers Log.    *has special analytic tool to view when and how register changed. After selecting the option 'Enable Log', you can track register changes in the menu item Analytics / Registers Log. 
-{{::reg_value_link.png?direct&200|}}+{{ network:reg_value_link.png?direct&200 |}}
  
-{{::log_fields2.png?direct&600|}}+== Adjusting logging intensity == 
 + 
 +{{ network:log_fields2.png?direct |}}
   ***Change tolerance** -'Tolerance' (absolute value or %) is the difference between new and previous register value, , if exceeded, its value will be written to the log. If the field is left blank, the record will occur upon any change. The recording frequency will be determined by the settings of the following items.   ***Change tolerance** -'Tolerance' (absolute value or %) is the difference between new and previous register value, , if exceeded, its value will be written to the log. If the field is left blank, the record will occur upon any change. The recording frequency will be determined by the settings of the following items.
   ***Min log interval** - serves as a filter for data, limiting recording frequency to this interval, so that time between two records will not exceed this interval   ***Min log interval** - serves as a filter for data, limiting recording frequency to this interval, so that time between two records will not exceed this interval
Line 131: Line 168:
   ***Max graph interval** - Log data can be a source for historical graphs (see register settings for recording on the graph below), then if there was no data within the specified interval, the graph will have a corresponding gap.   ***Max graph interval** - Log data can be a source for historical graphs (see register settings for recording on the graph below), then if there was no data within the specified interval, the graph will have a corresponding gap.
  
-  WARNING! Leaving 'Change tolerance' field empty will cause register write at ANY change. There is always some noise in  +<WRAP center round important 60%> 
-  ADC signal, so every WebHMI scan there will be writes to database. If there are many such registers this will  +WARNING! Leaving 'Change tolerance' field empty will cause register write at ANY change. There is always some  
-  affect system perfomance. Use log settings carefully and adequate to register type +noise in ADC signal, so every WebHMI scan there will be writes to database. If there are many such registers this  
 +will affect system perfomance. Use log settings carefully and adequate to register type  
 +</WRAP> 
 **Send log data to Level2 system**  - allows sending log and graph data to level2 **Send log data to Level2 system**  - allows sending log and graph data to level2
 +
 +=== Register's Log analytics tool ===
 +After you set up log options for the register, a special tool will be available. Plese refer to the [[registers_log?s[]=log|following]] article.
 +
 +
 +
  
 ===== Resources tab ===== ===== Resources tab =====
Line 140: Line 186:
 ---- ----
  
-Selection allows to send register value as a resource meter reading to Level2 cloud system and then generatate resource consumption reports.  +Selection allows to send register value as a resource meter. There are special tools in [[resource_local_tool |WebHMI]] & [[level2:setup_resource_meters_and_resources_consumption_analysis  | Level2]] cloud system to generatate resource consumption reports.  
-{{::resources_.png?direct&600|}}+ 
 +{{ network:resource_property.png?nolink |}}
  
 ===== States tab ===== ===== States tab =====
Line 164: Line 211:
 Here an example of static settings, min. and max. are constants: Here an example of static settings, min. and max. are constants:
  
-{{static_state_2.png?500}}+{{ network:dis_state_example_.png?direct&600 |}}
  
 With dynamic state settings end points of range are floating (//Delta// values are constants which are added or subtracted to dynamic margins): With dynamic state settings end points of range are floating (//Delta// values are constants which are added or subtracted to dynamic margins):
  
-{{dynamic_state_example.png?600}}+{{ network:dyn_alert_state_.png?direct&600 |}}
  
 All states have identical settings. All states have identical settings.
  
-===== Alerts ===== 
  
----- 
- 
-This tab allows to define alerts that will occur when certain bits of the register is set. See more about them [[Alerts | here]] 
-{{::setup_alerts.png?direct&600|}} 
  
 ===== Cross reference ===== ===== Cross reference =====
Line 185: Line 227:
 To overview places where the register is used.  To overview places where the register is used. 
  
-{{::x-ref.png?direct&800|}}+{{ network:x-ref.png?direct&600 |}}
  
-===== Working with a list of connections and registers=====+====== Managing register list ======
  
 ---- ----
 The list of registers is multi-level, when you minimize the list with the **>** signs, only the list of connections  and categories is displayed.  The list of registers is multi-level, when you minimize the list with the **>** signs, only the list of connections  and categories is displayed. 
  
-{{list_overview2.png}}+{{ network:list_overview2.png?direct&800 }}
  
 Format of the register list: Format of the register list:
Line 198: Line 240:
   ***ID** - A unique register number in the project.   ***ID** - A unique register number in the project.
   ***Title** - Name of the connection / register or the category.    ***Title** - Name of the connection / register or the category. 
-{{::category_example.png?direct&500|}}+ 
 +{{ network:category_example.png?direct&500 |}}
  
   ***Interval** - polling interval for the register   ***Interval** - polling interval for the register
Line 213: Line 256:
   ***Edit, Delete, Clone** buttons - corresponds to editing, deleting or cloning register(connection).   ***Edit, Delete, Clone** buttons - corresponds to editing, deleting or cloning register(connection).
  
-=== Group operations ===  +===== Group operations =====
-== Working with selections ==  +
-When the cursor hovers over the connection, a checkbox appears to the right of it for selecting or deselecting all registers in the connection. +
  
-{{reg_list_checkboxes.png}}+==== Working with selections ====
  
-There are some group operations inside **Tools** sub-menu for selected register - see below. +When the cursor hovers over the connection name, a checkbox appears to the right of it for selecting or deselecting registers in this connection. Only the visible register will be selected, which are not folded in the categories. To select all register you have to expand all categories inside the connection. 
  
-{{::reg_group_ops.png?direct&800|}}+{{ network:selection_options_.png?direct&600 |}}
  
 +There are some group operations inside **Tools** sub-menu for selected register - see below. 
 +
 +{{ network:tools_drop_down_.png?direct&600 |}}
 +  ***Import registers** - import registers from an external *.csv file 
   ***Export registers** - export selected register in a *.csv file to have a template or make some bulk modification using convenient spreadsheet editor   ***Export registers** - export selected register in a *.csv file to have a template or make some bulk modification using convenient spreadsheet editor
-  ***Disable** - disable polling of the selected register +  ***Import registers values** - updated the values of the registers from the external file or stored on the device 
-  ***Enable** - enable polling of the selected register +  ***Export registers values** - stores the values of the selected registers in the external file 
-  ***Delete** - delete selected register +  ***Store on device** - stores the values of the selected registers on the local storage
-  ***Change connection** - move selected register to another connection or category+
  
-== Importing registers == +**Add device** entry is for adding a built-in device profile. Please refer to [[connections#add_preset_device_connections| this]]. 
 + 
 +==== Importing registers ====
 **Import registers** makes reverse to export operation with csv - file containing prepared list of register. **Import registers** makes reverse to export operation with csv - file containing prepared list of register.
-{{::importregs.png?direct&600|}}+ 
 +{{ network:import_register_dialog_.png?direct&600 |}}
  
   ***Move to connection** - Allows you to use the connection ID (ID) from the csv file OR put registers in an existing connection.   ***Move to connection** - Allows you to use the connection ID (ID) from the csv file OR put registers in an existing connection.
-{{::move_to_conn_list.png?direct&500|}}+{{  network:move_to_conn_list.png?direct |}}
   ***Overwrite existent registers** - If the option is selected, if there are already registers with the given ID when importing the list in the project, they will be overwritten, otherwise registers with matching IDs from the list will receive new IDs.   ***Overwrite existent registers** - If the option is selected, if there are already registers with the given ID when importing the list in the project, they will be overwritten, otherwise registers with matching IDs from the list will receive new IDs.
  
-== Changing order of reading connections == + 
 +==== Bulk operations ==== 
 +These operations are also made on selections sets. 
 + 
 +{{ network:bulk_only_selected.png?direct&200 |}} 
 + 
 +=== Edit === 
 +With this you can edit same properties over the register selection set.  
 + 
 +{{ network:bulk_edit_basic.png?direct&600 |}} 
 + 
 +=== Disable, Enable, Delete === 
 +Makes respective action over the selected set of registers. 
 + 
 +=== Change connection=== 
 + 
 +Move selected register to another connection or category. 
 + 
 +{{ network:change_category_.png?direct&600 |}} 
 + 
 + 
 + 
 +===== Other tools ===== 
 +==== Changing order of reading connections ====
 The order of reading connections can differ from the order in which they are shown in Connection / Register list. Some serial devices may not "like" co-existing with certain devices in adjacent polls. With this tool you can sort the devices in the polling list. The order of reading connections can differ from the order in which they are shown in Connection / Register list. Some serial devices may not "like" co-existing with certain devices in adjacent polls. With this tool you can sort the devices in the polling list.
-{{::setup_plc_order.png?direct&800|}} 
  
-== Internal register map ==+{{ network:setup_plc_order.png?direct&600 |}} 
 + 
 +The communication will work from the list's top to the bottom. 
 + 
 +==== Internal register map ====
 With this tool you can make a overview of current memory map of the internal WebHMI registers.  With this tool you can make a overview of current memory map of the internal WebHMI registers. 
  
-{{register_map.png}}+{{ network:register_map.png?direct&600 }}
  
 Sometimes after intensive work with bulk import and export operation due to errors made during edition some register might be placed into wrong addresses and cause overlapping. (shown red in the above picture) Sometimes after intensive work with bulk import and export operation due to errors made during edition some register might be placed into wrong addresses and cause overlapping. (shown red in the above picture)
Line 250: Line 323:
 Another possible use for map is to quickly find some internal register in a list, using browser hotkey F3 or Crtl-F. And quickly follow the link to view register's settings. Another possible use for map is to quickly find some internal register in a list, using browser hotkey F3 or Crtl-F. And quickly follow the link to view register's settings.
  
 +==== Custom protocols ==== 
 +Please refer to this [[custom_protocols?s[]=custom | article]].
  
registers.1581433674.txt.gz · Last modified: 2020/02/11 15:07 by emozolyak
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki