Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseSCADA/GettingStarted/SettingUpAScadaProject"
(→A simple example) |
|||
| Line 55: | Line 55: | ||
=== Creating a new SCADA project === | === Creating a new SCADA project === | ||
| + | |||
| + | Click on "New > Other ..." or just press Ctrl+N. Then select "Eclipse SCADA configuration > Configuration Project". | ||
| + | On the next page choose a name for the project and click "Finish". | ||
| + | |||
| + | This create a new configuration project, which already contains a pretty basic sample configuration. For Windows | ||
| + | this will only work partly and is also not enough. But to check if everything worked so far we can create the | ||
| + | deployable artifacts anyway. | ||
| + | |||
| + | The SCADA configuration consists basically of two files: The infrastructure model and the component model. | ||
| + | During the configuration process they get merged into one common "world" model which in turn gets transformed | ||
| + | into the various artifacts. | ||
| + | |||
| + | Additionally there are recipes which provide some influence on the generation process. The basic steps are: load model, | ||
| + | store model. Between those steps there can be added additional processing steps. Two options are implemented out of the | ||
| + | box: "Node Mapping" and "skip deployment". | ||
| + | |||
| + | The Node Mapping task provides the ability to replace the IP addresses of the nodes with different ones. This is | ||
| + | very useful to provide the same configuration for test and staging environments where just the IP addresses are | ||
| + | changed. | ||
| + | |||
| + | Skip deployment is useful during development since the creation of DEB or RPM files can take quite some time. | ||
| + | |||
| + | To actually create the deployment artifacts, right click on a recipe (e.g. productive.recipe) and select "Run Recipe" | ||
| + | from the submenu "Eclipse SCADA Configuration". A progress dialog shoud appear and after a few seconds there should be | ||
| + | a new "output" directory which contains all the deployment artifacts for each node. | ||
| + | |||
| + | === A quick and dirty example === | ||
Revision as of 07:00, 19 March 2014
Contents
Install Java & Eclipse (on Windows)
Install Java
To develop with Java you need to install the Java JDK first. This can be downloaded at: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
If you have Windows 64 bit, you should install the 64 bit version (x64), otherwise install the 32 bit version (x86).
After installation (be careful to uncheck the installation of any stupid toolbars) you should add the java bin directory to your path and create the JAVA_HOME environment variable which should point to the installation directory of the JDK.
Install Eclipse
Now you can install Eclipse. Download it from here http://www.eclipse.org/downloads/
You must install the same architecture as the Java version you installed. So if you installed the 64bit version of Java, you should use the 64bit version of Eclipse. The version on which Eclipse SCADA is based is Kepler/4.3. The current version is 4.3.2, so you should download that one (the classic version). There is no installer, so just unzip it to some directory where you want to have it.
There is a nice screencast which explains all the necessary steps in depth.
https://www.youtube.com/watch?v=NlWZJtpptwc
Install WIX
The runtime plus configuration of Eclipse SCADA is deployed on Windows as an MSI file. The configurator needs the WIX Toolset to create those files, therefor you have to install it. The downloads can be found here: http://wixtoolset.org/releases/
The installer creates all necessary environment variables, so there is no additional work to do.
Install the Eclipse SCADA IDE tooling
Next step is to install the necessary plugins which contain the actual Eclipse SCADA components. For this go to "Help > Install New Software". In the text box "Work with" just enter following URL: http://download.eclipse.org/eclipsescada/updates/nightly/0.1.0/ Then select the "Eclipse SCADA IDE" category and click on "Next". The next screen should contain all the additionally selected dependencies. Click on "Next" there as well. On the next screen accept the Licenses and click on "Finish". After the installation Eclipse requires a restart. Do that.
Additionally you can now install the additional openSCADA components. These contain the OPC and the SNMP adapters. This will be part of the 0.2.0 release of Eclipse SCADA, but for now they have to be downloaded from the openSCADA site. To install it just repeat the steps above with the URL http://repo.openscada.org/p2/org.openscada/I/1.2.0/ and select the "OpenSCADA IDE" category.
After a restart you can start with configuring the SCADA system.
A simple example
Creating a new SCADA project
Click on "New > Other ..." or just press Ctrl+N. Then select "Eclipse SCADA configuration > Configuration Project". On the next page choose a name for the project and click "Finish".
This create a new configuration project, which already contains a pretty basic sample configuration. For Windows this will only work partly and is also not enough. But to check if everything worked so far we can create the deployable artifacts anyway.
The SCADA configuration consists basically of two files: The infrastructure model and the component model. During the configuration process they get merged into one common "world" model which in turn gets transformed into the various artifacts.
Additionally there are recipes which provide some influence on the generation process. The basic steps are: load model, store model. Between those steps there can be added additional processing steps. Two options are implemented out of the box: "Node Mapping" and "skip deployment".
The Node Mapping task provides the ability to replace the IP addresses of the nodes with different ones. This is very useful to provide the same configuration for test and staging environments where just the IP addresses are changed.
Skip deployment is useful during development since the creation of DEB or RPM files can take quite some time.
To actually create the deployment artifacts, right click on a recipe (e.g. productive.recipe) and select "Run Recipe" from the submenu "Eclipse SCADA Configuration". A progress dialog shoud appear and after a few seconds there should be a new "output" directory which contains all the deployment artifacts for each node.