Page Content
| Table of Contents | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
In this case the FMUs can be easily linked to the internal solver of ePHASORSIM by only adding a new tab to the Excel file for each type of FMUs. Therefore, the following steps must be taken:
Add a new tab in the Excel input file with exactly the same name as the FMU
Declare FMU parameter names and their values in the new tab
Note: in this case there is no need to check the 'FMUGlossary.csv' file
Add New Tab(s)
For each GenUnit type in the network data, an Excel sheet should be created with the same name as the GenUnit. For example, the figure below shows two new tabs, GENROU and GENROU_EXST1, are added to the existing Excel. At each FMU tab multiple instances of the same FMU can be declared. For example in the figure below, there are 2 instances of GENROU in the corresponding tab which each of them has a unique name.
...
Note: There
...
are no limits in the number of FMU instances, except the existing memory usage.
...
Insert FMU Data
The first row of the FMU tab is the header to define the ID of FMU, its connection point to the power system, and name of its parameters. The header must begin with two keywords “name” and “bus0”, and it is followed by all the required parameter names of the GenUnit, see the above figure as an example.
The following rows will contain the values for the corresponding parameters.
...
| color | #D3D3D3 |
|---|
...
Notes:
“name” value must be unique.
“bus0” specifies the bus ID to which the GenUnit’s “bus0” power pin is connected (see Power Pin). If a GenUnit has more than one power pin such as the HVDC component featured in the phasor11_HVDC example model, the header will instead begin with “name”, “bus0”, “bus1”, ..., “busN”, followed by the rest of the FMU parameters.
The parameter names must be exactly the same as the ones used in Modelica model of the GenUnit.