Introduction

IEC ICCP Client/Server Driver communicates with other ICCP Clients or Servers over Ethernet TCP/IP. Each instance of this Driver allows Clients, Servers, and Client/Server communication Profiles with other Centers.

This Driver, according to which is defined by 60870-6 standard, requires the definition of a Bilateral Table that specifies variables, parameters, and permissions for exchanging data among Centers that use TASE.2 protocol. The format, configuration, or maintenance of this table is outside the scope of this standard.

For an easy interchange of this table among different software manufacturers, IEC ICCP Client/Server Driver uses a CSV (Comma-Separated Values) file format to define a Bilateral Table for Clients or Servers. These files, called ICCPClient.blt on the Client side and ICCPServer.blt on the Server side, have an internal structure that users must follow.

To create these files, the following possibilities are available:

•If this Driver works as an ICCP Client, users can create a reading point declaration file ICCPClient.blt using an Online ICCP Server

•Using a file in Excel format, provided with this Driver, exporting it to a CSV format, and then renaming it to ICCPClient.blt or ICCPServer.blt

•Importing an XML file in Sisco AXS4 format

•Editing this file manually with an ASCII editor, such as Notepad

•Editing, at run time, the operation Tags of this Driver

Client or Server Tags in Elipse E3 or Elipse Power can be created automatically in Offline mode using the Tag Browser window, if these files were already created.

This Driver implements ICCP Blocks 1 (one, Basic Services), 2 (two, Extended Conditions), 3 (three, Blocked Transfers), and 5 (five, SBO Device Control).