Release Notes 13 - SimTecsincal.simtec.cc/13.5/ReleaseNotes-Eng.pdf · [HKEY_CURRENT_USER\SOFTWARE\Siemens\PDMS\13 ... The currently selected working environment is shown in a selection

$Page 1: Release Notes 13 - SimTecsincal.simtec.cc/13.5/ReleaseNotes-Eng.pdf · [HKEY_CURRENT_USER\SOFTWARE\Siemens\PDMS\13 ... The currently selected working environment is shown in a selection$
SIEMENS PSS SINCAL Platform 13.5

Release Information

April 2017 1/51

Release Information – PSS®SINCAL Platform 13.5

This document describes the most important enhancements and changes to the new program version. See

the product manuals for a more detailed description.

1 General Remarks 3

1.1 Licensing 3

1.2 PSS Tool 3

1.2.1 Enhanced Configuration for User Data 3

1.2.2 Loading of Registry Settings 3

1.2.3 General Deactivation of the Update Check 4

2 PSS®SINCAL 4

2.1 User Interface 4

2.1.1 Working Environments 4

2.1.2 New Function for Rapid Command Execution 5

2.1.3 Integrated Toolbar in the Graphics Editor 5

2.1.4 New Toolbar for Automation 6

2.1.5 New Tool Window for Automation 6

2.1.6 New Automation Functions 9

2.1.7 Enhanced Functions for Scenarios 11

2.1.8 Reduced Display of Branch Elements 12

2.2 Electrical Networks 13

2.2.1 New Hosting Capacity Calculation Module 13

2.2.2 Scenario Calculation for All Available Calculation Methods 20

2.2.3 Enhanced Contingency Analysis 21

2.2.4 Dynamic Simulation with NSN File 22

2.2.5 General Improvements for Protection Coordination 22

2.2.6 Enhanced Protection Analysis 23

2.2.7 Protection Routes for OC Protection Devices 27

2.2.8 Current Direction for Short Circuit Calculation and Protection Coordination 28

2.2.9 Integration of the Element Switch Times in the Breakers 29

2.2.10 New Functions for Measured Values 30

2.3 Pipe Networks 32

2.3.1 Scenarios 32


Release Information

April 2017 2/51

3 PSS®NETOMAC 32

3.1 User Interface 32

3.1.1 New Network Browser 32

3.1.2 Improved Debugging 34

3.1.3 Working Environments 37

3.1.4 New Function for Rapid Command Execution 37

3.2 Calculation Methods 38

3.2.1 Enhanced Functions in Eigenvalue Analysis 38

3.2.2 Optimization with Eigenvalue Analysis 41

3.2.3 Automation for Eigenvalue Analysis 46

3.2.4 Modified Eigenvalue Screening 47

3.2.5 Topological Querying in the Preprocessor 47

3.2.6 Sections for Structuring the Input Data Sets 48

3.2.7 Enhanced Malfunction Models in a DIS File 50

3.2.8 Switching of r Lines with DIS File 51


Release Information

April 2017 3/51

1 General Remarks

1.1 Licensing

PSS SINCAL 13.5 Platform uses the same license file as the preceding PSS SINCAL 13.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

PSS SINCAL Platform Support (phone +43 699 12364435, email [email protected]).

1.2 PSS Tool

1.2.1 Enhanced Configuration for User Data

The PSS SINCAL Platform stores the user-specific project data in the Microsoft "Documents"

directory provided for it. This is the optimum memory location for the project data, however, problems

may occur if the directory is synchronized with a server via a slow network connection.

A new setting was therefore provided by which the storing of the project data in the AppData

directory can be forced. The Save Projects in AppData directory option is provided in the

PSS Tool.

1.2.2 Loading of Registry Settings

Special settings are provided for the PSS SINCAL Platform, which can extensively change the

behavior and functions of the applications. These special settings cannot normally be entered via the

user interface but must be set in the Windows registry. The appropriate settings and related REG

files are provided by PSS SINCAL Support on request.

For the application to be simpler for normal users without administrator authorizations, a function for

loading the settings from the REG files was provided in the PSS Tool in the Administration tab. This

enables only settings for the PSS SINCAL Platform to be loaded from REG files.

mailto:[email protected]


Release Information

April 2017 4/51

1.2.3 General Deactivation of the Update Check

At the request of some system administrators the automatic update check of the applications of the

PSS SINCAL Platform with a central registry switch for the complete computer can now be

deactivated:

;

; Automatic check for updates on start-up of PSS SINCAL

; -1: Never (dword:ffffffff)

; 0: Always

; n: Days

[HKEY_CURRENT_USER\SOFTWARE\Siemens\SINCAL\13.5\Application]

"CheckUpdates"=dword:ffffffff

[HKEY_CURRENT_USER\SOFTWARE\Siemens\NETOMAC\13.5\Application]


[HKEY_CURRENT_USER\SOFTWARE\Siemens\PDMS\13.5\Application]


2 PSS®SINCAL

2.1 User Interface

2.1.1 Working Environments

PSS SINCAL provides a new function for switching complete working environments. This enables

any layouts of the application, e.g. combinations of toolbars and tool windows, to be switched simply

and straightforwardly. This makes it possible for the right working environment to be used for

different tasks (e.g. network creation, results evaluation etc.), i.e. precisely the tools required are

made available and not all the available tools, which would otherwise take up space or simply just get

in the way.

All available working environments are listed under View – Working Environments. Switching

between the working environments is possible by means of a simple selection.


Release Information

April 2017 5/51

The currently selected working environment is shown in a selection list in the standard toolbar.

Settings for the arrangement and visibility of toolbars and tool windows are automatically stored in

the current working environment. This can be selected at any time from the selection list. A dialog

box for defining additional user-defined working environments as well as for deleting working

environments can be called up via View – Working Environments – Customize.

2.1.2 New Function for Rapid Command Execution

PSS SINCAL provides a large number of commands in its menus. Although the commands are

arranged in logical groups, the calling of commands linked in submenus is not always convenient. It

may also occur that certain commands have to be "searched for" in the menus, particularly if these

are not frequently used. A new dialog box is therefore provided in all applications of the PSS SINCAL

Platform, by which commands can be started by entering the menu name. The dialog box can either

be opened via the toolbar or via Extras – Execute Command.

The dialog box contains all the commands available in the actual context, with their name and

symbol (if available). The entry field with a filter function enables the appropriate command to be

found simply and executed.

2.1.3 Integrated Toolbar in the Graphics Editor

The graphics editor is now provided with an integrated toolbar, which offers the most important

functions for editing in the network graphic. The new implementation corresponds to the toolbars that


Release Information

April 2017 6/51

were previously provided in the tabular view, in the diagram view and in the report view. In this way,

the functions that can be specially assigned to the graphics editor and only used there (e.g. selecting,

switching, graphic layer, object type etc.) can be provided precisely where they are required.

This change also prevents toolbars from taking up space on the user interface if they are not even

used.

2.1.4 New Toolbar for Automation

The new Macro toolbar with the following functions is provided in order to improve the control of

automation functions in the user interface:

Open macro explorer (this enables the macros available to be edited and executed)

Stop active macro (abort the macro recording)

Start recording (the called functions are recorded)

Stop recording (a script file is generated after a file name is entered)

2.1.5 New Tool Window for Automation

The new Macro Output tool window now makes it possible directly in the PSS SINCAL user

interface to interact with automation solutions. In this way, user entries can be entered directly in the

PSS SINCAL user interface during an automation process and the states or results can be visualized

if required. The automation will thus enable workflows to be created and embedded in the user

interface completely consistently.

The content of the tool window is completely defined with the automation functions. The following

example shows a variation of the known example "VoltageDrop" with user interactions.


Release Information

April 2017 7/51

The entry of the step width for increasing the load can be implemented in a text input control. After a

load was selected in the GUI, the calculation is started with the Calculate button.

The actual status of the script is displayed underneath in the Calculation area. Every time the

content is run, this is updated and any problems that occur are documented under Messages.

The following code snippets are designed to show how the written example can be programmed with

the new automation functions. An HTMLGUI object of the PSS SINCAL application is generated first

to activate the new automation window:

' Get the HTMLGUI object from the application

Dim HTMLGUI

Set HTMLGUI = SincalApp.GetHTMLGUI()

If HTMLGUI Is Nothing Then

WScript.Echo "Error: SincalApp.GetHTMLGUI failed!"

WScript.Quit

End If

' Reset the HTMLGUI

HTMLGUI.Reset()

HTMLGUI.OutputReset()

In this HTMLGUI, the available information and controls are then defined:

' Input form

HTMLGUI.Add Type_Title, "title_header", "VoltageDrop2", "title_header", ""

HTMLGUI.Add Type_Static, "static", "Calculate Voltage Drop", "Description", ""


Release Information

April 2017 8/51

' Input for delta

HTMLGUI.Add Type_Static, "STA1", "Delta P & Q", "", "html=<table><tr><td>"

HTMLGUI.Add Type_Edit, "delta", "", "0.1", "size=15px html=<td>"

HTMLGUI.Add Type_Static, "STA1", "", "", "<tr><td>"

' Submit & abort

HTMLGUI.Add Type_Button, "submit", "Calculate", "[CALC]", "submit nowrap html=<td>"

HTMLGUI.Add Type_Button, "abort", "Abort", "[ABORT]", "submit enabled=abort"

' Close

HTMLGUI.Add Type_Static, "STA1", "{HTML}", "", "html=</tr></table>"

HTMLGUI.Add Type_Static, "STA1", "<hr/>", "", ""

…

The interaction with the new automation window is programmed directly in the script. The function

waits here until the user clicks the button with the ID "[CALC]". The entered value is then fetched

from the text input control "delta".

' Wait for button press to start

Do While HTMLGUI.GetSubmit() <> "[CALC]"

WScript.Sleep 10

Loop

' Get data from control

Dim strDelta

strDelta = HTMLGUI.Value( "delta" )

The results are visualized for each completed load flow calculation with the following instructions:

HTMLGUI.OutputTitle "Calculation"

' Loop

HTMLGUI.OutputAdd Type_Static, "STA1", "Loop ", "html=<table><tr><td>"

HTMLGUI.OutputAdd Type_Static, "STA1", "", "html=<td>"

HTMLGUI.OutputAdd Type_Static, "loopcnt_value", "0", "html=<td>"

' P

HTMLGUI.OutputAdd Type_Static, "STA1", "P ", "html=<tr><td>"

HTMLGUI.OutputAdd Type_Static, "STA1", "=", "html=<td>"

HTMLGUI.OutputAdd Type_Static, "p_value", "0.0 MW", "html=<td>"

' Q

HTMLGUI.OutputAdd Type_Static, "STA1", "Q", "html=<tr><td>"

HTMLGUI.OutputAdd Type_Static, "STA1", "=", "html=<td>"

HTMLGUI.OutputAdd Type_Static, "q_value", "0.0 MVar", "html=<td>"

…

' Close table

HTMLGUI.OutputAdd Type_Static, "STA1", "{HTML}", "html=</table>"

HTMLGUI.OutputSync

HTMLGUI.Show()

As the code snippets make clear, the content in the new automation window can be freely designed

as required and also changed at any time. This makes it possible to design automation solutions so

that correct interactive workflows can be simulated that are run completely within the PSS SINCAL


Release Information

April 2017 9/51

user interface.

All new automation functions are documented in the System Manual in chapter Automation and the

example script "VoltageDrop2.vbs" shown here as an extract is also provided as part of the

PSS SINCAL 13.5 installation.

2.1.6 New Automation Functions

The user interface is also provided with new automation functions, which improve use in hosting

solutions with visualizations in PSS SINCAL.

Enhanced Selection Object

The selection object of the automation represents a collection of network elements and objects. For

more flexible use of this object, the identification methods were extensively increased.

The following code snippet shows the use of the enhanced selection object:

' Create a selection with multiple stuff and select it in GUI.

Set Selection = SincalDoc.GetSelection()

Selection.AddItemEx "Line", 1, SIASelectByID | SIASelectTerminal1

Selection.AddItemEx "Node", "SS1", SIASelectByShortName

Selection.AddItemEx "Breaker", "BB1", SIASelectByName

SincalDoc.Select Selection

As shown in the example, the identification of the element or object to be selected can be designed

very flexibly.

The first parameter determines the object to be selected. This supports nodes, network elements,

additional elements and supplementary graphic objects. The object type is selected via the name of

the appropriate database table. Alternatively, the internal RowType can also be used.

The object is identified with the next parameter. Different methods are used here: DBID, name, short

name, and graphic tag. The parameter is entered as a variant so that both texts as well as numbers

can be used.

The last attribute specifies the identification method. This parameter is implemented as a DWORD

mask. In other words, several options can be specified, such as whether only one terminal of the

element is to be selected.

Temporary Coloring for all Objects in the Network Graphic

Besides the already available functions for coloring nodes and network elements, a new function was

provided for the temporary coloring of any objects.

' Set temporary breaker color

SincalDoc.SetTempColor "Breaker", "BB1", 255, 128, 0, SIASelectByName

The new function was provided with variable parameters for identifying the object in the graphic.

These function in the same way as the selection object.


Release Information

April 2017 10/51

Changing of Persistent Properties with Automation

The most important graphic properties of the objects are now provided with the automation APIs.

This enables any changes to be carried out on these objects, in order, for example, to visualize

problems in the network with a different line width and object color.

The following illustration shows a line selected in the graphics editor with the graphical properties.

Precisely these properties can also be changed in the automation. The changes are carried out

persistently, i.e. precisely as if they are changed manually in the user interface.

In order to improve performance the elements to be changed must be identified once before

changing the attribute (similar to the selecting in the network graphic). For this the selection object is

used:

' Create selection

Dim Selection

Set Selection = SincalDoc.GetSelection()

' Add new objects to the selection

Selection.AddItemEx "Node", "SS1", SIASelectByName

Selection.AddItemEx "Element", "2T11", SIASelectByName

Selection.AddItemEx "Breaker", "Breaker L9-1", SIASelectByName

' Modfiy attributes

Selection.Property("Color") = RGB(255,0,255)

Selection.Property("SymbolFactor") = 250

Selection.Property("PenStyle") = "SOLID"

' Redraw

Selection.Invalidate

The new Property method is used to change the attributes in the network graphic. For this the

selection object is transferred and the attribute to be changed defined. The changes are then carried

out directly in the graphical objects of the network graphic and the corresponding database objects

are marked as modified. In other words, the changes are also stored in the database.

All new automation functions are documented in the System Manual in chapter Automation.


Release Information

April 2017 11/51

2.1.7 Enhanced Functions for Scenarios

In response to feedback from users, the functions of the scenarios were enhanced in many places in

order to further increase usability and flexibility.

Saving Variant Changes as Scenarios

This function enables any changes that were made in a variant to be stored in a scenario file. The

idea here is to carry out different modifications to network elements in the user interface. These

modifications are done in a variant. The variant comparison function enables the completed changes

to be evaluated. The new function is available here and enables the changes to be stored in a

scenario file.

Clicking the new button in the Variant Comparison window saves the changes shown in a scenario

file.

Variant of Scenario

This function enables the changes of a scenario file to be transferred to the physical database. A

subvariant is created for this and the changes from the scenario file are generated in the form of

variant changes in the database. To do this activate Insert – Scenario – Variant from Scenario.

This opens the following dialog box.

After the Scenario is selected and the Variant Name is entered, a subvariant is created by clicking

the Create button. The scenario is applied in this subvariant. In other words, the data of the individual

elements and switching states is transferred to the database according to the scenario files.


Release Information

April 2017 12/51

Additional Data in the Scenario

Previously only nodes and network elements could be saved in a scenario and network state file. The

function was enhanced so that the saving of attributes from the following tables is also possible:

• Calculation settings

• Reliability settings

• Network level

• Network area

• Breaker

• Measured values

2.1.8 Reduced Display of Branch Elements

The display functions of the branch elements were extended so that the display of terminals can be

reduced if required. With this display form the network element is not drawn completely but only the

terminal section at the node. The following illustration shows the principle:

The new display form draws the symbol of the network element several times, i.e. at each terminal.

This display form is particularly useful for networks that were created with automatic graphic

generation. This therefore completely prevents the overlap that normally occurs. It is also useful for

the display of stations. The station itself can be modeled in detail, but the connections to the other

stations can be visualized with the new terminal display form.

The new reduced display can be activated individually for each branch element via the Properties

window. The new Reduced Graphic option is provided for this.


Release Information

April 2017 13/51

2.2 Electrical Networks

2.2.1 New Hosting Capacity Calculation Module

The new PSS SINCAL "Hosting Capacity" calculation module (ICA) generates a temporary infeeder

or temporary load at selected nodes in an area of observation and increases the connection load

until one of the predefined background conditions is violated. This makes it possible to determine the

maximum connection load at the selected nodes in the area of observation without having to make

changes to the existing network.


Release Information

April 2017 14/51

The following illustration shows the operating principle:

The area of observation forms the basis for all checks in the calculation process. As already

mentioned, a temporary infeeder or temporary load with a varied power value is generated at each

selected node. The various calculations are carried out in order to make the checking of background

conditions possible.

A calculation with load profiles or operating points can be carried out if required in order to ensure

that the determined results are also correct with different network operating states. In this case the

entire calculation module is repeated for the different times/operating points.

The basic load flow without temporary infeeder/load is calculated for each calculation time. A

temporary infeeder/load is then generated at the selected nodes in succession and the connection

load is varied. The following calculations are then performed here to ensure that the set background

conditions are observed:

• Load flow:

Check of the utilization of all elements in the area of observation.

Check of the voltage limit values at all nodes in the area of observation.

Check of voltage changes (load flow with and without infeeder) at all nodes in the area of

observation.

Check for reverse feed via transformers at the boundaries of the area of observation.

• Short circuit:

Check of the permissible utilizations (iamax [%], ipmax [%]) of all elements in the area of

observation. For this a short circuit is calculated at the installation location and the utilization of

the elements is determined in the area of observation.

• Protection settings:

This is used to determine whether the protection devices still trip correctly with the new

infeeder/load.

DC

… Selected node

… Area of observation


Release Information

April 2017 15/51

If required, it is also possible to check whether a load tripping occurs.

The check is first carried out with the load flow calculation. This determines whether the currently

tested connection load at the examined installation location is at all permissible.

The check with the short circuit calculation is carried out after the load flow check is successfully

completed. If limit values are violated in the short circuit check, the load flow check is performed

again with a reduced connection load.

The protection settings are checked after the load flow and short circuit check. A simple check is

carried out here on the protection settings in order to minimize the calculation effort. This check is

carried out as soon as a maximum possible connection value is determined with load flow and short

circuit. A short circuit (according to the settings in the controller parameters) is calculated at each

node in the protection zone that limits the new infeeder/load. The currents registered by the

protection devices in the protection zone are recorded and a check is made whether these values

enable tripping in which the k factor is greater than or equal to the set value. If this criterion is not

fulfilled, the connection value is reduced and the check is repeated. The calculated minimum k factor

is recorded for each calculation time for each protection device.

Due to the number of tests with different calculation methods, it may take a very long time to

determine the hosting capacity. This is particularly the case if the check is carried out with a load

profile. This is illustrated with the following simple calculation example:

(number of nodes * calculation steps + additional calculations) * times from the profile

(300 * 20 + 4) * 96 = 576.384

Even a very small area of observation with 300 examined nodes and 96 different times requires more

than 500,000 calculations.

Example of Using the New Calculation Procedure

The hosting capacity check is started via Calculate – Load Flow – Hosting Capacity. This starts a

wizard, in which all essential control parameters for the calculation procedure can be defined step by

step.


Release Information

April 2017 16/51

The area of observation is defined on the first page of the wizard. It is possible to choose here

between a Network Area or a Network Element Group. In this example, the network area Basis-

Netzbereich is used. It is also possible to preselect the Network Levels of the area of observation

where a load/infeeder can be installed. In our case, connections are only to be made to nodes of the

network level 0.4 kV.

The data for the new element is defined on the second page of the wizard. The Type selection field

defines whether

• a DC infeeder or

• a load

is to be connected. In our example the connection of a DC infeeder must be examined at all nodes in

the area of observation. The Terminal Apparent Power section defines the data for the DC infeeder

to be connected. This is carried out by entering Smin and cosmin or Smax and cosmax. This

defines the range of the connection load to be examined by the calculation procedure. The accuracy

of this check is defined with the Sgen field.

The last page of the wizard is used to define the check conditions for the calculation procedure.

These conditions must be observed so that a connection load is classified as permissible.


Release Information

April 2017 17/51

The Observation section defines with the Type selection field which network observation is to be

carried out. The following options are available:

• Current state:

The current network state is used according to the settings at Load Flow – Calculation Settings.

• Load profile:

This check uses the load profile set in the Extended Load Flow – Calculation Settings.

• Operating points:

This check uses the operating points defined in the network.

In our example, only the current state is used for the check. This method is the fastest because far

fewer calculations are required than an examination with a load profile. The disadvantage, however,

is that the results are not so informative. The use of operating points that reflect the minimum, normal

and maximum operating states provides a compromise between calculation time and accuracy.

The Load Flow section is used to define for the load flow calculation the limit values that can occur

in the area of observation if the load is connected.

The Short Circuit section defines the limit values for the calculation of the short circuit that can occur

in the area of observation if a load is connected.

The Protection section makes it possible to activate an additional check of the tripping behavior of

the protection devices.

Click the Finish button to start the calculation. This may take a long time depending on the

observation type selected and the area of observation. The current calculation status is therefore

visualized in detail with a progress dialog box.


Release Information

April 2017 18/51

The result view is opened at the end of the calculation, and the results of the hosting capacity are

clearly visualized.

The Settings section of the results view is used to show the control parameters of the calculation.

The Results section visualizes the results of the calculation procedure in tabular form. Each row in

the table represents an installation location to which a load was connected.

The first column of the table contains the node name. This is implemented as a hyperlink and the

node can be selected in the graphics editor by clicking it. The maximum possible connection load is

then shown. This is followed by the values determined for the check criteria.

Those check criteria that have a limiting effect on the determination of the maximum connection load

are shown in orange.


Release Information

April 2017 19/51

The results can also be displayed directly in the network graphic in order to enable a better visual

assessment. For this the highlighting of the results can be activated in the Options dialog box of the

results view.

The following illustration shows the example network with the corresponding highlights:


Release Information

April 2017 20/51

The blue and green highlighting in the network indicates the connection points where a DC-infeeder

with a large power rating (>=3 MVA) can be connected. The yellow and red highlights indicate the

connection points where only smaller connection loads (<= 0.1 MVA) are possible.

2.2.2 Scenario Calculation for All Available Calculation Methods

This new function enables all available calculation methods to be used in conjunction with scenarios.

This is possible both in electrical networks as well as in pipe networks and offers the advantage of

allowing all results to be compared later with each other. In order to carry out the new scenario

calculation, the Calculate all Scenarios option is activated in the Calculation Settings dialog box.


Release Information

April 2017 21/51

For this, the complete network is loaded first of all in the virtual database. The defined scenarios are

processed in succession if the Consider for All Calculations with Scenarios is activated.

In other words, the selected calculation method is performed multiple times with the different

scenarios and the results are stored in a subvariant. The variants for the scenarios are created at the

end of the calculation. The name of the variant corresponds to the name of the scenario.

At the end of the calculation procedure, the results for all completed calculations are provided in the

database as subvariants. The results are evaluated by loading the required variant. The variant

comparison function can be used to compare different scenario results.

2.2.3 Enhanced Contingency Analysis

In response to requests from users, the following malfunction models were added to the contingency

analysis:

• Node Malfunction:

All elements connected to the nodes fail.

• Substation Malfunction:

All elements assigned to a substation fail.

These new malfunction models will simplify manual definition with a malfunction scenario since it is

no longer necessary to define all individual elements. The new malfunction models are linked in the

network browser in the same way as the network elements, i.e. nodes or stations can be marked in

the graphics editor and then simply assigned to a malfunction scenario.


Release Information

April 2017 22/51

2.2.4 Dynamic Simulation with NSN File

PSS SINCAL was provided with support for the new NSN file from PSS NETOMAC. This file can be

used to transfer a fully "calculated" load flow image of the network to the dynamic simulation in the

form of a complete admittance matrix.

The NSN file essentially eliminates the need for different modeling methods for controls and also

convergence problems because the load flow calculated by PSS SINCAL is used as an initial basis

for the dynamic simulation. With this as a basis, it is then possible to initialize models and machines

in PSS NETOMAC as well as define the stationary network state as an initial basis for further

processing.

The Use NSN option allows use to be activated in the calculation settings for the dynamic simulation.

2.2.5 General Improvements for Protection Coordination

It Diagrams

The instantaneous tripping of the OC protection devices is now always drawn up to the end of the

logarithmic diagram.

Enhanced Topology Information in Tabular View

In the Tabular View, the terminal is displayed at current transformers and the installation location of

the protection device and the node at voltage transformers.

Enhanced Results for DIFF Protection

The results tables of the protection coordination were enhanced so that important currents IDiff and


Release Information

April 2017 23/51

IStab are also provided for assessing the tripping behavior of DIFF devices. These currents are

displayed in the user interface in the protection device screen form for the results of the loops.

The currents can naturally only be calculated for DIFF devices, and so 0.0 is output for all OC and DI

devices.

2.2.6 Enhanced Protection Analysis

The protection analysis function provided since PSS SINCAL 13.0 has been enhanced in order to

further simplify and improve the automatic check of the protection settings.

Word Documentation of the Results

Word documentation is available for the results of the protection analysis. This is based on a

template document which is filled with the results of the protection analysis. Clicking the symbol in

the header of the results view enables the Word documentation to be created. The content and

scope here is the same as that of the results view, i.e. filter settings and display options are also

transferred to the documentation.


Release Information

April 2017 24/51

Enhanced Check for Backup Protection

An enhanced check of backup protection has been added to the check included in the protection

analysis. This enhanced check is carried out if the Enable malfunction devices option is activated.

This calculates for each protection route additional variations in which malfunctions occur at the

device at the start, at the end and both simultaneously. In this case, the fault on the protection route

must then be cleared by the backup devices.

The following illustration shows the results of the check. The route B05_SSE to E09_SSB was

checked in Area 1 several times:

• Devices at the start and end with a normal function

• Device at the start malfunctions (marked with an "x" behind the device)

• Device at the end malfunctions (marked with an "x" behind the device)

• Devices at the start and end malfunction (marked with an "x" behind the device)


Release Information

April 2017 25/51

As shown in the illustration, the primary protection is correctly configured and the malfunction can be

cleared if both devices function. However, if device E09_SSB malfunctions at the end, a correct

clearing by the backup protection is not possible.

A list of the backup devices of the protection zone can be called via the pop-up menu, and these

devices can alternatively be marked by clicking the hyperlink in the backup devices column.

Enhanced Checks in Protection Analysis

As part of the protection analysis, it is now possible to carry out enhanced checks using the clearing

time. This checks whether the clearing takes place either within a predefined time, or the maximum

permissible time is automatically determined by the reference short circuit current of lines I1s. The

new checks can be activated via the selection field in the Extended Checks section.

If a fault is cleared but the permissible clearing time is exceeded, the test result is documented as an

underfunction. For those checks where this occurs, the maximum permissible clearing time tmax is

shown in addition to the clearing time.


Release Information

April 2017 26/51

New Option to Restrict Protection Routes

The Stop at transformers checkbox is now provided in the Options dialog box. This enables the

protection routes to be limited. If this is activated, the determination of the protection routes is

stopped by transformers. This is designed to ensure that the calculation procedure can also be used

if the supply from the parent network is simulated with a "partitioned" slack node without protection

elements.

Improvements for Asymmetrical Networks

The determination of protection routes and protection zones for asymmetrical networks was

improved. For this the detection of protection zones containing simulations of symmetrical

connections with individual conductors was specially included in the algorithms for route

determination.

Enhanced Display Options

The new options improve the ability to adjust the display of the result view. The settings for this are

defined in the Options dialog box.

The new Display Topology makes it possible to select whether the protection device as before is to

be shown or the installation location (= terminal with node and element name).

Display in Table was also enhanced. It is now possible to select whether the clearing time, clearing

time and maximum permissible time tmax or the picked up and tripped devices are to be displayed.


Release Information

April 2017 27/51

The Scope of Representation section provides a new option in the selection list for adjusting the

display. This new option is particularly designed for checking the backup protection. In this way it is

possible to choose between the display of All Protection Routes, only the Primary Protection or

only the Backup Protection.

A small improvement was also made to improve the distinction between forward and reverse routes

in the table. Reverse routes are now automatically marked with a graphical symbol.

Visualization by Highlighting

An automatic highlighting of the protection zone selected in the table was implemented in the

network graphic in order to facilitate the evaluation of the results. This function can be activated via

the Options dialog box in the result view. The protection route is then highlighted in the network

graphic. The coloring corresponds to the display in the table. This makes it possible to quickly assess

in the network graphic where there are problems on the protection route.

The following illustration shows the selected protection route from device O04 to node N37. At the

end of the protection route there is an underfunction, which is then also be indicated directly in the

network graphic.

2.2.7 Protection Routes for OC Protection Devices

The protection routes have already been available in PSS SINCAL for several years, however, the

implementation was originally only designed for DI devices. The new version provides enhancements

to enable the protection routes to also be used for OC protection devices.

For each OC protection device, all possible protection routes belonging to the protection zone of the


Release Information

April 2017 28/51

device were determined in the network. A moving short circuit is then used to check up to which point

the registered currents cause tripping on I>, I>>or I>>>. The position of the short circuit point is

assigned here to each tripping zone and thus forms the basis for the visualization. A fixed current

value is not provided for the characteristic curve Ip but a range is covered instead. The current value

for tripping is therefore determined by a protection factor, which can be defined as required in

Calculation Settings – Protection Coordination in the Protection Route Factor field. This

protection factor is multiplied here by the factor with the smallest value of the characteristic curve in

order to obtain the current for determining the range.

The following illustration shows the protection route for an OC protection device of type 7SJ512, on

which the characteristic curve tripping Ip and the high set tripping I>> is active.

Starting from the installation location of the protection device, the red highlight indicates the range of

the instantaneous tripping I>> and the violet highlight the range of the characteristic curve tripping Ip.

2.2.8 Current Direction for Short Circuit Calculation and Protection

Coordination

The short circuit current is displayed with element arrows on conductors for the short circuit

calculation with current and voltage distribution for a malfunction location. This enables the actual

power flow in the short circuit to be visually assessed more easily.

The display of the protection devices was improved to display the current direction for the protection

coordination. This shows an enhanced overlay in the picked-up protection devices, which represents

the registered fault current. The following illustration shows the new display form.


Release Information

April 2017 29/51

The new ProtDevice – Show Current checkbox is provided in the View Options to activate the

enhanced display.

2.2.9 Integration of the Element Switch Times in the Breakers

The element switch times were originally implemented for simulating the switching actions for the

dynamic simulation. However, simulation as a virtual object to enable switching at any point is not

ideal. This causes problems with couplings to third-party systems, and the transfer or overwriting of a

switching state of the network, which is normally modeled with switches, is also not possible with the

element switch times.

The element switch times were therefore completely removed, and the data for the switching actions

in dynamic simulation is now directly assigned to the switches. The switches can be placed, in the

same way as with the element switch times, at the terminals of all network elements. However, this

describes "real" equipment that also has technical data and the switch position is considered in all

calculation modules.

The new Dynamics tab is now provided at the switch in order to define the switching actions for the

dynamic simulation. Any number of switching measures can be assigned in the Switch Time


Release Information

April 2017 30/51

Dynamics list. This enable extended switch sequences, such as Open-Close-Open, to also be

modeled easily.

The switching action is edited by double-clicking an element in the list. This then opens the Switch

Time Dynamics dialog box in which all parameters for the switching measure can be defined.

The switching measures can also be displayed in the network graphic. If the appropriate fields of the

switch times are activated at Annotation and Filter, the on and off switching actions are displayed at

the annotation of the breakers.

2.2.10 New Functions for Measured Values

New attributes were added to the measured values in order to improve usability in coupling solutions

in particular. These attributes are not included in the calculation methods, but improve the

documentation. The new attributes are available in the screen forms and the Tabular View in the user

interface.


Release Information

April 2017 31/51

A new function has also been provided in the pop-up menu of the measured values. This now also

allows an individual Master Resource for coupling solutions to be assigned in the user interface.

It is also now possible to apply the actual load flow result as a measured value. This new function is

available via Tools – Determining Data – Apply Measurement Data. This opens a dialog box for

applying the load flow results of the terminal on which the measuring device is placed.

The dialog box makes it possible to set the form in which the values are to be assigned (current or

power). All the measured values present in the network can either be considered or only those that

are selected in the graphics editor.

In order to simplify the editing of those measured values that are not graphically displayed, all

assigned measured values can now be edited in the pop-up menu via Additional Data –

Measurement Data.


Release Information

April 2017 32/51

2.3 Pipe Networks

2.3.1 Scenarios

The scenarios are now also available in gas, water or heating networks in the same way as in

electrical networks.

The functionality here is exactly the same as those in electrical networks, i.e. there is a special

scenario calculation that functions in the same way as the operating point calculation. All active

scenarios are calculated in succession and the results are provided with the corresponding scenario

identification in the database. This information, such as the operating point results, can then be

analyzed interactively in the user interface.

It is also possible to change the existing network temporarily with any scenario and then carry out

any calculations as required. For this, the required scenario to be included in the calculation is

defined in the calculation settings.

It is also possible to calculate the marked scenarios automatically in succession and save the results

in subvariants.

3 PSS®NETOMAC

3.1 User Interface

3.1.1 New Network Browser

PSS NETOMAC now provides a network browser with a topology display that functions in the same

way as the PSS SINCAL network browser. The new network browser improves the analysis of

complex networks, since the topological interrelationships are easier to identify. This is useful both

when working in the NET file with the text editor and also when evaluating results in tables and

diagrams.

The following illustration shows the network browser with the example project "entso-

e_example_case_3".


Release Information

April 2017 33/51

A toolbar is provided at the top, by which the most important functions can be called:

Go to the location

Refresh

Options

Help

This includes a filter line by which the display range can be restricted.

The upper list in the network browser shows all elements of the network, i.e. nodes and network

elements. These are grouped by type.

The lower list shows the topology. This is automatically synchronized with the upper list, i.e. the

display is always adapted according to the selection in the upper list. The illustration above shows

the marked line "S-GEN" and therefore this selection is also displayed in the lower list. The nodes of

the network element and also the other elements connected to these nodes are displayed. This

provides an impression which topological connections are present.

Double-clicking in the lower list enables nodes and elements to be selected in the upper list. The

display in both lists then changes according to the selection made. This makes it possible to navigate

through the entire network.

Another function is the localization of input data. In this way it is possible to move from a selected

network element in the network browser directly to the location in the NET or MAC file of a project at

which the network element was defined. This function can either be called via the integrated toolbar

or via Go to Location in the pop-up menu.


Release Information

April 2017 34/51

The filling of the network browser is a complex process because the data structures of the network

can only be fully interpreted using the PSS NETOMAC calculation kernel. Filling can also take a few

seconds, which is comparable with the time required for reading in the network for the load flow

calculation. The network browser is therefore not updated automatically but only manually. The

Refresh button is provided for this in the toolbar. The information determined as part of the update is

stored in a file in the project directory and made available until this is overwritten with a new update.

3.1.2 Improved Debugging

The debugging of controllers provided in PSS NETOMAC is required in order to analyze problems in

complex BOSL models. This enables the BOSL code to be executed in steps, as with a development

environment, and the inputs and outputs of the individual blocks analyzed.

The debug functionality has been enhanced and the ergonomics extensively improved in order to

further increase the usability of this frequently required function when creating new controllers and

analyzing problems with existing ones.

The controller debugging can be activated via the calculation parameters at Output – Control –

Diagnostics.

If the option is active, the debugging is automatically activated on determining the start conditions of

a controller when a load flow calculation or a dynamic simulation is started.

The debugging is controlled here with the Simulation window, which provides all important context-

related functions. Debugging is started by selecting the required controller. Instead of selecting in

stages in dialog operation, the following selection is now provided:


Release Information

April 2017 35/51

This enables a controller to be selected either by type or name. The further selection lists then

contain all the relevant selection values. This therefore reduces controller selection to a single

selection step.

The actual debugging starts according to this selection. The debugged controller is displayed as a

BOSL source code in the text editor.

The line with the currently processed BOSL block is indicated with a red highlight. The input value X1

and the output value Y1 of the block are output behind the line.

The right of the displayed calculation window shows general information on the controller. This

includes the type of controller and also its name. The actual iteration is also displayed.


Release Information

April 2017 36/51

All the actions for debugging are provided below this for selection in the form of radio buttons. The

following actions can be selected:

• Stepwise

An individual instruction is carried out.

• Next breakpoint

The controller is run starting from the current BOSL block up to the next breakpoint.

• Last breakpoint

The controller is run starting from the current BOSL block to the last breakpoint.

• End of iteration

The controller is run up to the end of the current iteration.

• Last iteration

The controller is run up to the last controller iteration, i.e. up to when this is convergent.

• Select another controller

This enables a new controller to be selected for debugging. The currently debugged controller is

run up to the end and the controller selection is then displayed in the calculation tool window.

• Proceed without debugging

This action ends debugging and the calculation is continued.

The Protocol option activates an enhanced output of all inputs and outputs of blocks to the LST file.

The selected action is executed either by clicking the Continue button or by pressing the F6 key.

Breakpoints are also provided to simplify debugging. These can be defined directly in the source

code of the displayed controller with the text editor. For this the pop-up menu is opened on the left

which then provides functions for editing breakpoints.

When the Next breakpoint action is called, the controller is run up to this set breakpoint. The output

values are output here behind the BOSL lines. This makes it possible to assess how the signals are

processed in the controller.


Release Information

April 2017 37/51

3.1.3 Working Environments

Like PSS SINCAL, PSS NETOMAC also provides the new function for switching complete working

environments. This enables any layouts of the application, e.g. combinations of toolbars and tool

windows, to be switched simply and straightforwardly. If required, different working environments can

be assigned to a shortcut in order to make switching more efficient.

3.1.4 New Function for Rapid Command Execution

A new dialog box is provided in the user interface, by which commands can be started by entering

the menu name. The dialog box can either be opened via the toolbar or via Extras – Execute

Command.

The dialog box contains all the commands available in the actual context, with their name and

symbol (if available). The entry field with a filter function enables the appropriate command to be

found simply and executed.


Release Information

April 2017 38/51

3.2 Calculation Methods

3.2.1 Enhanced Functions in Eigenvalue Analysis

Functional Enhancements

The range of functions for eigenvalue analysis was extended in order to also support networks with

the following elements:

• DFIG or U2_DFIG

• Torsion

The DFIGs were completely revised in the eigenvalue analysis. The following illustration shows the

result comparison of transfer function (red) with the simulation results in the time range (blue). As can

be seen, there is virtually a 100 % match.

The support of the torsion system in the eigenvalue analysis provided in the simulation is also new.

The same entries apply here as for the simulation. The following illustration shows the evaluation of

the transfer function.


Release Information

April 2017 39/51

Another improvement is the processing of parallel machines at the same node. This produces

multiple eigenvalues that cannot be processed effectively. To solve these problems, the parallel

machines are now automatically combined for the eigenvalue analysis.

Corrections

The following blocks were corrected in order to ensure that they supply correct results in the

eigenvalue analysis:

• ROTATE

• SAT

• RI/AA

• AA/RI

The inputs (INPUTs) of powers, torques, currents of machines were not related in the same way as

in the simulation section. Therefore all results with these kinds of INPUTs were not correct. This

problem has now been rectified.

Another problem with the order of input data was also rectified. Blocks present later in the controller

data sets were previously regarded as constant since the index was not yet known. A power system

stabilizer (PSS), for example, that was arranged according to the associated voltage controller, was

therefore ineffective in the eigenvalue analysis. This was also rectified.

Output of the State Variables

This new function also enables all the state variables included in the eigenvalue analysis to be

analyzed using their contribution. The benefit of this analysis is that it is also possible to determine


Release Information

April 2017 40/51

which state variables have the greatest effect on specific eigenvalue, without having a detailed

knowledge of the network.

This calculation is activated via the State Variables button in the simulation window.

The result of the calculation is shown in the Tabular View. Each characteristic value is listed with its

contribution in the eigenvalue. This also makes it clear that the problem is the data volume: Number

of modes x number of state variables defines the result quantity.

To control this problem of volume, the Mode overview diagram can be used to reduce the scope of

the analysis interactively. For this the Zoom function can be used in the diagram to simply select the

section of the image containing the eigenvalues to be analyzed. Only these modes are then

considered when determining the state variables.

Simplified Handling with Residues/Transfer Function

The Residues/Transfer function analysis enables enhanced evaluations of the eigenvectors to be

carried out, for example for the optimum positioning of controllers to be determined.

The transfer function G(s) is defined as follows:

)s(

)s()s( U

YG

The selection of the variables Y(s) and U(s) in the calculation window when examining an object has

been simplified. The following illustration analyzes whether the use of a power system stabilizer

(PSS) is useful at machine G10. This requires the analysis of the following transfer function:

PSS)s( V

G


Release Information

April 2017 41/51

The machine to be examined is selected for this, as well as the analyzed variable "Rotor Speed" at

Y(s).

The same object is used for U(s) as for Y(s) by selecting type "=Y(s)". Only the variable to be

analyzed then has to be selected. In the example illustrated this is the excitation voltage.

3.2.2 Optimization with Eigenvalue Analysis

The eigenvalue analysis (EVA) enables small signal stability to be examined in virtually any networks

and problematic points can be found relatively quickly with the extensive evaluation options.

However, the difficulty here is to find suitable solutions that can rectify these problems. The

optimization of controller parameters can thus be relatively difficult since settings frequently interact

with each other. The manually "optimized" parameters therefore have to be checked with an

eigenvalue analysis, in order to determine whether the setting supplies the required result. This a

relatively complex iterative process, which can be very time consuming with large networks.

Precisely this problem has to be solved with the new optimization with eigenvalue analysis. For this

the optimization function provided in PSS NETOMAC was also made useful in conjunction with

eigenvalue analysis.

The optimization calculation with EVA is now provided in PSS NETOMAC like the already available

optimizations. In other words, the parameters to be varied are defined in the CTL file and a target

function defined in the NET file via BOSL.

The actual optimization is started via Tools – Optimization. The Eigenvalues option is offered for

this in the simulation window.


Release Information

April 2017 42/51

The optimization itself is carried out based on the results of the eigenvalue analysis. The following

new BOSL blocks enable the results to be accessed as part of the optimization:

• Eigenval – Eigenvalue

o Sigma/Omega for mode no.

o Sigma/Omega with max. participation factor

o Sigma/Omega with minimum damping

o Sigma/Omega with max. EV_right

o Sigma/Omega with max. EV_left

• Mode – Mode

o Mode with min. damping

o Sigma/Omega with max. participation factor

o Mode with max. EV_right

o Mode with max. EV_left

• EV_Right – Right Eigenvector

o Magnitude/angle for mode no.

o Magnitude/angle with max. participation factor

o Magnitude/angle with minimum damping

o Magnitude/angle with max. EV_right

o Magnitude/angle with max. EV_left

• EV_Left – Left Eigenvector






• Particip – Participation Factor






• Residue – Residue






The new blocks are therefore used in the target function of the optimization in order to determine

whether the variation of a parameter brings an improvement.


Release Information

April 2017 43/51

The following extract from the NET file shows the use of the new BOSL blocks:

The 1st line defines the BOSL block and the subsequent line defines the component. The following

types are possible here:

• M – Machine

• N – Node

• B – Branch

• Y – Controller

Individual parameters can be queried according to type. With the machines, these are the machine

variables, with the nodes these are voltages and frequency and with branches the power and the

impedances.

The following example shows a NEVA controller which is called after eigenvalue analysis as part of

the optimization. This determines Sigma and frequency of the mode with minimum damping (HZ1 =

1):

Precisely these values are accessed in the target function of the optimization and thus determine

whether the optimization of the damping brings an improvement.


Release Information

April 2017 44/51

Either the Quasi Newton and Mod.-Powell option can be selected for the optimization procedure.

The following illustration shows this selection in the calculation window, as well as the output basis of

the eigenvalues in the example network.

The mode overview diagram shows an eigenvalue with Sigma > 0 rad/sec. This increasing oscillation

has to be damped better by varying the parameters of the controller. At the end of the optimization an

eigenvalue with Sigma = – 0.51 rad/sec is determined.


Release Information

April 2017 45/51

To achieve this improved damping, the parameters P1 and P2 were varied in the voltage controller of

the machine.

The optimized parameters are output in the LST file.


Release Information

April 2017 46/51

3.2.3 Automation for Eigenvalue Analysis

The functions of the eigenvalue analysis are now available via the automation APIs so that these can

be used in the users' applications/tools. Use here is exactly the same as for the other automation

functions provided for calculation modules.

The following code snippet shows the new automation APIs:

Dim ptrNetoSimSrv ' Netomac-Simulation Server

Dim ptrNetoSim ' Netomac-Simulation

Set ptrNetoSimSrv = WScript.CreateObject( "Netomac.SimulationSrv" )

If ptrNetoSimSrv Is Nothing Then

WScript.Quit

End If

Set ptrNetoSim = ptrNetoSimSrv.GetSimulation()

If ptrNetoSim Is Nothing Then

' TODO: Add your error handler code here

WScript.Quit

End If

' Simulation parameters

ptrNetoSim.Parameter("NEVA_CALC_METHOD") = "QR" ' "QR", "SUBSP" or "DPOLE"

ptrNetoSim.Parameter("NEVA_SIGMA_MIN") = -2.0

ptrNetoSim.Parameter("NEVA_SIGMA_MAX") = 0.5

ptrNetoSim.Parameter("NEVA_FREQ_MIN") = 0.1

ptrNetoSim.Parameter("NEVA_FREQ_MAX") = 1.0

ptrNetoSim.Parameter("NEVA_ZETA_MAX") = -99

ptrNetoSim.Parameter("NEVA_ZETA_CHART") = -5

ptrNetoSim.Parameter("NEVA_SIGMA_START") = 0.0

ptrNetoSim.Parameter("NEVA_TR_TIME_MAX") = 10.0

ptrNetoSim.Parameter("NEVA_FR_FREQ_DELTA") = 0.001

ptrNetoSim.Parameter("NEVA_FR_FREQ_MIN") = 0.01

ptrNetoSim.Parameter("NEVA_FR_FREQ_MAX") = 2.0

' Commands to be executed

ptrNetoSim.Parameter("NEVA_COMMAND") = "METHOD=MODAL

ANALYSIS;TYPE=SYNCHRONOUSMACHINE;DATA=3;OBJECT=GEN;"

ptrNetoSim.Parameter("NEVA_COMMAND") = "METHOD=TRANSFER FUNCTION ANALYSIS;Y(s)

TYPE=SYNCHRONOUSMACHINE;Y(s) DATA=3;Y(s) OBJECT=GEN;U(s) TYPE=SYNCHRONOUSMACHINE;U(s)

DATA=GEN;U(s) OBJECT=10; CHART=EXPORT_TO_FILE=RESXX;"

ptrNetoSim.Parameter("NEVA_COMMAND") = "METHOD=RESIDUES;Y(s) TYPE=SYNCHRONOUSMACHINE;Y(s)

DATA=GEN;Y(s) OBJECT=10;U(s) TYPE=SYNCHRONOUSMACHINE;U(s) DATA=9;U(s) OBJECT=10;"

' Start EVA Simulation

ptrNetoSim.Run CalcEigenvalues

As shown in the code snippet, all significant control parameters can be transferred to the calculation

object. The process here is the same as with the other automation functions provided in

PSS NETOMAC. It is also possible to define "commands" which execute the actions that are

normally started interactively in the user interface in dialog mode. The above example shows the

execution of three different actions: Mode activities, transfer function and residues. The diagrams of

the transfer analysis can be exported in the PSS NETOMAC GUI to any file using the automation


Release Information

April 2017 47/51

function and thus made available for later evaluations and further processing. To simplify the use, the

entry of the analyzed objects as well as controllers and controller variables are provided with the

readable name instead of the internal number.

In order to simplify the use of the EVA automation, the macro recorder was also enhanced in the

user interface. This records the actions carried out by the user in interactive dialog operation and

transfers this to the automation script.

3.2.4 Modified Eigenvalue Screening

Eigenvalue screening (EVS) is a simplified form for examining the small signal behavior of the

network. This determines the mode distribution in the S plane on the basis of a dynamic simulation

with a defined disturbance. This makes it possible to obtain a simple and particularly fast assessment

of eigenvalues without having to carry out any complex und time consuming calculation with the

eigenvalue analysis.

The implementation of the eigenvalue screening and also the integration in the user interface was

now designed in the same way as for eigenvalue analysis. In other words, all parameters are set via

the calculation settings (CTL file).

The control parameters in the dialog box refer to eigenvalue analysis, in addition to those settings

specially required for eigenvalue screening.

The settings for the Mode Overview diagram (S plane) are likewise defined in the dialog box. These

are the same settings that are also available with eigenvalue analysis. An option is also provided for

controlling whether the display is to be carried out with or without an integrated mode overview table.

3.2.5 Topological Querying in the Preprocessor

This new function enables the use of topological queries in the preprocessor section of

PSS NETOMAC in order to create the network or also controllers accordingly. For example, this

enables the controllers of a machine to be masked out of the data sets if the machine is not present.


Release Information

April 2017 48/51

The following code snippet shows how the topological queries are carried out:

@@IF(EXISTS_MACHINE(MachineUID)) THEN

@@ENDIF EXISTS

@@IF(.NOT.EXISTS_MACHINE(MachineUID)) THEN

@@ENDIF EXISTS

@@IF(EXISTS_NODE(NodeUID)) THEN

@@ENDIF EXISTS

@@IF(.NOT.EXISTS_NODE(NodeUID)) THEN

@@ENDIF EXISTS

@@IF(EXISTS_ELEMENT(ElementUID)) THEN

@@ENDIF EXISTS

@@IF(.NOT.EXISTS_ELEMENT(ElementUID)) THEN

@@ENDIF EXISTS

As shown in the code snippet, it is possible to query the existence of machines, nodes and elements.

These queries must always be terminated with an ENDIF EXISTS statement.

Nested queries are permissible, such as:

@@IF(EXISTS_MACHINE(MachineUID)) THEN

$ read in if MachineUID is present

$ …

@@IF(EXISTS_NODE(NodeUID)) THEN

$ read in if MachineUID and NodeUID are present

$ …

@@ENDIF EXISTS

@@ENDIF EXISTS

# Variables must not be used with the UIDs.

3.2.6 Sections for Structuring the Input Data Sets

The use of sections is a new alternative variant for structuring the input data. These start with the ID

[[Section]] and end either with [[End_Section]] or only with [[End]].

The following sections are defined (not case sensitive).

[[plot_header]]

[[plot_data]]

[[pzd_data]]

[[feeder]]

[[machines]]

[[torques]]

[[network]]

[[nonlinearities]]

[[models]]

[[models_during_loadflow]]

[[universal machines]]


Release Information

April 2017 49/51

[[models_in_2-system]]

[[models_in_0-system]]

[[extras_in_2-system]]

[[extras_in_0-system]]

[[simulation_events]] !required if load flow or simulation events

[[loadflow_events]]

[[fault_elements]]

The use of the new [[Sections]] is optional. The former standard input sequence as well as the

section selection with ## can still be used. Mixing is also possible. The data sets can thus be built

with the standard input sequence and the selection of partial data sets can be made with sections. It

is only important to note that the E code must not be used inside a section if used.

The sections do not have to be arranged in the standard input sequence if only the new sections are

used. Sections can also be empty.

The following code snippet illustrates the use of sections with a small NET file:

****Sample for sections

$1......12......23......3AA1....12....23....34....45....56....67...78...89...9ZZ

$ Variables

@@ #T_IN=.11

...

[[Simulation_Events]]

...

@ #NODE1 = 'MOT_K '!Shortcircuit Node

@ #NODE2 = 'MOT_K '!Voltage Criterium Node

@ #T1 = .1 !Faultduration (sec)

@ #TEND = 10000. !Time to next Event (sec)

*#NODE2 #T1 03

S#NODE1 1. ENDE

*#NODE1 #TEND66

S#NODE1 0. ENDE

[[End]]

$1......12......23......3AA1....12....23....34....45....56....67...78...89...9ZZ

[[Feeder]]

EINSP 110 110 1000 .1 1

[[End]]

[[Network]]

SNetz EINSP 1 00

TMOT_OS TRAFO Yy110 110 10 .1 10

Tmess 0010 10

RNetz MOT_OS SWITCH 1.0E-6 110

Rmess MOT_US SHUNT 1.E-6 10

[[End Network]]

@@IF(EXISTS_NODE(mess))THEN

[[Network]]

VMOT_US DFIG 8 6 -10.

AMOT_OS MOT_K $N62 1. .1 1.0 110

[[End Network]]


Release Information

April 2017 50/51

@@ENDIF EXISTS

[[Models_during_Loadflow]]

[[End]]

[[Models]]

$ Controller Data

U_DFIG DFIG N

#volt.mac

DREHZ DFIG N

#md.mac

$

[[End Models]]

$1......12......23......3AA1....12....23....34....45....56....67...78...89...9ZZ

[[Machines]]

A DFIG DFIG_Test

1<Unsat> Md_Cont 10

2 U_DFIG 1.000 .008 .08

3 .008 .08 .3247 .145 .001

4MOT_US PQ

[[End Machines]]

3.2.7 Enhanced Malfunction Models in a DIS File

The definition of the disturbance criteria in the DIS file was enhanced with a line on which the fault

location can be positioned. For this a new definition line is provided in the DIS file, which defines the

partitioned branch in front of the actual fault definition.

[[Fault_Elements]]

$1.......2.......3.......A.1.....2.....3.....4.....5.....6.....7....8....9....Z.

$ UID Left Right FZweig FKno F0Kno Delta

$ [%]

L L814 L1 R1 FZ1 FK1 10

[[End Fault_Elements]]

The line to be partitioned is identified via the Name3 field. The HZ6 field defines the position of the

fault location starting from the start node. HZ1 and HZ2 define switch branches at the start and end

of the line. The HZ3 field defines the fault branch and HZ4 the fault node.

The branch and node names defined here can be used in the subsequent disturbance lines. This has

the advantage that the disturbance scenarios can be simply "inherited" on different lines.

Line

Right Left

Fault


Release Information

April 2017 51/51

3.2.8 Switching of r Lines with DIS File

The r-lines present in PSS NETOMAC are used to describe the static switching state of the network.

These are impedance-free and are therefore well suited for simulating switches. A special function is

also provided by which the r lines can be simply switched on and off via the ZZ column. The switch

position is then the basis for the load flow and also the further dynamic simulation.

In order to make switching with the r-lines more flexible and straightforward, it is now also possible to

switch with the DIS file for the load flow calculation. The new section [[Loadflow_Events]] in the DIS

file is used for this.

[[Loadflow_Events]]

$1.......2.......3.......A.1.....2.....3.....4.....5.....6.....7....8....9....Z.

L814 OF

L815 ON

[[End Loadflow_Events]]