Difference between revisions of "EclipseSCADA/GettingStarted/ESAC"

Revision as of 06:54, 25 February 2014

The Eclipse SCADA Administration Client (ESAC)

Download the "Eclipse SCADA Administration Client" (http://www.eclipse.org/eclipsescada/downloads.html). The Client is available as a simple zip file for Windows, Linux and Mac. Additionally for Windows there is a MSI installer available.

The ESAC is primarily used for two things: Peeking into a running system, to browse tags/items, and to deploy configurations to a running Equinox based SCADA application. You can also use it to show the historical data and browse alarms and events.

Connections

Eclipse SCADA supports 3 basic (home grown) protocols:

1. net/gmpp (the old protocol)
2. ngp (the current protocol)
3. sfp (in development, compact, less features but efficiently to implement, supports only DA)

Generally the standard protocol which is used throughout Eclipse SCADA is ngp. It supports flexible timeouts, streaming compression, ssl, callbacks.

On top of the basic protocol there exist 4 variants:

1. da (Data Acquistion)
2. ae (Alarms & Events)
3. hd (Historical Data)
4. ca (Configuration Administrator)

The reason for that is that it reduces the surface of the API, so you wouldn't need to have to include all ae/hd/ca functionality if you are only interested in DA. The consequence of it is, that each variant needs its own port. Maybe in the future there will be a wrapper that supports all variants over one connection, but for now that doesn't exist.

To connect to a Eclipse SCADA Server, you need to connect using an Eclipse SCADA URL. This takes the following shape:

 [da|ae|hd|ca]:[net|ngp|sfp]://[[<username>]:<password>@]<host>:<port>[?<option>=<option value>[&<option>=<option value>]]

Examples:

 da:ngp://localhost:2101
 da:ngp://demo.openscada.org:2101
 ca:ngp://myuser:mypassword@scada.example.org:2401?timeout=240000

All ports can be chosen freely, but within the project we use defined standard ports.

URL Options are documented here.