This article answers a few frequently asked questions (FAQ) about version 3.0 of Elipse E3, SCADA tool for process control and monitoring.
FAQ: I already have a hardkey for Elipse E3 version 2.5, and now I want to use version 3.0. What should I do?
The hardkey for version 3.0 is different from the hardkey for version 2.5. So, you must contact Elipse Software‘s sales department to acquire a new hardkey.
FAQ: Will the hardkey I use with version 2.5 continue working with Elipse E3 version 3.0?
Version 2.5 can support both the old hardkey model (Hasp4) and the new model (Hasp HL). Version 3.0, on the other hand, only supports the new model. So, in case your hardkey model is not Hasp HL, you must contact Elipse sales department to get a new model.
FAQ: Although I upgraded the hardkey to the new Hasp HL model, Elipse E3 still will not acknowledge the programmed copy. Why is this happening?
First, make sure you’ve programmed the hardkey for version 3.0. Then, you must also check if the product key has been properly installed before the computer is turned on. Please notice that Windows always executes the new 3.0 version as service; this means that even before there are any users logged in the system, Elipse E3 processes will already be running. If the hardkey is connected after the system starts up, it will be necessary to stop E3 Server (using the E3 Admin icon on system’s taskbar), connect the hardkey, and then start E3 Server again.
FAQ: I have an application that runs normally on version 2.5; is it compatible with version 3.0?
Elipse E3 accepts all applications that used to run on version 2.5. However, please notice that in version 3.0, all applications run on SYSTEM user account. This user’s settings may vary from system to system (for example, Windows regional settings, installed printers, etc.), and it may cause problems where this information is used. A typical problem is when you set up a printer for the local user, and yet Elipse E3 keeps using the printer set up on the server. To fix this, you can use E3 Admin’s Printer option to perform the settings directly on the server.
There is one exception that occurs with Windows Vista users: Viewer’s Disable task switching option does not work in this system. This happens because Windows Vista does not allow programs to perform that type of blocking.
FAQ: Is it possible to open screens from other applications by using the new Remote Domain feature?
You must not confuse “remote domains” with “distributed domains”. Remote Domains allow accessing databases of other Elipse E3 application, which include server tags and XObject properties. Other objects, like screens, alarms, and reports, are not supported.
FAQ: What is the difference between using Remote Domains or OPC between two E3 servers?
There are two basic differences: the communication protocol and the way data becomes available. For communication protocol, Remote Domains use REC protocol, developed by Elipse. OPC, on the other hand, communicates via DCOM, known for its performance restrictions in disconnection situations or network problems, which demands special settings to work properly. As for data availability, with OPC you can only fetch properties, unlike Remote Domains, which allows you to access objects.
FAQ: Can remote domains be set up or tested in Demo mode?
No; to do so, you will need (in builds equal to or higher than 411) to have at least a Studio hardkey to set up and test remote domains.
FAQ: Can applications be exported from Elipse SCADA and imported to Elipse E3 in Demo mode?
Exporting applications from Elipse SCADA in Demo mode is allowed. However, to import the application to Elipse E3, you will need to have an E3 Studio hardkey.
FAQ: Why does Elipse E3 run as a service?
This feature is needed in order to allow information exchange between Elipse E3 modules (E3Server/E3Server, E3Server/Studio, E3Server/Viewer) via the new REC protocol. This protocol has completely replaced DCOM protocol for version 3.0.
FAQ: Can a Viewer from version 2.5 be connected to a 3.0 server?
No, this feature has become available starting at version 3.0. After this version’s release, it will be possible to connect the Viewer from an older version to a more recent version, maintaining compatibility between versions. Notice however that the new features will not work if the Viewer’s version is older than the Server’s version.
FAQ: I have just upgraded from version 2.5 to 3.0, and the shortcuts to run the Domain stopped working. Why?
This happens because in version 2.5, the shortcuts to run the applications referred to E3 Server. From version 3.0 on, this has changed: the shortcuts now refer to E3 Admin. Changing this is very simple: you need only replace “E3Server” for “E3Admin” in the shortcut.
For example:
C:\Program Files\Elipse E3\Bin\E3Server.exe" -start
"C:\supervisory\application.dom" -viewer
Should be:
C:\Program Files\Elipse E3\Bin\E3Admin.exe" -start
"C:\supervisory\application.dom" -viewer
FAQ: When E3 Studio runs on Windows Vista, an UAC (User Account Control) warning message window is displayed. What does it mean?
This is a standard security message from Windows Vista for all programs that ask permission to run as an administrator. This is the case of E3 Studio, E3 Server, and E3 Viewer.
