{"id":3588,"date":"2019-03-25T17:45:01","date_gmt":"2019-03-25T20:45:01","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/communication-between-elipse-e3-and-elipse-scada-via-remoteapp-driver\/"},"modified":"2019-10-18T10:55:16","modified_gmt":"2019-10-18T13:55:16","slug":"communication-between-elipse-e3-and-elipse-scada-via-remoteapp-driver","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/communication-between-elipse-e3-and-elipse-scada-via-remoteapp-driver\/","title":{"rendered":"Communication between Elipse E3 and Elipse SCADA via RemoteApp driver."},"content":{"rendered":"
\n

Introduction<\/b><\/u><\/p>\n

In addition to communication via OPC, another type of communication provided by Elipse Software is via Elipse SCADA Remote Access<\/b> driver.<\/p>\n

Also called RemoteApp Driver, it enables communication with Elipse SCADA via Remote Applications protocol. To do so, the Elipse SCADA application must have the TCP\/IP network driver installed and set up, with an available connection.<\/p>\n

Settings<\/b><\/u><\/p>\n

At Elipse SCADA:<\/b><\/p>\n

1. Open the Organizer, select Drivers<\/b>, and then click New<\/b>. Select tcpip32.dll<\/b> file from Drivers <\/b>folder in Elipse SCADA’s installation.<\/p>\n

\"\"<\/div>\n

2. Click Set up<\/b> to open the driver’s properties window. Click it again to edit the number of IP ports where the driver will receive the connections and the maximum amount of supported connections.<\/p>\n

\"\"<\/div>\n

3. Save the changes and run the application, which should be ready to receive the connections of RemoteApp driver.
\n
\nAt RemoteApp driver (Elipse E3):<\/b><\/p>\n

1. Insert RemoteApp driver in an E3 application and open its settings window.<\/p>\n

2. On Setup <\/b>tab, select Ethernet <\/b>from Physical Layer<\/b> option; this will cause the driver to communicate via Ethernet.<\/p>\n

\"\"<\/div>\n

3. On Ethernet <\/b>tab, select TCP\/IP<\/b> from Transport <\/b>option, set up the IP of the computer where Elipse SCADA is at IP <\/b>field and the port used by the TCP\/IP network driver at Port <\/b>field.<\/p>\n

\"\"<\/div>\n

At the tags (Elipse E3):<\/b><\/p>\n

Tags are set up via their ParamDevice <\/i>and ParamItem <\/i>properties.<\/p>\n

You can also use the Tag Browser<\/b> window, which connects directly to Elipse SCADA and shows the tags available in the application at Tags <\/b>and RemoteApplications <\/b>items.<\/p>\n

\"\"<\/div>\n

Although the Tag Browser shows only the Tags <\/b>and RemoteApplications<\/b> folders, you can access any of the application’s object or property via the object’s path and name. For example, to retrieve the number of active alarms in the application, type Application.activeAlarms<\/b> at ParamItem <\/i>property.<\/p>\n

Similarly to what happens with Elipse SCADA, you don’t have to inform a tag’s complete path to find it. If a tag has a unique name in the application, that is, if no other object has the same name, you can simply inform its name. For example, if there is only one Tag001 <\/b>object in the application, you can access it via Application.Tags.Tag001<\/b>, Tags.Tag001<\/b>, or Tag001<\/b>.<\/p>\n

IMPORTANT:<\/b><\/p>\n