Professional Documents
Culture Documents
Activity No. 2
Admittance Matrix Formulation using IEEE
Common Data Format for the Exchange of
Solved Load Flow Data
I.
DELIVERABLES
1. Softcopy of source code and required output text files (.txt).
2. Hardcopy of documentation. Submit in A4 paper, IEEE double-column format.
3. Place all files in an encrypted compressed folder (RAR) and upload it at our class e-group with the
following filename format: SURNAMES_GROUP#_ACT# (e.g. CRUZ-SANTOS_GROUP2_ACT2.rar)
II.
OBJECTIVES
1. To be able to understand common data format used in solving load flow problems.
2. To be able to use MATLAB or other programming tool/language to read and parse data.
3. To be able to develop a program that will formulate the BUS Admittance Matrix using IEEE
formatted data.
III.
DISCUSSION
The data file has lines of up to 128 characters. The lines are grouped into sections with section headers.
Data items are entered in specific columns. No blank items are allowed, enter zeros instead. Floating
point items should have explicit decimal point. No implicit decimal points are used.
Data type codes:
Bus Data
==========
Section start card :
--------------------1st row
Columns 1- 4 -999
2nd row
Columns 1-16 BUS DATA FOLLOWS
3rd row
Columns 1- 4 -999
Bus data cards :
----------------Columns 1- 4 Bus number (I)
Columns 6-17 Name (A) (left justify)
Columns 6-7 Substation code
Columns 8-9 Voltage level(23-230 kV, 11-110 kV, 69-69 kV, 34-34.5 kV, 13-13.2 kV, 6.-6.24 kV)
Columns 10-10 Type of busbar(B-physical busbar, b-virtual busbar)
Columns 11-13 Ckt. number
Columns 19-20 Load flow area number (I) Don't use zero!
Columns 21-23 Loss zone number (I)
Columns 25-26 Type (I)
0 - Unregulated (load, PQ)
1 - Hold MVAR generation within voltage limits, (PQ)
2 - Hold voltage within VAR limits (gen, PV)
3 - Hold voltage and angle (swing, V-Theta) (must always
have one)
1
IV.
PROBLEM SPECIFICATION
1. The input text files should follow the format shown below.
2. The high-level programming language Matlab can be used but not limited to other programming
language such as C/C++, Java, Visual Basic/C++, etc..
3. The documentation should include but not limited to the following sections.
i. Abstract brief summary of the problem and your program
ii. Implementation include a short description of each program module/part
iii. Testing emphasize all assumptions you made in your program.
iv. Results and Discussion
v. Conclusions answer the problem objectives
vi. On the first page/cover page of your documentation, write the boxed statement below (or any
statement of the same effect) and sign.
We certify upon our honor that we solved this activity independently, without asking help
from anybody. We may have, however, consulted published references and reading
materials, and we hereby acknowledge (write proper bibliography) them accordingly. It
took us _______ hours to finish this activity.
___________________
Sign over printed name
V.
___________________
Sign over printed name
DISCUSSION
1. What programming language/tool did you use in this activity and why?
2. How did you find the IEEE data format compared to other format used in Load flow study.
3. Where you able to meet all objectives for this activity? State all the challenges you have
encountered in this activity and discuss how you come up with the solutions.