Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseSCADA/Tutorials/Tutorial01"

Line 56: Line 56:
  
 
[[File:Project-with-output-files.png|center|thumb|240px|Figure 4: Generate configuration output files]]
 
[[File:Project-with-output-files.png|center|thumb|240px|Figure 4: Generate configuration output files]]
 +
 +
 +
'''NOTE:''' If you have problems with this step you probably have missing some plugin installation.
  
  

Revision as of 16:35, 5 April 2015

Tutorial 1 - Running a minimal master server configuration

Objective

In this tutorial will get up an running with a minimal server configuration so you can connect to it using the ESAC (Eclipse Scada Admin Client).

You can get the full source code for this configuration project cloning the following repository https://github.com/GabrielNicolasAvellaneda/org.eclipse.scada.tutorial01.configuration


Prerequisites

You will need to have an Eclipse IDE with all the Eclipse Scada plugins installed. Also is useful to have some OpenScada plugins installed.


Step 1 - Create a new Server Configuration Project

We will create a minimal master server configuration that will generate different values so we can use the ESAC to monitor and change some DataItem values.

For this, we will use the Eclipse Scada Configuration Project type template that comes with the Eclipse Scada Plugin IDE.

Create a new Eclipse Scada Project by clicking on File / New / Other / Eclipse Scada Configuration Project

Figure 1: Create new Eclipse Scada Configuration Project


Give it a Project Name as for example org.eclipse.scada.tutorial01.configuration and then click Finish.

Figure 2: Project Name


You will end up with the following file structure

Figure 3: Project files


For now, the most import file are:

world.escm: Component Model file: Here you expose a data structure with the variables for your system. This is a logical model of your system. Your client application will see this structure when it connects to the master, so this file is very important.

world.esim Infrastructure Model file: Here you define where your services will run. This is the actual topology for your services.

productive.recipe This is a special file that generates the Eclipse Scada configuration based on the content of world.escm, wrold.esim, etc.


Step 2 - Generate the configuration files from this default configuration

Right click on productive.recipe file and select menu option Eclipse Scada Configuration / Run Production (default)

Figure 4: Generate configuration output files


This will generate an output folder with files that has the final configuration for the Eclipse Scada services. We will change this default configuration in a moment.

Figure 4: Generate configuration output files


NOTE: If you have problems with this step you probably have missing some plugin installation.


Step 3 - Running the master server

Right click on output / node1 / master / master.profile.xml and click Run As / Run Equinox Application Profile

If you see and error that says . If you see another errors, please check the your envirment and follow the plugin setup instructions.

I have checked and in my system the bundle org.h2 was already registered without any problem. But for some reason the Eclispe Scada IDE plugin can find it. So I removed the line <start>org.h2</start> and then Runned again the to generate a .launch file. Then I edited the Launch Configurations to add the missing bundle.


c:\workspace\development\tools\eclipse-4.3.3-kepler-SR2-x64\plugins\org.h2_1.3.168.v201212121212.jar

4. Connecting to the running master service with OSTC

Open the OSTC and add the connection da:ngp//localhost:2101 http://download.openscada.org/installer/ostc/I/


This is only a project you quickstart testing the different components of Eclipse Scada. On a real-world configuration you will configure drivers, exporters, hd service, etc.

Double clicking the world.esim will open the Infrastructure model editor. Where you can define your network node topology. You can define master servers, archive value servers, drivers, etc.

Double clicking the world.escm will open the Component Model Editor. There you can define the component that the services will expose.


NOTE: Every time you change the Infrastructure Model, Component Model or the Javascript files of the customization pipeline (more on this on future tutorials), you need to re run productive.recipe to generate the new configuration output files.

Back to the top