connections
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
connections [2020/06/02 09:08] – [Adding built-in device connections] emozolyak | connections [2020/08/07 07:39] – atolstov | ||
---|---|---|---|
Line 2: | Line 2: | ||
The connection determines which communication driver and what parameters WebHMI will use to exchange data with the equipment. The list of the connection settings and their meaning is given in this section. | The connection determines which communication driver and what parameters WebHMI will use to exchange data with the equipment. The list of the connection settings and their meaning is given in this section. | ||
- | There are 2 options to create a new connection - use the //New Connection// | + | There are 2 options to create a new connection - use the //New Connection// |
{{ :: | {{ :: | ||
Line 16: | Line 16: | ||
***Serial number** - for documenting purposes, to track physical device used in this connection | ***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) | ***SKU** - for documenting purposes, manufacturer model number to identify the type of device (Stock Keeping Unit) | ||
- | ***Category** - grouping connections into logical groups, for organising | + | ***Category** - grouping connections into logical groups, for organizing |
***Device Model** - type of device and its protocol to connect to | ***Device Model** - type of device and its protocol to connect to | ||
***Protocol** - more specific protocol subtype, if there are many options (like RTU/ | ***Protocol** - more specific protocol subtype, if there are many options (like RTU/ | ||
Line 23: | Line 23: | ||
The rest settings **(2)** of **Basic tab** may vary depending on type of protocol (below those ones for Modbus TCP): | 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 | ***Device address** - the address of the connected device on the network | ||
- | ***Address base (offset)** - to automatically shift the register address before | + | ***Address base (offset)** - to automatically shift the register address before |
***TCP port*** - TCP port used for the protocol | ***TCP port*** - TCP port used for the protocol | ||
***Unit identificator** | ***Unit identificator** | ||
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. | -**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 | + | ===== Add preset |
+ | Beginning with 4.0.4161 there is a new function '' | ||
- | There are built-in | + | There are preset |
{{ :: | {{ :: | ||
+ | There a few devices preset. | ||
+ | {{ : | ||
+ | After the creation will be done, you need to edit connection to finish it creation. | ||
+ | {{ : | ||
- | This feature | + | After that, it will be ready to turn it on. |
+ | {{ : | ||
+ | Here is a connection established and data acquired. | ||
+ | ==== Diagnostic preset registers ==== | ||
+ | There are also a diagnostic solution for your project included. \\ | ||
+ | It is called " | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | It is a bunch of registers, which intended to show the status | ||
+ | {{ : | ||
+ | It is also logging enabled by default to make it possible create a graph with average load or input voltage for example. | ||
+ | {{ : | ||
+ | {{ : | ||
+ | |||
+ | |||
+ | 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. | ||
{{ :: | {{ :: | ||
- | Don't forget to correct the default settings for network address, port etc. after adding, because the devices are | + | Don't forget to correct the default settings for network address, port etc. after adding |
- | added with default presets. | + | |
connections.txt · Last modified: 2024/02/02 08:48 by emozolyak