Differences

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

--- connections [2020/06/02 15:15] – [Adding built-in device connections] emozolyak
+++ connections [2020/08/06 16:30] – Add device search optimisation atolstov
@@ Line 16: / Line 16: @@
   ***Serial number** - for documenting purposes, to track physical device used in this connection
   ***SKU** - for documenting purposes, manufacturer model number to identify the type of device (Stock Keeping Unit)
-  ***Category** - grouping connections into logical groups, for organising a large list of devices.
+  ***Category** - grouping connections into logical groups, for organizing a large list of devices.
   ***Device Model** - type of device and its protocol to connect to
   ***Protocol** - more specific protocol subtype, if there are many options (like RTU/ASCII/TCP etc. )
@@ Line 23: / Line 23: @@
 The rest settings **(2)** of **Basic tab** may vary depending on type of protocol (below those ones for Modbus TCP):
   ***Device address** - the address of the connected device on the network
-  ***Address base (offset)** - to automatically shift the register address before apllying it to the transmission telegram (for Modbus family protocols).
+  ***Address base (offset)** - to automatically shift the register address before applying it to the transmission telegram (for Modbus family protocols).
   ***TCP port*** - TCP port used for the protocol
   ***Unit identificator**  - slave Id in the Modbus network. This number passes through Modbus TCP gateways to serial bus.
@@ Line 53: / Line 53: @@
   -**Mode** - //Normal// mode is when WebHMI polls the device. //Virtual UART// mode is when WebHMI activates special driver to enable external access to that serial port via TCP socket. Please refer for more details to [[Virtual UART]] function page.
-===== Adding built-in device connections =====
+===== Add preset device connections =====
+Beginning with 4.0.4161 there is a new function ''Add device'' designed to facilitate connection between WebHMI, when using a 7bit(tm) devices.
-There are built-in connections you can add in one-click from the register list tree.
+There are preset connections you can add in one-click from the register list tree.
 {{ ::add_conn_new_2.png?direct&400 |}}
+There a few devices preset.
+{{ :conn:add:15.png?direct&400 |}}
+After the creation will be done, you need to edit connection to finish it creation.
+{{ :conn:add:5_on.png?direct&400 |}}
+After that, it will be ready to turn it on.
+{{ :conn:add:6_works.png?direct&400 |}}
+There are also a diagnostic solution for your project included. \\
+It is called "WebHMI Health registers".
-This feature is available since the fw version of 4.0.4161. If some device can be nested inside another (e.g. 7bit AipPoint sensor inside 7bit AirGate MQTT connection or WebHMI Health registers inside other WebHMI internal connection) the option to create a category in that connection will be offered.
+{{ :conn:add:10_health_reg.png?direct&800 |}}
+ It is a bunch of registers, which intended to show the status of WebHMI.
+{{ :conn:add:11_hr_works.png?direct&800 |}}
+It is also logging enabled by default to make it possible create a graph with average load or input voltage for example.
+{{ :conn:add:12.png?direct&800 |}}
+{{ :conn:add:13.png?direct&800 |}}
+If some device can be nested inside another (e.g. 7bit(tm) AipPoint sensor inside 7bit(tm) AirGate MQTT connection or WebHMI Health registers inside other WebHMI internal connection) the option to create a category in that connection will be offered.
 {{ ::add_device_1.png?direct&400 |}}