updated May 11, 2011

Scenario

1.  openPDC Server Installation

1.1.  Download and Install openPDC per section 1 in  Part 1:   GridTrak Open Source PMU Integration with openPDC

For this scenario, openPDC version 1.5.2, 64 bit from the May 5/6, 2011 nightly build and PMU Connection Tester 4.2.7 will be installed.

The platform for this scenario’s openPDC server is Windows 2008 Enterprise R2/64, 2GB RAM, AMD Phenom II X4-955 (3.21 GHz) running in a Hyper-V virtual machine with allocation for 2GB RAM and 4 virtual CPUs and 127GB VHD.  Also installed in the server are SQL Server 2008, Visual Studio 2010 Professional, and IIS web server.

We will use Windows Integrated Security for SQL Server and use pass through user credentials for the openPDC service.

openPDC_SqlSetup   openPDC_UserCredentials

Add Company and Vendor for GridTrak, add gridtrak Vendor Device, and update the Node information.

openPDC_Node

1.2.  The openPDC server is configured with a static IP4 Address:  192.168.0.83.  For this scenario, the openPDC Server and openPDC PMU Client are on the same LAN network segment.

2.  openPDC PMU Client Setup

The openPDC PMU Client is running on a Windows 7 Professional PC with a gridtrak Sensor connected by serial port.  The following is a screen shot of the gridtrak Device configuration in the openPDC Client.

openPDC_PMUClientDevice

2.1.  Select the Manage Menu, Configure an Output Stream.  Set the configuration to transmit UDP to the server (192.168.0.83) on port 4712.  Enable Auto Publish Config Frame and Auto Start Data Channel.

openPDC_ClientOutputStream

2.2.  While configuring the Output Stream, click the Launch Device Wizard link (in the browse list row for the selected Output Stream) and add the PMU device.

openPDC_ClientOutputStream_AddDeviceWiz

2.3.  Open the Windows Control Panel, open the Windows Firewall applet and select the Advanced options. 

Create and Enable an Outbound Firewall Rule for UDP Port 4712.

openPDC_Client_FirewallOut1_UDP-4712    openPDC_Client_FirewallOut2_UDP-4712

openPDC_Client_FirewallOut3_UDP-4712

2.4.  We can run Wireshark and filter for udp.dstport == 4712 to verify that the configured openPDC Output Stream is transmitting.

I’ll need to ask the openPDC developers why there are no UDP checksums in the UDP packet.  The UDP packet contains IEEE C37.118 data as indicated by the “aa01” prefix.  The IEEE C37.118 data packet will have its own CRC check.

openPDC_Client_Wireshark-UDP=4712

3.  Windows Server Configuration to Receive Data

3.1.  Open the Windows Control Panel, open the Windows Firewall applet and select the Advanced options. 

Review the Inbound Rules to determine if there are any conflicts for UDP Port 4712.  In our server, there 2 Rules for Windows Media Player that allow UDP on any local port.  These 2 rules are disabled.  I suspect that running Windows Media Player on the server could potentially cause problems with receiving UDP, so we won’t do that!

openPDC_Server_Firewall_UDP-4712

3.2.  Run the PMU Connection Tester and configure it to listen or UDP Port 4712.  In the Settings tab, set Force IP4  to True.  Enter the Device ID Code for the PMU and click the Connect button.  The Real Time Frame Detail at the bottom of the window should show incoming data.  After about 1 minute (or less) the PMU Connection Tester should receive a Configuration Frame.  After receiving the Configuration Frame, the program will start plotting the data on the graph.

openPDC_Server_PmuConnTester_UDP-4712

3.3.  In the PMU Connection Tester File menu, Save the Connection and the Configuration in files.

4.  Configure the openPDC Server to Receive the Data Stream

On the Server, do this:

4.1.  If the PMU Connection Tester is Connected, Disconnect it and optionally close it.

4.2.  Run the openPDC Manager and in the Devices menu, select Add New (Wizard)

4.3.  In the Device Configuration Wizard, Step 1, click Browse next to the Connection File field and load the file saved from the PMU Connection Tester session.

4.4.  After loading the Connection File, the Device ID Code and Device Protocol fields should be updated.  Click Next to continue to Step 2.

openPDC_Server_NewDeviceStep1

4.5.  In Step 2, click Browse next to the Configuration File field and load the file saved from the PMU Connection Tester Session.

4.6.  After loading the Configuration File, check the Connection is to Concentrator checkbox and fill in the PDC fields. 

openPDC_Server_NewDeviceStep2

4.6.A)  You may optionally review and change the configuration by clicking the Modify Configuration button.

openPDC_Server_NewDeviceStep2_ModifyCfg

4.7.  Click Next to move on to Step 3.  The New Device is shown.  Click Finish, then click OK to close the Success dialog.

openPDC_Server_NewDeviceStep3  openPDC_Server_NewDeviceSuccess

4.8.  The Browse Devices screen now displays two Devices.  One is the remote PMU and the other is the remote openPDC Concentrator.  The remote openPDC Concentrator can be identified by the checked box in the Concentrator column.

openPDC_Server_BrowseDevices

Last edited Jan 15, 2012 at 3:48 AM by ajstadlin, version 8

Comments

No comments yet.