Стандарт детерминирует диаграмму состояний узлов канала связи и переходы между ними по событиям в канале. Также на этом уровне осуществляется контроль целостности и последовательности кадров и данных, контроль потока , отсчет таймаутов. Группа обобщающих документов[ править править код ] Обобщающий стандарт англ. Представляет собой выборку из излишне универсальных базовых документов и других стандартов. Физический уровень[ править править код ] Используется асинхронный интерфейс UART с 1 стопбитом, 1 битом четности и 8 битами данных.
|Published (Last):||8 February 2011|
|PDF File Size:||12.28 Mb|
|ePub File Size:||19.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
Prior to the development of electronics and telecommunications networks all co-ordination between control centres was carried out by telephone. However, the development of SCADA supervisory control and data acquisition systems allowed remote control and monitoring of electrical plant from centralised control centres. Initially individual SCADA manufacturers developed their own proprietary "closed" protocols for communicating from a control centre to electrical equipment in the field.
However, none of these communication protocols were suited to the requirements of communicating between control centres. To meet these special requirements for communication and co-ordination between control centres the IEC developed the IEC set of standards. Background[ edit ] Inter-utility real time data exchange has become critical to the operation of interconnected systems in most parts of the world.
For example, the development of electricity markets has seen the management of electricity networks by a functional hierarchy that is split across boundaries of commercial entities. At the top level there is typically a system operator with coordination responsibilities for dispatch and overall system security.
Below this are regional transmission companies that tie together distribution companies and generating companies. In continental power systems there is now considerable interconnection across international borders. ICCP allows the exchange of real time and historical power system information including status and control data, measured values, scheduling data, energy accounting data and operator messages.
Historically there has been reliance on custom or proprietary links and protocols to exchange real time data between systems. ICCP began as an effort to develop an international standard for real-time data exchange within the electric power utility industry.
A working group was formed in to develop a protocol standard, develop a prototype to test the specification, submit the specification to the IEC for standardisation and carry out interoperability testing between developing vendors. The initial driver was to meet European Common Market requirements in The official designation of the first protocol was TASE.
In the US, ICCP networks are widely used to tie together groups of utility companies, typically a regional system operator with transmission utilities, distribution utilities and generators. Regional operators may also be connected together to co-ordinate import and export of power between regions across major inter-ties.
The objects that are used to convey the data are defined in various parts of IEC Block Description Data Examples: Periodic System Data: Status points, analogue points, quality flags, time stamp, change of value counter, protection events. Association objects to control ICCP sessions. Extended Data Set Condition Monitoring: Provides report by exception capability for the data types that block 1 is able to transfer periodically.
Block Data Transfer: Provides a means transferring Block 1 and Block 2 data types as block transfers instead of point by point. In some situations this may reduce bandwidth requirements.
Information Messages: Simple text and binary files. Includes mechanisms for interlocked controls and select-beforeoperate. Event Reporting: Extended reporting to a client of error conditions and device state changes at a server.
Additional User Objects: Scheduling, accounting, outage and plant information. Time Series Data: Allows a client to request a report from a server of historical time series data between a start and end date. Data transfers result from a request from a control centre client to another control centre server. Control centres may be both clients and servers.
As such any physical interfaces, transport and network services that fit this model are supported. ICCP may operate over a single point-to-point link between two control centres; however, the more general case is for many control centres and a routed wide area network.
A client may establish associations with more than one server and a client may establish more than one association with the same server. Multiple associations with same server can be established at different levels of quality of service so that high priority real time data is not delayed by lower priority or non real time data transfers.
These services are normally provided by lower protocol layers. The agreement identifies data elements and objects that can be accessed via the link and the level of access permitted. Once an ICCP link is established, the contents of the Bilateral Tables in the server and client provide complete control over what is accessible to each party. There must be matching entries in the server and client tables to provide access to data and objects. Although interoperability is not regarded as a high risk area, the standard is such that an implementation does not have to support all conformance blocks in order to claim compliance with the standard.
A minimal implementation only requires Block 1. Only those blocks necessary to achieve the required functionality need be implemented. It is also not necessary to support all objects defined in the standard for any particular block. Extensive interoperability testing between products of some of the major vendors has been a feature of ICCP protocol development. Independent reports are available, as no doubt are reports from vendors.
An ICCP purchaser must define functionality required in terms of conformance blocks required and the objects within those blocks. Application profiles for the ICCP client and server conformances must match if the link is to operate successfully.
Product Differentiation[ edit ] ICCP is a real time data exchange protocol providing features for data transfer, monitoring and control. For a complete ICCP link there need to be facilities to manage and configure the link and monitor its performance.
The ICCP standard does not specify any interface or requirements for these features that are necessary but nevertheless do not affect interoperability.
ICCP implementers are free to handle these issues any way they wish. Local implementation is the means that developers have to differentiate their product in the market with added value. Additional money spent on a product with well-developed maintenance and diagnostic tools may well be saved many times over during the life of the product if use of the ICCP connection is expected to grow and change. As a networked server. As a gateway processor. This configuration offers maximum performance because of the direct access to the SCADA database without requiring any intervening buffering.
This approach may not be available as an addition to a legacy system. A networked server making use of industry standard communications networking to the SCADA host may provide performance approaching that of an embedded ICCP application. On the application interface side the ICCP is not restricted to the SCADA environment but is open to other systems such as a separate data historian or other databases.
Security may be easier to manage with the ICCP server segregated from the operational real time systems.
The gateway processor approach is similar to the networked server except it is intended for legacy systems with minimal communications networking capability and so has the lowest performance.
IEC 60870-6 ICCP/TASE.2 communication protocol