{"id":3603,"date":"2019-03-25T17:45:05","date_gmt":"2019-03-25T20:45:05","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/setting-up-elipses-iccp-driver\/"},"modified":"2024-02-20T16:04:35","modified_gmt":"2024-02-20T19:04:35","slug":"setting-up-elipses-iccp-driver","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/setting-up-elipses-iccp-driver\/","title":{"rendered":"Setting up Elipse’s ICCP Driver."},"content":{"rendered":"
\n

The goal of this article is to illustrate ICCP driver’s basic settings, both in Server and in Client versions.<\/p>\n


\nSetting up the Driver<\/b><\/u><\/p>\n

As established by standard 60870-6, the ICCP driver needs a bilateral table set up, where parameters, variables, and data exchange permissions between hubs are established. Elipse’s ICCP driver uses a CSV (Comma Separated Values<\/i>) file to set up the client and\/or server bilateral table. The BLT files’ internal structure (ICCPClient.BLT<\/b> for the client and ICCPServer.BLT<\/b> for the server) is the following:<\/p>\n

ICCPVersionYear-ICCPVersionMonth,BLTFileFormatVersion
\n**DataSets**
\nDataSetCount
\nDataSetDeclaration <\/b>(appears DataSetCount times)
\n**DataValues**
\nDataValueCount
\nDataValueDeclaration<\/b> (appears DataValueCount times)
\n**Devices**
\nDeviceCount
\nDeviceDeclaration<\/b> (appears DeviceCount times)
\n**Messages**
\nMessageCount
\nMessageDeclaration <\/b>(appears MessageCount times)<\/span><\/p>\n

Their properties are the following:<\/p>\n

\"\"<\/div>\n

 <\/p>\n

\"\"<\/div>\n

Attached to this article are two files, ICCPServer.BLT<\/b> and ICCPClient.BLT<\/b>, which can be the foundations for creating the structure.<\/p>\n

ICCP Server<\/b><\/u><\/p>\n

After creating the ICCPServer.BLT<\/b> file (as seen above), you must access the driver settings on ICCP General<\/b> tab:<\/p>\n

\"\"<\/div>\n

To set up the driver as the Server, configure the General Profile<\/b> property as ICCP Server<\/i><\/b>. You can generate a basic BLT file from an LD (Logical Device Cache Files<\/i>) file, which is generated by Elipse’s IEC61850<\/b> driver. This functionality is required when the data read locally via IEC61850 need to be available to other hubs via ICCP. If necessary, Msg Timeout (ms)<\/b>, Local P Selector<\/b>, Local S Selector<\/b>, Local T Selector<\/b>, Local App ID<\/b> and Local AE Qualifier<\/b> properties can also be configured on this window. BLT File Path<\/b> property must be configured with the destination folder where the BLT files were created.<\/p>\n

After the configuration on ICCP General<\/b> tab, access ICCP Server<\/b> tab:<\/p>\n

\"\"<\/div>\n

On this window, configure Local Domain<\/b>, Billateral Table Name<\/b> and Billateral Table Version<\/b> properties. Local Domain<\/b> property informs the name of the local ICCP server (instance name). This name will be verified on both ends (client and server) for several operations and must be equivalent on both sides<\/b><\/u>. Billateral Table Name<\/b> and Billateral Table Version<\/b> properties will be verified by the client to ensure the application’s security (notice that this verification only happens when the client is an Elipse E3\/Power running on the same driver). From Check BLT File<\/b> option, you can check if the BLT file’s syntax is correct; if so, the following message will be displayed:<\/p>\n

\"\"<\/div>\n

The physical layer’s configuration follows the IOKit<\/b>‘s pattern: on the Server end, the physical layer must be set up as Ethernet <\/i><\/b>on Setup <\/b>tab, and the port that expects the connection must be configured on Ethernet <\/b>tab (enable Listen for connection on port…<\/b> option).<\/p>\n

Importing tags at ICCP Server<\/b><\/u><\/p>\n

Creating tags at the ICCP driver is simple, since they can be imported directly via TagBrowser. If ICCPServer.BLT<\/b> file’s syntax is right, the tags declared in the file will be available in the TagBrowser’s ICCPLocal<\/b> folder, as seen below:<\/p>\n

\"\"<\/div>\n

From there, you can drag the desired tags to the current project.<\/p>\n

ICCP Client<\/b><\/u><\/p>\n

When using ICCP Client, the ICCPClient.BLT<\/b> file can be created in two different ways. The first possibility is to create the file manually, with the same structure as ICCPServer.BLT<\/b> file. The second one is to create the file automatically. This is possible because the ICCP driver can retrieve an ICCP Server’s database online, and from there it can create a simple version of ICCPClient.BLT<\/b> file according to this database. Notice that to use this functionality, the ICCP Server must be both set up and online, thus making it possible for the ICCP Client to retrieve the database. For notes on how to work online and offline, see the next items.<\/p>\n

Regardless on how the file was created, to set up the ICCP Client you must first access the driver’s ICCP General tab:<\/p>\n

\"\"<\/div>\n

On this window, General Profile<\/b> and BLT File Path<\/b> properties’ setup is similar to ICCP Server’s, but General profile<\/b> property must be configured as ICCP Client<\/i><\/b>. BLT File Path<\/b> property must be configured with the destination folder containing ICCPClient.BLT<\/b> file.<\/p>\n

After setting up ICCP General<\/b> tab, you will need to access ICCP Client<\/b> tab, according to the image below:<\/p>\n

\"\"<\/div>\n

On this tab, you will need to set up Remote Domain<\/b>, Expected Billateral Table Name<\/b> and Expected Billateral Table Version<\/b> properties. Remote Domain<\/b> property informs the name of the remote ICCP server. This name will be verified on both ends (client and server) for several operations, and must be equivalent on both sides<\/b><\/u>. Expected Billateral Table Name<\/b> and Expected Billateral Table Version<\/b> are verified only if the server is also an Elipse E3\/Power using the same driver. Both properties will be checked to ensure the application’s security. If the ICCPClient.BLT<\/b> file was created manually, you will be able to check its syntax from Check BLT File <\/b>option.<\/p>\n

The physical layer’s configuration follows the IOKit<\/b>‘s pattern:\u00a0 on the Client end, the physical layer must be set up as Ethernet <\/i><\/b>on Setup <\/b>tab, and the IP and port where the client will connect must be configured on Ethernet <\/b>tab.<\/p>\n

Importing ICCP Client tags<\/b><\/u><\/p>\n

Tags can be imported at the ICCP Client in two different ways. If the ICCPClient.BLT<\/b> file has been created manually, the tags declared in the file will be available in ICCPRemote_Offline<\/b> folder, as seen below:<\/p>\n

\"\"<\/div>\n

If the ICCP Server’s database has been retrieved automatically, the data will be available in ICCRemote_Online<\/b> folder. When clicking on the folder, the driver will retrieve the data online and, from there, it will create the ICCPClient.BLT<\/b> file. Notice that for this to happen, the physical layer must be configured correctly and the ICCP Server must be online. If all parameters are correct, the available tags will look like this:<\/p>\n

\"\"<\/div>\n

Using Elipse’s ICCP driver as both ICCP Client and ICCP <\/b><\/u><\/p>\n

Elipse’s ICCP driver can work as both ICCP Client and ICCP Server at the same time. To do so, set up General Profile<\/b> property on ICCP General<\/b> tab as ICCP Client\/Server<\/b><\/i>, and then proceed to configure both tabs (ICCP Client<\/b> and ICCP Server<\/b>). ICCP Server’s tags will be available in ICCPLocal<\/b> folder, while ICCP Client’s tags will be available in ICCPRemoto <\/b>folders (Online and Offline). Settings for ICCPServer.BLT<\/b> and ICCPClient.BLT<\/b> files are the same as the ones mentioned on the above items. The main difference is when configuring the physical layer, which must follow these procedures:<\/p>\n