Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:sw:01-mervis:data-source-hidden [2023/12/19 13:45]
avsetula [SCADA]
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. 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>​ </​WRAP>​
Line 25: Line 23:
 It is recommended to have the solution in [[creating-new-project-hidden#​switching_to_full_mode|Full mode]] before continue. It is recommended to have the solution in [[creating-new-project-hidden#​switching_to_full_mode|Full mode]] before continue.
 </​WRAP>​ </​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 =====
Line 42: Line 62:
  
 {{ :​en:​sw:​01-mervis:​data-source:​data_source_03_change_name.png?​direct |}} {{ :​en:​sw:​01-mervis:​data-source:​data_source_03_change_name.png?​direct |}}
 +
  
 ==== Setting properties ==== ==== Setting properties ====
Line 77: Line 98:
  
 {{ :​en:​sw:​01-mervis:​data-source:​data_source_05_proxy_parameters.png?​direct |}} {{ :​en:​sw:​01-mervis:​data-source:​data_source_05_proxy_parameters.png?​direct |}}
 +
  
 ==== .exs file ==== ==== .exs file ====
Line 89: Line 111:
 </​WRAP>​ </​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 ==== 
- 
-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.*/ 
- 
-==== Webserver ==== 
- 
-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.