Introduction

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. This table's format, its configuration, or maintenance is outside the scope of this standard.

For an easy interchange of this table among different software manufacturers, 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 the same 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 declaration file for an ICCPClient.blt reading point using an Online ICCP Server

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

•Importing an XML file in the Sisco AXS4 format

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

•Editing, at run time, this Driver's operation Tags

Client or Server Tags in 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, 2, 3, and 5 (Basic Services, Extended Conditions, Blocked Transfers, and SBO Device Control, respectively).