-
Notifications
You must be signed in to change notification settings - Fork 16
1. Quickstart Guide Excel
The excel sheet testcases.xlsx is used as the model-independent toolbox interface to input model-specific information and set up different cases for simulation with the MTB. The file contains 3 different sets of predefined cases used by Energinet to review models in relation to the RfG (Requirements for Generators), to the DCC (Demand Connection Code) and for unit testing. It is possible to add or disable cases as needed, either in the predefined case sets and in separate custom cases set that is also available. The excel sheet testcases.xlsx consists of the following tabs:
- Settings
- Area values
- RfG cases
- DCC cases
- Unit cases
- Custom cases
- Event types
- RfG cases overview
- DCC cases overview
- Unit cases overview
The Settings tab and the cases tabs will be explained in depth below. A short description for the other tabs are as follows - The tab Area values contain handling of requirement values based on the plant-specific information such as the connection point. The tab Event types describes the different types of events that the testbench is able to perform, with detail as to how the X1 and X2 is used for the specific event type. The tabs RfG cases-, DCC cases- and Unit cases overview all describe the pre-defined test cases available in each of the cases sheets.
Note
The following are new for MTB 2.0:
-
Default P available associated with the signal mtb_s_pavail_pu, the Event Type Pavail, and the initial power available at t=0, Pavail0
-
Default Q(U) droop associated with the signal mtb_s_qudroop, the Event Type QUdroop, and the initial Q(U) droop setting at t=0, QUdroop0. This previously was a constant V droop associated with the constant mtb_c_vdroop
-
Main Transformer Grounded is associated with the signal mtb_s_mtrfrgnd and initial main transformer grounding configuration, MtrfrGnd0. No event is associated with this signal.
The Settings tab is the interface to input model-specific information. Most of the inputs are straight forward and self-explanatory with additional explaination in the comment column.
Caution
The projectname must not contain any spaces as this causes an error in the plotter Python script later on, as it is not able to find the path of the output files.
The first setting is the Casegroup, this is important as it selects which of the pre-defined case sets that are run, either the RfG-, the DCC- or the Unit case set. The Area is selected based on if the plant is connected in **DK1 **(Continental Europe) or **DK2 **(Nordic).
There are three types of SCR and corresponding X/R-ratios:
- min, corresponding to the minimum short-circuit level.
- tuning, an intermediate short-circuit level between the minimum and the maximum short-circuit level. If the tuning parameters are not needed, leaving it blank will result in the MTB omitting them from the simulation.
- max, corresponding to the maximum short-circuit level.
PSCAD Initialization time and PF flat time dictates the simulation run time before the first event is activated. When looking at the event definition in the cases tabs, time 0 will always be offset by these times in PSCAD and PowerFactory respectively. The times do not have to be identical, as the plotter tool will offset the time accordingly, ensuring the first event will always happen at time 0 when plotting.
The testcases excel document contains four tabs for defining cases, 3 of them being the predefined sets as described earlier. The last is for setup of additional custom cases, however the former 3 can also be edited as desired.
For each of the 3 predefined sets of cases, an overview tab is also included that provides an overall description of each case.
Each of the tabs will look similar to the example below.
Note
The following are new for MTB 2.0
-
Pavail0, the initial power available at t=0, with Default, refering to the Default P available value on the Settings Tab
-
QUdroop0, the initial Q(U) droop setting at t=0, with Default, refering to the Default Q(U) droop value on the Settings Tab
-
MtrfrGnd0, the initial main transformer grounding configuration at t=0, with Default, refering to the Main Transformer Grounded value on the Settings Tab
Each row represents an individual case that is referred to by its,
- Rank: Rank number
- RMS: Run case in RMS model? Is to be set either TRUE or FALSE.
- EMT: Run case in EMT model? Is to be set either TRUE or FALSE.
- Name: Name of the case.
The is followed by the Initial settings at the start of the simulation,
- U0: The initial voltage level in p.u.
- P0: The initial active power reference in p.u.
- Pavail0: The initial active power available in p.u.
- Pmode: The initial active power control mode
- Qmode: The initial reactive power control mode
- Qref0: The initial reactive power reference (is set based on Qmode)
- QUdroop0: The initial reactive power reference(is set based on Qmode)
- SCR0: The initial SCR (-1 equals stiff grid)
- XR0: The initial X/R ratio
- MtrfrGnd0: The main transformer initial grounding configuration
- Simulationtime: Simulation time of the case. Automatically accounts for initialization time.
This is then followed by up to 12 Events that can be specified for a specific Case.
The Events are defined by,
- type: The type of Event
- time: The Event time, i.e. when the Event will be activated
- X1: Action depending on Event_n.type, see section 1.3.4
- X2: Action depending on Event_n.type, see section 1.3.4
The different type of Events and the actions performed by _Event_n.X1 and _Event_n.X1, are descripted in the Event type tab,
See below for the most common type of Events,
Note
Qref depends on in which Qmode the plant are operated in.
- If Qmode = Q: Then Qref is equal to the reactive power reference in p.u. as measured at the PoC
- If Qmode = Q(U): Then Qref is equal to the voltage reference at the PoC in p.u.
- If Qmode = PF: The Qref is equal to the Power Factor (PF) of the plant as measured at the PoC
Let us use case rank 86 as an example. This case is used to simulate a 3ph-fault and a change in the SCR when the fault is cleared to represent e.g. a faulty line being disconnected.
-
Firstly, the case is only active, if the plant is not a DSO connection, since the row is colored slightly purple. If it isn't a DSO connection, the case will be run for both RMS and EMT (column B and C).
-
The case will be named "ION_RfG_Fault_3_SCR" (column D) and will start with an initial voltage equal to U0, in this case set based on Uc from the Settings tab (column E). In this case corresponding to 1.065 p.u. in relation to the Un.
-
The active power will initialize at 1 p.u. (column F) and the plant should only have the LFSM active power control mode active (column G).
-
The reactive power control mode is set as the plants default control mode (column H), which is defined in the Settings tab, with a reference of 0 (column I).
-
SCR (column J) and X/R ratio (column O) will be equal to the SCR tuning and X/R tuning defined in the Settings tab. In this case 20 and 15 respectively.
-
Lastly the simulation time will be 15 seconds (column L) in addition to whatever is defined as the PF flat time in the Settings tab.
-
The case consists of two events.
-
Event 1 is a 3ph-fault (column M) set to start at time 0 (column N), this corresponds to the moment the flat run period is finished.
- X1 is set as 5% (column O) to indicate that the 3ph-fault should result in a residual voltage of 5% or 0.05 p.u. at POC, while
- X2 is set as 0.150 (column P) to indicate that the Event should last for 150 ms.
-
Event 2 is a change in the SCR (column Q) that will occur at time 0.149 (column R), which is 0.149 seconds after the flat run period.
-
X1 is set as the SCR min (column S) and
-
X2 is set as the X/R ratio min (column T)
In this case both are equal to 10. This results in the SCR and X/R ratio changing after 149 ms from when the flat run period has finished.
-
-
The simulation will continue for a total of 15 seconds, excluding the flat run period defined in the Settings tab.
For further questions or help, please check if the README or the Quickstart Guides contains the answer.
Otherwise, please contact the Energinet simulation model team: simuleringsmodeller@energinet.dk