The historian is also designed to be used in distributed systems, having a single node dedicated to archival and several others sending concentrated measurements to the central archive. The files produced by the historian can later be analyzed using Hadoop. The project includes a historian for data archival. The system is capable of concentrating over one billion measurements per day coming from over 100 phasor measurement units across the Eastern Interconnection. The sorted measurements can then be streamed to other applications using either IEEE C37.118 or BPA PDCstream. There is also a built-in concentration engine which sorts the real-time data into frames based on the timestamp associated with each measurement. The supported protocols are IEEE C37.118 (v1.0 and Draft 6), IEEE 1344, BPA PDCstream, FNET, SEL Fast Message, and Macrodyne. The openPDC implements a number of standard phasor protocols which can be used to receive data from devices. These adapters can be configured using any one of three supported database systems: Microsoft SQL Server, MySQL, and Microsoft Access. The output adapter layer is typically responsible for archival of measurements received from the input adapter layer and the action adapter layer.Adapters in this layer can also introduce new measurements to the system, just like adapters in the input adapter layer. The action adapter layer is typically responsible for concentration and processing of the input measurements.That data is used to create measurements which are sent to other adapters to be processed or archived. The input adapter layer is typically responsible for receiving data from an outside source such as a phasor measurement unit.The service is responsible for managing the life cycle of adapters that create and process the streaming phasor measurements.
Open pdc file windows#
The phasor data concentrator runs as a Windows service. Finally, on April 1, 2010, the Grid Protection Alliance inherited development of the openPDC and entered into a contract with the North American Electric Reliability Corporation in an effort to further enable its use as a distributed system. Then on February 23, 2010, AREVA T&D announced that they would be providing commercial support for the openPDC. The first stable release of the openPDC was made available on January 28, 2010. The openPDC officially launched on October 7, 2009. This port is often open, since it is needed for surfing the web.Ĭreate the Kerberos configuration file.The openPDC is based on the SuperPDC which was developed by the Tennessee Valley Authority starting in 2004. The next thing to try is to get Kerberos to communicate via http over TCP port 80. If it still does not work, continue with the next step.
If there is no contact through UDP port 88, open TCP port 88 for outgoing traffic instead (if possible), and try kinit again. After that, try to contact our authentication server with kinit as described before. This is the default (and preferred) mode of operation. If possible, open UDP port 88 for bidirectional communication. Kerberos uses in its standard configuration the following ports for communication: Port nameĪlternative configurations for usage with firewalls (see below)
Contact your system administrators and make sure that a firewall is really the problem. When a firewall is installed between your workstation and the computers at PDC, a special configurations described below may be necessary to use Kerberos.
0 kommentar(er)
