====== SCADA terminal in a PLC-free solution ======

<WRAP group>
<WRAP half column 100%>
#;;
<html><style>h1 {margin-bottom: 10px !important;}</style><span class="tag-skelet inline-tags">
<span class="tag-patron">Patron</span>
<span class="tag-neuron">Neuron</span>
<span class="tag-gate">Gate</span>
<span class="tag-unipi11">Unipi&nbsp1.1</span>
<span class="tag-axon">Axon</span>
</span></html>
#;;
</WRAP>
<WRAP half column 100%>
If the project exceeds a certain size, there is a need to structure the solution more, or even completely split it into several separate parts, even though it was originally advantageous to have all controllers in one solution, for example because of [[en:sw:01-mervis:multiple-unipi-through-sscp-hidden|SSCP communication]], or connection to [[en:sw:01-mervis:mervis-scada-project-hidden|SCADA]]. Another reason may be that multiple programmers are working on a single installation but with multiple PLCs.

The assemblies created by splitting one large assembly in this way can be freely linked using [[en:sw:01-mervis:data-source-hidden|Data sources]].

When splitting a solution with a SCADA terminal and multiple PLCs, it is advisable to create a separate solution for the SCADA terminal with data sources only, representing the PLCs in separate projects. Therefore, this manual describes the recommended procedure on how to create the solution and how such a solution should look like.
</WRAP>
</WRAP>


===== Solution creation =====

Create a brand new solution in Full Mode before proceeding:

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_01_full_mode.png?direct |}}

==== Creating a terminal ====

A terminal is a virtual device in the Mervis IDE that contains all the information about the SCADA project and defines which PLCs the Mervis SCADA server will communicate with and how it will connect to them.

----

First there is a need to add the terminal itself by right clicking on **System**, and selecting **Add Terminal**.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_02_add_terminal.png?direct |}}

Then select **Mervis SCADA rev. 1.0** from the list. Confirm by clicking **OK**

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_03_choose_scada.png?direct |}}

Now it is necessary to set the properties in the terminal to match the properties of the SCADA project that was created in [[https://www.unipi.technology/cs/customer/scada/|customer portal]]. A detailed description of this setup can be found in the [[en:sw:01-mervis:mervis-scada-project-hidden?tns#creating_a_scada_terminal|Create Mervis SCADA project]] article.



==== Data source ====

<WRAP center round info 90%>
Adding and using a data source is described in detail in [[en:sw:01-mervis:data-source-hidden|separate article]].
</WRAP>

A data source is a simplified definition of a PLC used in another assembly. The basis of the definition are the communication parameters for connection to the PLC (local or proxy) and the *.exs file containing the definition of variables.

The prerequisite for creating a separate assembly for a terminal is the connection of 3 or more PLCs from separate assemblies.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_04_three_data_sources.png?direct |}}


=== Assigning Data Source to the Terminal ===

After expanding the terminal by using the arrow to the left of the name and clicking on the terminal channel **terminalChannel** right click and then select **Assign Device** from the context menu.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_05_add_device.png?direct |}}

A dialog box opens with a list of data sources (or PLCs) that are available in the IDE project. Mark the desired data sources and click **OK** to assign them to a terminal.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_06_choose_device.png?direct |}}


==== Creating a data point table and SCADA schema ====

Since the solution is created in full mode, before creating the table or schema, an HMI project must be created. Then, in this project the table and, if applicable, the schema can be created or copied from another solution. 

<WRAP center round important 90%>
When **copying a table/schema from another solution** it is necessary to remap variables!
</WRAP>

----

<html><span class="kbBlueText">1. Adding a new HMI project</span></html>

To create a new HMI project, right-click on the **HMI Projects** row in the Report and select **Add New HMI Project** from the context menu.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_07_new_hmi.png?direct |}}

Dialog box opens in which must be specified the name and location of the new HMI project. It is **strongly recommended** to keep the location in the project directory.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_08_hmi_name.png?direct |}}

----

<html><span class="kbBlueText">2. Creating a table/schema of data points</span></html>

The data point table or schema is created by right-clicking on the HMI project and selecting **Add new HMI template** from the context menu and selecting the appropriate parameters.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_09_hmi_schema.png?direct |}}

<WRAP center round info 90%>
Setting up a table or schema and mapping data points is described in separate articles ([[[en:sw:01-mervis:mervis-scada-project-hidden#datapoint_table_for_the_mervis_scada|table]]/[[en:sw:01-mervis:creating-scada-graphic-hidden|schema]]).
</WRAP>
 

----

<html><span class="kbBlueText">3. Table and SCADA scheme assignment</span></html>

After creation of table/schema, the templates must be assigned to a terminal. Click on the terminal to display its properties in the right column, where the items **Data Point Table** and **Schemes** are located. Data point table or schema created in the previous steps must be assigned to these items.

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_10_map_schema.png?direct |}}


===== Outcome and risks =====

<WRAP center round important 90%>
Extra care must be taken when making changes to the project, especially when making changes to individual data sources, where the .exs file will be changed and possible disconnection from the target PLC will occur. When update happens on a data source or project moves, it is necessary to compile the target project and then upload the updated SCADA definition in the Mervis SCADA web interface.
</WRAP>

----

As a sample project, a simple report was created using three data sources representing Unipi PLCs from other solutions and a SCADA terminal with a data point table. The table contains three counter values, one from each PLC. 

The resulting solution looks as follows:

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_11_solution.png?direct |}}

Data points table containing counters of individual PLCs:

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_12_datapoint_table.png?direct |}}

The resulting appearance of the table in the SCADA interface:

{{ :en:sw:01-mervis:separate-scada-solution:more_projects_scada_13_example_scada_table.png?direct |}}