Documentation
| Grid Protection Alliance | openPDC Project on GitHub | openPDC Wiki Home | Documentation |
The default IP stack for most new Windows systems is IPv6, this means all connections will default to IPv6 unless otherwise specified. If you want the openPDC to use IPv4, the server and client connections can be configured to use the IPv4 stack by specifying “;interface=0.0.0.0” in the relevant configuration settings and connection strings. The interface setting is used to specify the IP address of the network interface controller (NIC) to use for the connection – an IP of zero means that the default NIC should be used for the connection; the format of the interface IP setting determines the IP stack version, i.e., IPv4 or IPv6, to use for the connection, for example, to force use of IPv6 you would use “;interface=::0”.
- User's Documentation
- Getting Started
- Frequently Asked Questions
- Use and Configuration Guides
- Overview of the openPDC Management System
- How to Use the openPDC Manager
- Default openPDC Ports
- Running openPDC on Linux / Mac
- Running openPDC on a Raspberry Pi
- Data Quality Reporting Services
- Custom Point Tag Naming Convention
- Enabling Security for Historian Web Services
- The GEP Subscription Tester
- Running the openPDC in Virtual Machine
- Moving Historian to Another Location
- Using a "Gateway Style Connection" between openPDCs and/or openPGs
- Controlling UDP data loss
- Remote Console Security
- Help Me Choose Diagrams
- Configuration File Settings
- Setting for Uniform CPU Utilization
- openPDC Console Commands to Adjust Configuration Settings
- openPDC OSI-PI Adapters
- Data Quality Monitoring Adapters
- Adapter Connection String Syntax
- openHistorian 1.0 Archive Size Calculator ++ Archived XLSX
- Distributed Historian Setup Notes
- Automated Archive Data Recovery Operation (a.k.a. Missing Data Gap Filling)
- Automated Connection Failover Operation
- Adjusting Output Stream Labels to Meet ISO Naming Standard
- PMU Connection Tester (accessed via host site)
- How to Manually Configure the openPDC
- How to Bulk Apply line-to-line Sqrt(3) Adjustment to all Voltage Magnitudes
- Single Page Overview
- Developer's Documentation
- Getting Started
- Frequently Asked Questions
- Build the openPDC Manager
- Data Access Options for the openPDC
- Device to Data in 5 Easy Steps
- High-level Code Structure and Class Relationships
- How to Create a Custom Adapter
- Two Custom Adapter Examples
- Multiple Adapter Synchronization
- Automated Phasor Tag Naming Convention
- About the Signal Reference Field
- Processing openPDC data with Hadoop
- Code Change Notes
Note: you can get a quick optimization of the openPDC run-time assemblies by using the .NET native image cache NGen.
The most recent system API help and documentation can be downloaded from the Nightly Builds - it's included with the binaries. This help can be used as standalone, compiled help files (.chm) or can be directly integrated within Visual Studio. We have also made our help system available online: Synchrophasor Protocol Classes Documentation
- Sep 12, 2016 HTML to Markdown by chefsteph9
- Oct 5, 2015 Migrated from CodePlex by ajs
- May 29, 2015 4:39 PM Last edited by ritchiecarroll, version 97
Copyright 2016 Grid Protection Alliance