Class PowerTransformer
object --+
|
Element'.Element --+
|
Core.IdentifiedObject'.IdentifiedObject --+
|
Core.PowerSystemResource'.PowerSystemResource --+
|
Core.Equipment'.Equipment --+
|
Core.ConductingEquipment'.ConductingEquipment --+
|
PowerTransformer
An electrical device consisting of two or more coupled windings, with
or without a magnetic core, for introducing mutual coupling between
electric circuits. Transformers can be used to control voltage and phase
shift (active power flow). A power transformer may be composed of
separate transformer tanks that need not be identical. The same power
transformer can be modelled in two ways, namely with and without tanks:
<ol> <li>The power transformer that uses power
transformer ends directly (without tanks) is suitable for balanced
three-phase models. This is typical for transmission and sub-transmission
network modelling. Such a transformer will require one power transformer
end for each physical winding. There must be a one-to-one association
between PowerTransformerEnd and Core::Terminal.</li>
<li>The power transformer that uses transformer tanks is suitable
for an unbalanced transformer, a balanced transformer within a single
tank, or a balanced transformer made up of three tanks. This is typical
for distribution network modelling and the only choice when modelling an
unbalanced transformer, or a transformer that has more than three
windings. Power transformer modelled with tanks will require for each
tank, one transformer tank end per physical winding in the tank. There
may be one, two, or three phases in the transformer tank end. Examples:
3 phases for 3-phase delta or wye connected windings, 2 for one
phase-to-phase winding, and 1 for a phase-to-neutral or phase-to-ground
winding. With 1 or 2 phases, more than one transformer tank end may be
associated to the same 3-phase Core::Terminal instance, while with 3
phases there should be a one-to-one association.</li> </ol>
This power transformer model is flexible in order to support different
kinds of data exchange requirements. There are 5 possible ways to combine
available classes and their attributes: <ol>
<li>Instance parameters - Use the r, x, r0, x0, b, b0, g, and g0
attributes on PowerTransformerEnd and ignore related
TransformerStarImpedance, TransformerMeshImpedance, or
TransformerCoreAdmittance. This option assumes a star connection of the
series impedances. It is suitable for typical transmission, balanced
three-phase transformer models, for transformers with 2 or three
windings.</li> <li>Star instance parameters by
association - Instead of the r, x, r0, x0, b, b0, g, and g0 attributes,
use associations to TransformerStarImpedance and
TransformerCoreAdmitance. This option is suitable in same scenarios as
option 1, but when catalogue data is available for
transformers.</li> <li>Mesh instance parameters by
association: Instead of the r, x, r0, x0, b, b0, g, and g0 attributes,
use associations to TransformerMeshImpedance and
TransformerCoreAdmittance. This option supports transformers with more
than three windings.</li> <li>Catalog mesh parameters
by association - Instead of attributes r, x, r0, x0, b, b0, g, and g0 and
associations to TransformerStarImpedance, TransformerMeshImpedance, or
TransformerCoreAdmittance, use the association to TransformerEndInfo. The
TransformerEnd.endNumber should match the corresponding
TransformerEndInfo.endNumber, following the IEC standard convention of
numbering from the highest voltage ends to the lowest, starting at 1.
This matching supports higher-level use of a catalog, through just one
association between TransformerTank and TransformerTankInfo, with simpler
exchanges and incremental updates. The associated TransformerEndInfo will
have associations to TransformerMeshImpedance and
TransformerCoreAdmittance. This option supports unbalanced transformer,
with more than three windings and is suitable whenever the transformer
test data has been converted to an electrical model.</li>
<li>Catalog test data by association - This is the same as option
4, except TransformerEndInfo will have associations to
AssetModels::TransformerTest decendents, instead of to
TransformerMeshImpedance and TransformerCoreAdmittance. This option is
suitable when the test data is available, and the receiving application
is able to interpret the test data.</li> </ol> Every profile
should specify which one or more of these options are supported.
|
|
__init__(self,
*args,
**kw_args)
Initialises a new 'PowerTransformer' instance. |
|
|
|
Inherited from Core.PowerSystemResource'.PowerSystemResource:
getLocation,
setLocation
Inherited from Core.IdentifiedObject'.IdentifiedObject:
addNames,
getNames,
removeNames,
setNames
Inherited from object:
__delattr__,
__format__,
__getattribute__,
__hash__,
__new__,
__reduce__,
__reduce_ex__,
__repr__,
__setattr__,
__sizeof__,
__str__,
__subclasshook__
|
__init__(self,
*args,
**kw_args)
(Constructor)
|
|
Initialises a new 'PowerTransformer' instance.
- Parameters:
Location - Location of this power system resource.
- Overrides:
object.__init__
|