Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
General Remarks
1.1 Licensing
PSS SINCAL
18
PSS NETOMAC
21
21
29
32
34
April 2015
1/36
SIEMENS
General Remarks
1.1
Licensing
PSS SINCAL 11.5 Platform uses the same license file as the preceding PSS SINCAL 11.0 version.
In order to activate the software it is only necessary to assign the license file to the new version using
the PSS Tool utility program.
If you need a new license file or have any questions about the licensing, please contact the Product
Support (phone +43 699 12364435, e-mail sincal@simtec.cc).
1.2
External Programs
The NetCad and SIGRA V4.2 programs are no longer contained on the installation DVD. NetCad has
been replaced by a new Model Editor which is directly integrated in the PSS NETOMAC user
interface. SIGRA is a viewer for COMTRADE files, which is used to display the plot signals of the
dynamic simulation. However, as the relevant functions have long been directly integrated in
PSS SINCAL and PSS NETOMAC, SIGRA is thus no longer required.
If NetCad or SIGRA are nevertheless still required, please contact Product Support. The programs
are then made available via a download link.
1.3
Russian Language
Besides the previously available languages, German, English, Spanish, Chinese and Turkish, the
user interface of the PSS SINCAL platform is now also available in Russian. The required language
is selected as before using the PSS Tool utility program.
April 2015
2/36
SIEMENS
PSSSINCAL
2.1
User Interface
Supplementary Graphic Elements in the Database
In response to many requests from users, the supplementary graphic elements are now also stored
in the database. The supplementary graphic objects have been fully incorporated in the variant
management and can also be generated directly in the database in the same way as the network
elements, such as when making GIS couplings.
Saving in the database was provided for the following supplementary graphic objects:
Line
Rectangle
Ellipse
Arc
Polyline
Freehand line
Text field
Frame
Hilite
Legend
Graphics
Diagrams
However, the saving of the supplementary graphic elements in the database is relatively complex
because the different elements have different attributes, which do not fit well in relational structures
(e.g. long texts with variable length). The saving of the display order with a relational database can
also only be implemented poorly.
In order to save all the data of the supplementary graphic elements different tables are therefore
required:
Table name
Table description
GraphicObjPnt
GraphicObjBase
GraphicObjLegend
GraphicObjText
GraphicOrder
Graphic order
The GraphicObjBase table is the basis for all supplementary graphic elements. This saves the basic
data of all elements. Depending on the object type, other tables are then assigned.
The buckle points of objects are stored (e.g. for polygon and freehand line) in the GraphicObjPoint
table. The GraphicObjText table manages all variable length texts. The GraphicObjLegend table is
specially provided for managing the extended data of the legend.
The display order of network elements and supplementary graphic objects is stored in the
April 2015
3/36
SIEMENS
GraphicOrder table. The table is in the form of a linked list. This is designed to ensure that the
display order can also be managed efficiently in the database.
Information about the attributes in the tables is provided in the Database Description manual in
chapter Tables of Network Graphics.
When updating existing networks, all the supplementary graphic elements stored in the SIN file are
automatically transferred to the database.
Data type
GraphicBackground_ID
Variant_ID
Short
name
Unit
Std.
Description
Long Integer
Long Integer
Flag_Variant
Integer
GraphicLayer_ID
Long Integer
GraphicArea_ID
Long Integer
OrderNo
Integer
Type of Text
File
Text (255)
File Name
Visible
Integer
Visibility Flag
PosX
Double
0.25mm
Position X
PosY
Double
0.25mm
Position Y
Width
Double
0.25mm
Width
Height
Double
0.25mm
Height
Brightness
Integer
Brightness
Contrast
Integer
Contrast
Alpha
Integer
Alpha
April 2015
4/36
SIEMENS
Simplified with graphics from node data based on longitude and latitude
Extended with graphic data for nodes and elements in your own spreadsheets
The graphic import is configured in the Options tab of the Import Excel dialog box. If the Graphic
generation from node data option is activated, it is possible to configure in an enhanced setting
dialog box whether the node data is to be imported in the form of longitude and latitude or as GauKrger coordinates. However, this option is only available if the import of the extended graphic data
is not activated in the file assignment.
April 2015
5/36
SIEMENS
2.2
Electrical Networks
Improved Performance in the Load Flow Calculation
In order to reduce the number of iterations of the load flow calculation, the node voltages are no
longer directly pre-assigned with the slack voltage, but an improved initial voltage is determined by
means of a network tracing.
Furthermore, a wide range of different optimizations were implemented in the load flow calculation in
order to increase computing speed for large networks and networks with poor convergence:
Improved initial values for the initial load flow in the contingency analysis and reliability
calculation
Uniform initialization of voltage with phase rotation thus resulting in improved convergence
April 2015
6/36
SIEMENS
order to model the network elements in PSS SINCAL, the following conventions apply:
Voltages: Like the voltage entry for the network level, the line-line or line-ground voltage must be
entered.
With these agreements, you can include all existing symmetrical networks directly in the
asymmetrical load flow calculations without modifying input data. If you add asymmetrical
subnetworks, you can immediately calculate asymmetrical load flow.
April 2015
7/36
SIEMENS
Equivalent frequency
Radial network
The difference between the Ratio R/X at fault location and Ratio R/X at fault location R/X < 0.3
methods is the application of the following "optional provision" from the standard: As long as R/X
stays less than 0.3 in all branches, it is not necessary to use the factor 1.15.
The Simulation of DC Infeeders in the Short Circuit was also enhanced. DC infeeders have the
same angle of current in the load flow and in the short circuit. However, VDE 0102/IEC 909 stipulates
a different current angle for the short circuit. This angle can therefore be set as required.
The Additional Short Circuit Data field enables the short circuit current of the DC infeeder to be
influenced. If this option is activated, the short circuit current of the DC infeeder has the angle set in
the Angle Short Circuit field.
April 2015
8/36
SIEMENS
The simple decay is only used if a precise decay is not stated via the stability data. The simplified
decay is included in the following procedures:
Protection coordination
Depending on the tripping time, a higher impedance is produced for the next calculation (loop).
The impedance of the machine does not change during the static calculation of a loop.
Dynamics
For this a Parkian model is defined from the subtransient reactance, sustained short circuit and
time constant.
April 2015
9/36
SIEMENS
In order to simplify use of the protection coordination also in these regions, the protection manual
now contains the new chapter Protection Designations According to ANSI. This shows the input
screen forms of PSS SINCAL together with the corresponding ANSI codes.
DI settings predefined
DI settings user-defined
OC protection settings
Voltage tripping
A common time register for the delay times of the individual tripping units normally results in shorter
clearing times in the network. This is particularly the case if the pickup changes to a tripping unit with
a shorter delay time. This is explained with the following example.
April 2015
10/36
SIEMENS
Tripping behavior of protection device B with common time register for the delay time:
Time step 1:
A
Tripping after 200 ms
230 ms
B
Time step 2:
A
B
Tripping unit 1: after 250 ms
Tripping behavior of protection device B with individual time register for the delay time:
Time step 1:
A
Time step 2:
A
B
Tripping unit 1: after 480 ms
April 2015
11/36
SIEMENS
Loop impedance L1 L2
Loop impedance L2 L3
Loop impedance L3 L1
If this does not apply to a protection device, this can be set individually by assigning Loop
Impedance Data in the Directional Element tab. This is useful for the tripping behavior with a twophase ground fault, since without individual settings PSS SINCAL does not use the loop impedance
of the phase-phase loop for the ground tripping.
April 2015
12/36
SIEMENS
It can now be defined with the directional element how the Angle Evaluation works. The following
options are available here:
Normal:
Directional element operates as before.
Modify V:
Instead of the voltage of the actual impedance loop, the sum of the voltage of the other phases
rotated by 90 degrees is used.
Modify V and I:
In addition to the correction of the voltage, the ground current is ignored for phase-ground loops.
The short circuit current characteristics in the I/t diagram are determined with the Working Voltage
and the decay behavior of the machine. The State Decay Current selection field is used to control
the display in the I/t diagram:
No data:
No current is shown in the I/t diagram.
Ia:
The I/t diagram shows the effective value of the tripping current.
Iasym:
The I/t diagram shows the asymmetrical tripping current.
April 2015
13/36
SIEMENS
The display of Transformers in the I/t Diagram was likewise enhanced. Previously, the destruction
through overheating was represented in the I/t diagram with a constant It of 25 times the rated
current for 2 seconds. ANSI C57.92 stipulates, however, that the destruction of the transformer is
divided into thermal and mechanical destruction. For both types of destruction, there are formula for
determining the relevant damage curve irrespective of the rated apparent power for two-winding
transformers. PSS SINCAL calculates both characteristic curves and the "least favorable" is then
displayed in the I/t diagram.
Decay Behavior of a Synchronous Machine:
April 2015
14/36
SIEMENS
If the pickup time of a protection device is permanently reached, this protection device trips and
determines also the time for the first time loop. For all other time steps of the stability calculation the
connection of the protection device that trips is opened. This process is repeated until the fault
current equals 0.0.
All open connections are then reclosed for the consideration of the next fault.
Fault Event
The protection simulation is carried out for each fault event. All fault observations of the fault event
are simulated in the network at the time t = 0.0. All element switch times are ignored.
If the pickup time of a protection device is permanently reached, this protection device trips and
determines also the time for the first time loop. For all other time steps of the stability calculation the
connection of the protection device that trips is opened. This process is repeated until all fault
currents equal 0.0.
All open connections are then reclosed for the consideration of the next fault event.
Fault Sequence
The protection simulation is carried out for each fault event. All fault observations of the fault event
are simulated in the network at the specified time. All element switch times are likewise simulated.
If the pickup time of a protection device is permanently reached, this protection device trips and
determines also the time for the first time loop. For all other time steps of the stability calculation the
connection of the protection device that trips is opened. This process is repeated until all fault
currents equal 0.0.
All open connections are then reclosed for the consideration of the next fault sequence.
Starting the Protection Coordination Based on Stability Calculation
In order to start the new protection coordination, a new menu item has been provided in the main
menu at Calculate Protection Device Coordination as well as in the pop-up menu for fault
observations.
April 2015
15/36
SIEMENS
The current-dependent determination of the temperature is included in all calculation methods based
on the load flow.
April 2015
16/36
SIEMENS
In order to output the currents of current transformers, an EMT simulation must be carried out and
the dynamic data of the current transformer must be entered correctly.
The primary resistance, the secondary resistance and the main reactance at least are required. If
these attributes are not defined, it is not possible to include the current transformer in the dynamic
simulation and so no signal is plotted.
CIM 16
The CIM 16 import and export in PSS SINCAL have been further improved. There is now a Common
Grid Model Exchange Standard (CGMES) conformity declaration for PSS SINCAL 11.5. This was
completed on the basis of extensive tests and adaptions in order to ensure that the requirements of
the CGMES of 02.04.2014 are also fulfilled.
April 2015
17/36
SIEMENS
2.3
Pipe Networks
Temperature-Dependent Determination of Consumption
The ambient temperature is an essential factor for determining consumption when planning pipe
networks. During planning, the network is redesigned many times for maximum consumption.
However, as the maximum consumption for many consumers depends on the ambient temperature,
the maximum does not occur at the same time and the planning results in an overdesigned network.
A temperature-dependent consumption calculation makes it possible to include the simultaneity of
consumers in the planning. This enables a realistic network model with lower consumption values to
be produced. The results enable a weaker network to be designed or for existing networks to be
operated for longer without any expansion.
The temperature consumption characteristics are assigned directly at the consumer, and the air
temperature (= ambient temperature) is defined in the network level.
The following examples show the same consumption behavior for different power and temperature
settings at a design temperature of -20 degrees.
April 2015
18/36
SIEMENS
100
Tabs
0
-30
-20
-10
10
0
-30
-20
-10
10
-100
1.0
Tabs
0
-30
-20
-10
10
100
Trel
0
-10
April 2015
10
20
30
19/36
SIEMENS
0
-10
10
20
30
-100
1.0
Trel
0
-10
April 2015
10
20
30
20/36
SIEMENS
PSSNETOMAC
3.1
The Model Editor enables complex dynamic models to be created through the simple placing of
graphic blocks. The possible uses here are unlimited since all essential controller types and
controller blocks available in PSS NETOMAC are provided.
The models created here are saved in a special XMAC file which contains both the model graphics
as well as the required parameters for the model blocks. These XMAC models can be used in
PSS NETOMAC, PSS SINCAL and PSS E directly, i.e. without any further processing (e.g. compiling
or linking).
The following illustrates the creation, testing and use of models in order to convey how the new
Model Editor is used.
April 2015
21/36
SIEMENS
The first page of the wizard enables you to enter a name for the model as well as an additional
description. The Add model file to project option enables the new model to be integrated directly in
the currently opened PSS NETOMAC project. The second page of the wizard is used to define the
size of the drawing sheet for the new model. However, the default settings made here in the wizard
can be modified later at any time. Click Finish to create the new model file and also display it in the
Model Editor.
Nothing is displayed at first apart from a blank drawing sheet. However, this sheet is the work area
on which the new model is created. The most important functions for editing the model are provided
directly in the Toolbar of the Model Editor. This provides fast access to functions for marking
elements, for zooming the view, for creating blocks and connectors, as well as for setting model
parameters.
Other functions are provided in the Toolbox. Besides the functions provided in the toolbar, this
provides functions for creating supplementary graphic elements as well as for editing and aligning
elements.
The creation of a model starts normally with the definition of the output block. This defines the type of
April 2015
22/36
SIEMENS
the model. The following example shows the modeling of the standard ESAC8B voltage controller.
To do this, the Insert Output function is activated in the toolbar of the Model Editor.
It is then possible to position the output block at any position in the Model Editor by simply clicking
the required spot. This then displays a selection list in which all available output blocks are listed.
The list can be filtered by simply typing. The required output type can then be selected by doubleclicking or by pressing the Return key. After the selection list is closed, the new block is shown in the
Model Editor.
The new block in the Model Editor is already selected. The pink marking point indicates the position
where a connector can be added.
Double-click the output block to edit its parameters. This will open a data screen form in which all the
parameters of the block are listed in different tabs.
All input blocks are normally created after the output block is defined. Exactly the same procedure is
April 2015
23/36
SIEMENS
used again here. The Insert Input function is selected in the toolbar.
As previously described, the inputs are positioned in the Model Editor. Four machine sizes are
required for our controller: PSS, EC, VOEL and VUEL. The input block MACHINE is therefore
selected from the list and the first block is positioned in the Model Editor. The screen form is opened
by double-clicking the block and it is assigned the required parameters.
The process is repeated for the three other input blocks. This produces the following graphic in the
end.
Once the input blocks and the output block have been created, the actual controller blocks can be
created between them. A first order delay element is connected at the input with the compensated
excitation voltage (ECOMP). For this the Insert Block function first has to be activated in the toolbar.
April 2015
24/36
SIEMENS
As before, the block can then be inserted by clicking the required position in the Model Editor. The
block type DE1 is selected from the list.
After the selection list is closed, the block is displayed. We can now see four differently colored
marking points here.
The new block must then be connected with the ECOMP input block. The Insert Connector function
can be activated for this in the toolbar. This enables the creation of a connector between a block
output and a block input. However, the connector can be created even more easily by selecting the
block for which the connector is to be linked to the output. In our case this is the ECOMP input block.
(1)
(2)
The cursor symbol changes when the cursor is placed over the blue marking point (1). This indicates
that a connection to an input marking point can be created here directly by clicking and dragging. To
do this, place the cursor with the left mouse button held down over the required target block, in our
case over the delay element. The marking points where the connection is possible are indicated. The
April 2015
25/36
SIEMENS
connection is created (2) when the mouse button is released over a marking point.
The models can normally also be parameterized individually. With our delay element, the lag time
constant is to be variable. To do this, the dialog box for defining the model variables is opened either
via the toolbar or via Model Variables and Equations.
Any variable can be defined in the dialog box. The variables are identified with a unique name. A
description and also limit values can also be defined for greater efficiency. However, the value of the
variable is particularly important here. This is the default value, which is used if the variable is not
explicitly defined when the model is used.
The variable defined in this way can now be assigned in the delay element. To do this, the delay
element is double-clicked to open the relevant screen form, and the variable #TR is assigned to the
Lag time constant field.
The other blocks are created and parameterized in the same way until the model is complete.
April 2015
26/36
SIEMENS
An open loop test is normally carried out first of all in order to test the implementation of a model. In
this test a model is tested without any connection to the network. For this to be possible, the model
must be provided with all the necessary data. This data is defined in the Debug Properties dialog
box.
April 2015
27/36
SIEMENS
Inputs
The values at inputs and outputs can be predefined here for open loop operation.
It is also possible to define a jump function for the inputs. In other words, the value of the input is
changed over time. This enables the processing of the model to be checked when a jump
function occurs.
Outputs
A pre-defined output value can also be defined here for the open loop test for special controller
types.
Variables
This section contains exactly the same variables that were defined in the Variables and
Equations dialog box under Variables. Any values are assigned here to the variables for the
diagnostics. This makes it possible to check how the model behaves with different parameters.
Globals
The global model variables are listed in this section. Like the variables, these can also be
changed specially for the diagnostics in order to test how the model works with these settings.
Before the dynamic behavior of a model is tested, the structural correctness of the model has to be
tested. The Verify Model function is provided for this purpose. This checks whether all variables
used in the model have actually been defined and whether all blocks in the Model Editor are provided
with connectors. If there are any errors, messages are output in the message window.
As soon as all errors have been rectified in the model, this can be simulated dynamically with the
Run Model function. This checks the behavior of the model with a dynamic simulation in open loop
operation. The calculation time and the simulation time step are defined with the global debug
parameters #TSIM and #SIMDT. The signals of all outputs of the model are recorded and output in
an RES file. These can then be visualized in diagrams.
April 2015
28/36
SIEMENS
It can naturally also be used in PSS SINCAL. This incorporates the new XMAC models in exactly the
same ways as the MAC models. The required model is selected in a data screen form and the
parameters of the model can then be edited in an input list.
The XMAC models are used in PSS E in the same way as in PSS SINCAL. The required model can
be selected in a dialog box in the user interface. The parameters of the model are also offered for
editing in an input list.
3.2
April 2015
29/36
SIEMENS
programming languages and many applications. The following example shows the start of the load
flow calculation with a simple VBS script.
' Create an internal In-Process server
Set SimulateObj = WScript.CreateObject( "Netomac.Simulation" )
If SimulateObj is Nothing Then
WScript.Echo "Error: CreateObject Netomac.Simulation failed!"
WScript.Quit
End If
' Set net file
SimulateObj.AddDataFile 1, "D:\data\test.net"
' Start Loadflow calculation
SimulateObj.Run siCalcLoadFlow
If SimulateObj.Status <> siStatusFinished And _
SimulateObj.Status <> siStatusFinishedWithVariants Then
WScript.Echo "simulation failed!" & vbCrLf
Else
WScript.Echo "successfully finished!" & vbCrLf
End If
The following automation functions are provided for the user interface:
Application Object
o
Project Object
o
o
o
o
o
o
o
o
Export Object
o
o
o
o
o
April 2015
30/36
SIEMENS
o
o
o
o
The following automation functions are provided for the calculation methods:
Simulation Object
o
Init Initialization
Language Language
Messages Messages
Message Object
o
o
A detailed description is provided in the chapter Automation in the PSS NETOMAC System Manual.
Example scripts are also provided which show how the automation functions of the calculation
methods and user interface can be used. These examples are provided in the directory "{My
Documents}\PSS Files\Netomac\Batch".
April 2015
31/36
SIEMENS
3.3
User Interface
Enhancements in the Text Editor
The PSS NETOMAC input data is structured in columns. Due to this special structure of the input
data, the Overwrite mode is actually recommended for editing the data, since this keeps the column
layout unchanged.
The Delete and Insert Functions in Overwrite Mode were changed so that they do not "destroy"
the column layout. In other words, when selected text is deleted, it is not actually deleted but
replaced with the corresponding number of spaces. During an insert operation, the existing text is
inserted in the cursor position instead of the text buffer. This ensures that the column layout is
retained when editing the text in Overwrite mode. The normal Insert mode in the text editor is
naturally also available with the same functionality as before.
The text editor also features the new function for Selecting and Copying Blocks. The block
selection is activated by pressing the Alt key whilst selecting with the mouse.
A useful enhancement has been added for opening Include files (#lines) in the text editor. These can
be opened in the text editor as before directly via the pop-up menu, however, the predefined search
paths are now also included. In other words, models that were found by the calculation methods can
also be opened in the text editor via the pop-up menu.
The new Insert Model function is also provided in the pop-up menu of the text editor. This opens a
file selection dialog box. The model selected in the dialog box is then added in the text editor with all
the required parameters.
April 2015
32/36
SIEMENS
The dialog box for Comparing Diagram Pages was completely updated. It was previously only
possible to make a comparison using a PZD file. As this is no longer required in the new
PSS NETOMAC software, the comparison can now either be carried out with a user-defined diagram
page or as before with a PZD file.
Also new is the possibility to define a folder manually for the generated diagram pages. This function
was provided in the Compare Diagram Pages and Diagram Pages for Variants dialog boxes.
In order to improve the editing of diagrams, the pop-up menu of the diagram page now features a
function enabling all the signals assigned to a diagram to be deleted.
April 2015
33/36
SIEMENS
Multiple selection is now possible in the list of signals. This enables the selected signals to be
deleted easily.
A new button is now provided behind the field in which the description of the signal is defined. This
enables the generation of a default description using the properties of the selected signal. This allows
new signals to be assigned quickly and uniformly with descriptive texts.
The definition of signals was also improved. The machines differentiate between general machine
data, synchronous machine data and asynchronous machine data. Only the appropriate signal types
are offered for selection depending on the data selected. A selection list with the possible controller
types is offered for the output values of controllers (previously, the type always had to be correctly
entered in the input field).
The display of the selection and input fields in the dialog box was also optimized. Unnecessary
control elements (e.g. line data) are masked out in order to simplify the display.
3.4
Calculation Methods
Enhanced DTF Import
The DTF import function was enhanced to enable an improved connection to SCADA systems. The
idea here is that the SCADA system stores additional information in the DTF file which is processed
during the DTF import and then stored in a special SV (State Variables) file.
The main task of the SV file is to enable a connection of the topology of PSS NETOMAC with that of
the SCADA system. The most important characteristic data is also stored from the load flow result
from the SCADA system. This firstly enables the load flow results to be compared, and secondly
allows the node voltages to be used also as start values for the load flow calculation in
PSS NETOMAC.
The SV file is a simple ASCII file with two sections: Bus and Component.
April 2015
34/36
SIEMENS
Each line contains data for one node. The "NID" column defines the name of the node in
PSS NETOMAC. This is followed by the voltage and the voltage angle as status variables from the
SCADA system. Lastly, it is also possible to store an ID from the SCADA system.
The Component section stores additional information on the imported network elements:
Each line contains a network element. The topology of the network element in PSS NETOMAC is
defined in the columns "NID", "NID2" and "EID". The element type is stored for a better identification
of the element in the "AA" column. This is followed by the status variables for active and reactive
power from the SCADA system as well as the ID of the element in the SCADA system.
If there is a substitute model in the form of a MAC file, this should be given preference. In order
to implement it in PSS NETOMAC, the parameters are read from the MAC file and provided with
the data from the DYR file.
If there is no substitute model, the PSS E user model is connected directly to the NET file.
April 2015
35/36
SIEMENS
The following extract from PSS E DYR file shows a standard model (GENROU) and a user model
(SEMIPO):
If a substitute model is available, the MAC file is linked. The parameters for the model are read from
the MAC file and provided with the data from the DYR file:
If no substitute file is available as a MAC file, the direct import to the NET file is carried out. The
parameters of the model are set according to the DYR file and the model is also marked for later
linearization ("L" column ZZ).
The marking for linearization with the model connection enables a PSS E user model to be used in
NEVA. All selected models are then automatically linearized before eigenvalue analysis.
April 2015
36/36