Citect SCADA 2018 R2 - Cluster Definition

Hello everyone,

I'm studying to use the Citect SCADA, I created the Cluster1 before and select "Include" at column "Project" in tab "Edit" of "Topology". After clicking the save button, it disappeared and I can not find the "Cluster1" in the tab "Edit", but when I check the view by Cluster, it still is there. The picture is below. 

Now I can only create the cluster with a different name from "Cluster1" (For example ClusterA).

Can somebody help me to explain what is this and how can I find the Cluster1 to delete? I already find the information in the Citect SCADA web help, but I can not find the relevant information.

Thanks and Best Regards

Canh

Parents
  • Ok, so an Include project is a way you can structure or nest folders under a project. If you want you can put everything in a single project. But most customers use a structure, to make use of some benefits like having comms in a single project or pages/tags in different area projects. Basically you have a single "Active" project, then as many "Include Projects" as required, it can also go several levels deep. So in Citect Studio, you define that relationship via the "Projects > Includes" tab. For example, the ExampleSA project has the following includes defined:
    SA_Include
    SA_Library
    IndustrialGraphics_Include

    Then if you look at SA_Include, it includes the "Include" and "SA_Controls" projects.

    When you toggle "System Projects" view on, you will see the ExampleSA project now can be expanded to show them as nested include projects. But if it is all too daunting, just switch the System Projects view off. So you can just focus on projects you create.

    Now to confuse things even more, there is actually a project called "Include". This goes way back to when Citect was first developed. I think back in the V1.0 DOS days. This is basically a System Project that should not be modified.
Reply
  • Ok, so an Include project is a way you can structure or nest folders under a project. If you want you can put everything in a single project. But most customers use a structure, to make use of some benefits like having comms in a single project or pages/tags in different area projects. Basically you have a single "Active" project, then as many "Include Projects" as required, it can also go several levels deep. So in Citect Studio, you define that relationship via the "Projects > Includes" tab. For example, the ExampleSA project has the following includes defined:
    SA_Include
    SA_Library
    IndustrialGraphics_Include

    Then if you look at SA_Include, it includes the "Include" and "SA_Controls" projects.

    When you toggle "System Projects" view on, you will see the ExampleSA project now can be expanded to show them as nested include projects. But if it is all too daunting, just switch the System Projects view off. So you can just focus on projects you create.

    Now to confuse things even more, there is actually a project called "Include". This goes way back to when Citect was first developed. I think back in the V1.0 DOS days. This is basically a System Project that should not be modified.
Children
No Data