Differences

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

--- en:sw:01-mervis:data-source-hidden [2023/12/18 09:44]
zrusek
+++ en:sw:01-mervis:data-source-hidden [2023/12/20 11:40] (current)
avsetula [Data source]
@@ Line 17: / Line 17: @@
 This solution is suitable for use where it is necessary to connect several previously separate solutions that have been created either by the interaction of several programmers or by splitting an already too large assembly.
-The data source can be used for communication via SSCP protocol, webserver or Mervis SCADA.
 </WRAP>
 </WRAP>
 <WRAP center round important 90%>
-Before proceeding, it is advisable to have the solution in [[creating-new-project-hidden#prepnuti_do_plneho_modu|Full mode]].
+It is recommended to have the solution in [[creating-new-project-hidden#switching_to_full_mode|Full mode]] before continue.
 </WRAP>
+===== Usage =====
+<html><span class="kbBlueText">SSCP communication</span></html> \\
+Whatever the reason for using the data source, the SSCP protocol can also be used for data exchange between PLCs. More information can be found in the separate article [[multiple-unipi-through-sscp-hidden|]].
+----
+<html><span class="kbBlueText">SCADA</span></html> \\
+Thanks to the data source, adding PLCs to Mervis SCADA is possible without merging into one large solution. This is useful especially to keep clarity, logical division or if each PLC is managed/programmed by a different programmer. /*This use is described in detail in the [[separate-scada-solution-hidden|]] article.*/
+----
+<html><span class="kbBlueText">Webserver</span></html> \\
+The connection of the data source to the local web HMI, which is created as a webserver terminal, is possible in a similar way to the PLC. In this way, it is possible to display information from a PLC from another solution in one interface. Further information can be found in a separate [[creating-external-hmi-hidden|]] article.
 ===== Adding a data source to the solution =====
-Adding a data source to the solution is done by selecting the **System** line at the top of the left panel of the solution, right-clicking and selecting **Add Data Source** from the context menu.
+Adding a data source to the solution is done by selecting the **System** line at the top of the left solution panel, right-clicking and selecting **Add Data Source** from the context menu.
 {{ :en:sw:01-mervis:data-source:data_source_01_add_source.png?direct |}}
@@ Line 39: / Line 59: @@
 ==== Names ====
-It is almost impossible to identify the PLC used in the data source, so it is advisable to set a descriptive name for the data source and include information about the source assembly (name, version, compile date, etc.) in a note. Both can be set in the properties in the right panel. In the sample solution the data source was named after the source PLC (Axon S105).
+It is quite difficult to identify the PLC connected to the solution as a data source, so it is recommended to set a descriptive name for the data source and include details about the source solution (name, version, compile date, etc.) in a note. Both can be set in the data source properties in the right panel. In the example, the data source was named according to the source PLC (Axon S105).
 {{ :en:sw:01-mervis:data-source:data_source_03_change_name.png?direct |}}
 ==== Setting properties ====
-For each data source, you must define SSCP parameters for communication, which vary by application.
+For each data source it is necessary to define SSCP communication parameters that depend on the application.
 ----
@@ Line 51: / Line 72: @@
 <html><span class="kbBlueText">Local</span></html>
-Local use means the connection of the PLC on the same local area network (LAN). Locally, the data source can be used for [[multiple-unipi-through-sscp-hidden|communication via SSCP protocol]], or for connection to [[creating-external-hmi-hidden|external web terminal]]. On the other hand, a locally defined data source cannot be used for a SCADA terminal because the SCADA server is not running on the local network but in the cloud.
+For local communication, all PLCs must be on the same local area network (LAN). Locally, the data source can be used for [[multiple-unipi-through-sscp-hidden|data exchange via the SSCP protocol]] or for connection to an [[creating-external-hmi-hidden|external web terminal]]. However, a locally defined data source cannot be used for a SCADA terminal because the SCADA server is not running on the local network but in the cloud.
 For local communication, the IP address and a few other parameters available in the source solution are sufficient.
@@ Line 64: / Line 85: @@
 <html><span class="kbBlueText">Proxy</span></html>
-Connecting a data source is also possible via [[connecting-to-unipi-via-mervis-proxy-hidden|Mervis Proxy]]. Connecting via proxy is ideal for merging [[#|multiple PLCs into one SCADA project]], or for exchanging information via SSCP protocol in a large facility where individual PLCs are either on separate networks or connected via [[lte-configuration-hidden|LTE network]].
+Connecting a data source is also possible via [[connecting-to-unipi-via-mervis-proxy-hidden|Mervis Proxy]]. The proxy connection is ideal for connecting to SCADA, or for exchanging data via SSCP protocol in a large site where individual PLCs are either on separate networks or connected via [[lte-configuration-hidden|LTE]].
 <WRAP center round important 90%>
@@ Line 73: / Line 94: @@
   * **Target address**: proxy.unipi.technology
   * **TCP port**: 12348 (12349 for SSL)
-  * **Certificate validation**: for SSL only, details [[ssl-certification-validation-hidden|here]]
+  * **Certificate validation**: optional for SSL, details [[ssl-certification-validation-hidden|here]]
   * **SSCP address**: mostly 1
 {{ :en:sw:01-mervis:data-source:data_source_05_proxy_parameters.png?direct |}}
 ==== .exs file ====
-In general, an .exs file is an executable copy (Shark Executable Image) of a project in the Mervis IDE. In this case we can say that it is the definition of all variables that are available in the PLC (inputs, outputs, in the program). This file is generated among the solution files in the **bin** directory, every time the assembly is compiled.
+In general, an .exs file is an executable image (Shark Executable Image). In this case it can be said that it is a definition of all variables that are available in a PLC (inputs, outputs, in the program). This file is generated together with the solution files in the **bin** directory, every time the solution is compiled.
-First you need to select the data source in the left panel of the solution, which will display the data source properties in the right panel. In the properties, the *.exs file from the selected assembly is selected for the "Path to executable image" parameter:
+First, it is necessary to select the data source in the left panel of the solution to display the data source properties in the right panel. In the properties, the *.exs file from the chosen solution is selected for the "Executable Image Path" parameter:
 {{ :en:sw:01-mervis:data-source:data_source_06_exs_file.png?direct |}}
 <WRAP center round important 90%>
-**WARNING!** When moving solution  folders, it is necessary to take extra care not to disconnect the *.exs file, or take this into account and create the link again. Otherwise, you will not be able to compile the report or work with the data source variables.
+**WARNING!** When moving solution folders, take extra caution and reattach the *.exs file if the path is unlinked. Otherwise, you will not be able to compile the solution or use the data source variables.
 </WRAP>
-===== Usage =====
-==== SSCP communication ====
-Whatever the reason for using the data source, the SSCP protocol can also be used for data exchange between PLCs. More information can be found in the separate article [[multiple-unipi-through-sscp-hidden|]].
-==== SCADA ====
-Adding PLCs to Mervis SCADA is possible thanks to the data source without having to merge them into one large assembly. This is especially advantageous for maintaining clarity, logical partitioning, or if each PLC is managed/programmed by a different programmer. This use is explained in detail in [[user:zrusek:029-merging-few-projects-under-one-mervis-scada|]].
-==== Webserver ====
-It is possible to connect a data source similar to a PLC to a local web HMI that is created as a webserver terminal and display information from this PLC from another report. Further information can be found in the separate article [[creating-external-hmi-hidden|]].