The use of synchrophasors for monitoring and improving the stability of power transmission networks is gaining in significance all over the world. The aim is to monitor the system state, to intensify awareness for system stability and to make optimal use of existing lines. This way, system stability can be improved overall and even the transmission performance can be increased. The data from so many PMU’s and PDC’s needs to be collected and directed to proper channels for its efficient use. Thus we need to develop an efficient, flexible and hybrid data concentrator that can serve this purpose. Besides accepting the data from PMU’s, PDC should be able to accept the data also from other PDC. We have designed such a PDC (iPDC) that accepts data from PMU & PDC that are IEEEC37.118 standard compliant. WAMS architecture with iPDC and PMU at different levels. This architecture enables iPDC to receive data either from a PMU or other iPDC. Both PMU and iPDC from whom the data is being received should be IEEE C37.118 synchrophasor standard compliant. It is hybrid architecture. iPDC Design The client server architecture is common in networks when two peers are communicating with each other. Of the two peers (PMU and iPDC) that are communicating with each other in WAMS one acts as a client and the other as a server. Since PMU saves the requests coming from iPDC by sending data or configuration frames it acts as a server. It listens for command frames from iPDC. PMU-iPDC communication can be either over TCP or UDP communication protocols. On receiving command frames, PMU replies to the iPDC with data or configuration frames according to the type of request. iPDC functionality is bifurcated as server and client. iPDC as a Client - When iPDC receives data or configuration frames its acts as a client. When acting as a client, it creates a new thread for each PMU or a PDC from whom it is going to receive data/configuration frames. This thread would establish connection between the two communication entities. It handles both TCP and UDP connections. The first frame that the server (PMU/PDC) would receive is the command for sending the configuration frame. When the server replies with the configuration frame, iPDC (client) would generate another request to start sending the data frames. On receiving such a command frame, the server starts sending the data frames. If there is some change in the status bits of data frame which the client (iPDC) notices, it would take an action. For example if it notices a bit 10 has been set, it would internally send a command to server to send the latest configuration frame. iPDC as a Server- When iPDC receives command frames from another PDC it would acts as a server. There would be two reserved ports one for UDP and other for TCP on which the PDC would receive command frame requests. Thus PDC now plays the role of PMU waiting for command frames.

1. iPDC
Phasor Data Concentrator
User Manual
by
Kedar Khandeparkar
&
Nitesh Pandit
under the guidance of
Prof. A.M. Kulkarni
Indian Institute of Technology, Bombay

2. We would like to express my sincere thanks and gratitude to Prof. A.M. Kulkarni,
Prof. V.Z. Attar & Prof. S.U. Ghumbre for the constant motivation and valuable guidance
they provided us throughout the course of the project. We am highly indebted to them for
giving us this opportunity to work under them for this M.Tech project, and also clarifying
our doubts and for bringing into perspective, the dierent aspects of the project topic.
They constantly encouraged us by giving suggestions and criticisms on our work. Working
under them has been a great learning experience for us.
i

3. Contents
1 How to use iPDC 2
1.1 Start iPDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Add a Source Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Remove a Source Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Turn OFF the data Transmission . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 Turn ON the data Transmission . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6 Request Conguration frame . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.7 Add a Destination Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.8 Remove a Destination Device . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.9 iPDC Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.10 iPDC Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 DBServer 17
3 How to use PMU Simulator 18
3.1 Start PMU Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2 Create Conguration Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Header Frame Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.4 View PMU Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.5 Update Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.6 Exit PMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
ii

4. List of Figures
1 iPDC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Setup Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Tooltip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4 Add Source Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5 Successfull Done . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6 Add Source Device Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7 Remove Source Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8 Remove Source Device Error . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9 Data Transmission OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
10 Data Transmission ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
11 Conguration Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
12 Add Destination Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
13 Remove Destination Device . . . . . . . . . . . . . . . . . . . . . . . . . . 14
14 Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
15 iPDC Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
16 PMU Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
17 tooltip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
18 Conguration Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
19 Phasor Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
20 Analog Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
21 Digital Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
22 Successfull Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
23 Header Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
24 PMU Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
25 STAT change options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
26 STAT Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
27 Set Conguration Change Bit . . . . . . . . . . . . . . . . . . . . . . . . . 29
28 New Phasors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
29 New Phasor Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . 31
30 New Analogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
31 New Analog Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . 33
32 Remove Phasors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
33 Remove Phasors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
34 Data Rate Change Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
35 New Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
iii

5. 36 Conguration Change Bit Set . . . . . . . . . . . . . . . . . . . . . . . . . 38
37 Exit PMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1

6. 1 How to use iPDC
1.1 Start iPDC
Installation of iPDC is given in README le. After installing iPDC, open a terminal,
switch to the iPDC folder and type iPDC to start the application. The user will get
iPDC Setup window along with the main window. User need to ll the iPDC details.
The screenshots of this operation are given below.
iPDC Setup
Figure 1: iPDC Setup
2

7. Setup Details
Figure 2: Setup Details
3

8. 1.2 Add a Source Device
ToolTip
The tooltip gives the details of the operation performed by a button. In order to add a
Source Device the mouse pointer is moved to Add Source Device button.
Figure 3: Tooltip
4

9. Add Source Device Window
On clicking the Add a Source Device button, the user will be prompted with a window.
The screenshot of the same is given below. User has to ll the elds with proper values.
Figure 4: Add Source Device
5

10. Sucessfull Operation
Below Screenshot shows the successfull source device add operation.
Figure 5: Successfull Done
6

11. UnSucessfull Operation
If the values are not entered properly then the user will be prompted with an error window.
Some of the errors messages are Please enter valid value for device ID code, Please enter
valid IP Address, etc.
Figure 6: Add Source Device Error
7

12. 1.3 Remove a Source Device
Remove Source Device Window
On clicking the Remove a Source Device button, the user will be prompted with a
window. The screenshot of the same is given below. User has to enter the IDcode and
protocol of the Source device to be removed.
Figure 7: Remove Source Device
8

13. Unsuccessfull remove operation
If the user enters wrong values in the elds, then remove operation will fail and user will
be prompted with an error window. Remove operation fails if the values entered do not
exist.
Figure 8: Remove Source Device Error
9

14. 1.4 Turn OFF the data Transmission
User may require to explicitly turn o the data transmission of a Source device. On
clicking Turn OFF the data Transmission button, the user will be prompted with a
window. The screenshot of the same is given below. User has to enter the IDcode and
protocol of the Source device whose data transmission is to be put o.
Figure 9: Data Transmission OFF
10

15. 1.5 Turn ON the data Transmission
In order to restart the previously turned o data transmission of a source device user
has to click Turn ON the data Transmission button. The user is prompted with a
window which displays the details of Source devices whose data transmission is turned
o. When user enters the correct values the data transmission restarts.
Figure 10: Data Transmission ON
11

16. 1.6 Request Conguration frame
User may require to explicitly send a request to get latest Conguration frame of a Source
device. On clicking Request Conguration frame button, the user will be prompted
with a window. The screenshot of the same is given below. User has to enter the IDcode
and protocol of the Source device to whom conguration frame request is to be sent.
Figure 11: Conguration Request
12

17. 1.7 Add a Destination Device
Once we click the Add a Destination Device button, the user will be prompted with a
window. The screenshot of the same is given below. User has to ll the elds with proper
values. The destination device is the one whom the iPDC sends the combined data and
conguration frames.
Figure 12: Add Destination Device
13

18. 1.8 Remove a Destination Device
To remove a previously added Destination device user has to click Remove a Destina-
tion Device button. On entering the correct values the device will be removed.
Figure 13: Remove Destination Device
14

19. 1.9 iPDC Connection Table
To view the details of Source Destination Devices to which iPDC is connected user has
to click iPDC Connection Table button.
Figure 14: Connection Table
15

20. 1.10 iPDC Details
To view the iPDC details user has to click iPDC Details in the menu tab.
Figure 15: iPDC Details
16

21. 2 DBServer
Installation of DBserver can be seen in README le. If the data from Source devices need
to be stored in MySQL database then user has to install DBServer. Before running iPDC
application, user has to run DBServer. Details of how to run DBServer are mentioned
in README. It is a UDP server listening on xed port 9000 on which it would receive
the data from iPDC. MySQL database need to be pre-congured and database and tables
should be created from le db.sql.
17

22. 3 How to use PMU Simulator
3.1 Start PMU Simulator
Installation of PMU Simulator is given in README le. After installing PMU Simula-
tor, open a terminal, switch to the PMU Simulator folder and type PMU to start the
application. The user will get PMU Setup window along with the main window. User
need to ll the PMU Server details. The screenshot of this operation is given below.
PMU Server Setup
Figure 16: PMU Server Setup
18

23. 3.2 Create Conguration Setup
ToolTip
The tooltip gives the details of the operation performed by a button. In order to create
conguration frame for PMU the mouse pointer is moved to Create Conguration
Frame button.
Figure 17: tooltip
19

24. Dene PMU Conguration
def: A conguration frame is a machine-readable BINARY data set containing informa-
tion and processing parameters for the PMU and the current real-time data set.
On clicking the Create Conguration Frame button, the user will be prompted with a
window. The screenshot of the same is given below. User has to ll the elds with proper
values. The Conguration Frame will generated as per the IEEE C37.118 standard.
Figure 18: Conguration Details
20

25. Add Phasor Channels
On clicking the Next button on PMU Conguration Setup Window, the user will be
prompted with a new window. The screenshot of the same is given below. User has to
ll the phasor channel names properly.
Figure 19: Phasor Channel Names
21

26. Add Analog Channels
On clicking the Next button on Phasor Channels Window, the user will be prompted
with a new window. The screenshot of the same is given below. User has to ll the analog
channel names properly (if any).
Figure 20: Analog Channel Names
22

27. Add Digital Channels
On clicking the Next button on Analog Channels Window, the user will be prompted
with a new window. The screenshot of the same is given below. User has to ll the digital
channel names properly (if any).
Figure 21: Digital Channel Names
23

28. Sucessfull Operation
Below Screenshot shows the Conguration frame successfully created.
Figure 22: Successfull Operation
24

29. 3.3 Header Frame Generation
def: This frame shall be human readable information about the PMU, the data sources,
scaling, algorithms, ltering, or other related information.
On clicking the Header Frame Generation button, the user will be prompted with
a window. The screenshot of the same is given below. User has to enter the PMU de-
tails properly as per above denition. The Header Frame will generated as per the IEEE
C37.118 standard.
Figure 23: Header Frame
25

30. 3.4 View PMU Details
User can view the PMU server and conguration details by clicking View Conguration
Details button.
Figure 24: PMU Details
26

31. 3.5 Update Conguration
On clicking the Update Conguration button, the user will be prompted with a win-
dow. The screenshot of the same is given below.
Figure 25: STAT change options
27

32. STAT Change
The STAT word bits can be changed by clicking any of the buttons on Conguration
Modication Window. There is a separate button for some of the bits in STAT word
whose details can be found in the IEEEC37.118 Synchrophasor Standard. The screenshot
of the same is given below.
Figure 26: STAT Changed
28

33. Conguration Change Bit
On clicking the Set Conguration Change Bit button, the user will be prompted with
a new window. The screenshot of the same is given below. User has to select one of the
options.
Figure 27: Set Conguration Change Bit
29

34. Add Channels
If user clicked on the Add Channels.
Add New Phasor
After selecting the Add Channels user will be prompted with a new window. The screen-
shot of the same is given below. User has to ll the number of new phasor to be added.
It could be zero also.
Figure 28: New Phasors
30

35. New Phasor Channel Names
On clicking the Next button, the user will be prompted with a new window. The screen-
shot of the same is given below. User has to ll the new phasor channel names properly
(if new phasor num zero).
Figure 29: New Phasor Channel Names
31

36. Add New Analogs
On clicking the Next button, the user will be prompted with a new window. The screen-
shot of the same is given below. User has to ll the number of new analogs. It could also
be zero.
Figure 30: New Analogs
32

37. New Analog Channel Names
On clicking the Next button, the user will be prompted with a new window. The screen-
shot of the same is given below. User has to ll the new analog channel names properly
(if new analog num zero).
Figure 31: New Analog Channel Names
33

38. Remove Channels
If user clicked on the Remove Channels.
Remove Phasors
After selecting the Remove Channels user will be prompted with a new window. The
screenshot of the same is given below. User has to ll the phasor number of phasors to
be removed and it should be within the range of available number of phasors.
Figure 32: Remove Phasors
34

39. Remove Analogs
On clicking the Next button, the user will be prompted with a new window. The screen-
shot of the same is given below. User has to ll the number of analogs to be removed and
it should be within the range of available number of analogs.
Figure 33: Remove Phasors
35

40. Data Rate Change Option
After performing the add or remove channels operation user will be prompted with a new
window. The screenshot of the same is given below. User has to select the option for
Data Rate.
Figure 34: Data Rate Change Option
36

41. New Data Rate
On clicking the YES on PMU Data Rate window, the user will be prompted with a new
window. The screenshot of the same is given below. User has to select the new data rate
from the drop down box.
Figure 35: New Data Rate
37

42. Successfull Conguration Modication
On clicking the Next on New Data Rate window or NO on PMU Data Rate window, the
user will be prompted with a new window. The screenshot of the same is given below. Its
shows the conguration frame successfully modied and respectively STAT bit changed.
Figure 36: Conguration Change Bit Set
38

43. 3.6 Exit PMU
User can terminate the PMU Simulator by clicking on the PMU Quit button.
Figure 37: Exit PMU
39