Differences

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

--- connections [2018/07/27 20:15] – akuzmuk
+++ connections [2018/07/27 20:25] – [Basic Info Tab] akuzmuk
@@ Line 3: / Line 3: @@
 To create a new connection use the **New Connection** button on **Registers** page.
-{{:add_conn_from_scratch.png?direct&912|}}
 {{::add_new_conn2.png?direct&912|}}
@@ Line 10: / Line 8: @@
 There are 2 ways to edit existing connection:
-{{::select_conn_to_edit.png?direct&912}}
+{{ :select_conn_to_edit.png?direct&600 |}}
 ==== Basic Info Tab ====
-After selecting a connection to edit, the page with //Basic info// tab is opened:
+After selecting a connection to edit, the page with **Basic info** tab is opened:
-{{::conn_basic_tab_review.png?direct&800|}}
+{{ :conn_basic_tab_review.png?direct&600 |}}
-The group **(1)** of setting is common for any kind of connection communication protocol:
+The group **(1)** of settings is common for any kind of communication protocol:
   ***Title** - the name of the connection that will be displayed when working with the project
-  ***Description** - explanation for role and function of the connection
+  ***Description** - user-defined description of the connection
-  ***Serial number** - for docunmenting purpose, to track physical device used in this connection
+  ***Serial number** - for documenting purposes, to track physical device used in this connection
-  ***SKU** - for documening purpose, 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 organizing a large list of devices.
+  ***Category** - grouping connections into logical groups, for organising a large list of devices.
   ***Device Model** - type of device and its protocol to connect to
-  ***Protocol** - more specific protocol indication, if there are many options (like RTU/ASCII/TCP etc. )
+  ***Protocol** - more specific protocol subtype, if there are many options (like RTU/ASCII/TCP etc. )
-  ***Script alias** - if you have the same type of devices and use scripts to process data in them, it is convenient to copy the same scripts (with the same references to the registers.) Using the connection variable name, you can choose which connection you want to use to access the register by its name in the lua script.
+  ***Script alias** - if you have the same type of devices and use scripts to process data in them, it is convenient to copy the same scripts (with the same references to the registers). Using the connection variable name, you can choose which connection you want to use to access the register by its name in the Lua script.
-The rest settings **(2)** of Basic tab may vary with different types of protocols (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
   ***Address base (offset)** - to automatically shift the register address before apllying 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.
-    ***Disable** - disables/enables communication for this connection
+  ***Disable** - disables/enables communication for this connection
-    ***Simulate device** - the ability to simulate the presence of the device in the network (simulation mode), with possibility to write and read 'virtual' registers of this device.
+  ***Simulate device** - the ability to simulate the presence of the device in the network (simulation mode), with possibility to write and read 'virtual' registers of this device.
 Please refer to specific communication protocols documentation and WebHMI application examples for more info.