Page Content
| Table of Contents | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
I/O Pins Format
Following table lists the useful path format to access different pins, parameters and variables of a GenUnit FMU.
No | Pin Description | Pin Type | Instruction | Examples |
1 | GenUnit Interface pins | I/O | GenUnitID/Pins_name | gen_1_1/dVREF |
2 | Component pins | O | GenUnitID/Component_name.Pins_name | gen_1_1/esst4b1.EFD |
3 | Sub-block pins | O | GenUnitID/Component_name.Sub-block_name.Pins_name | gen_1_1/esst4b1.add1.y |
4 | Component parameters/variables | O | GenUnitID/Component_name.Data_name | gen_1_1/esst4b1.VREF_0 |
5 | Sub-block parameters/variables | O | GenUnitID/Sub-block_name.Data_name | gen_1_1/esst4b1.gain1.K |
...
| color | #D3D3D3 |
|---|
...
Notes:
When using import from Excel Template, GenUnitID is the unique ID defined under name column of the GenUnit Excel page.
When using third party data formats, GenUnitID must follow the corresponding generator ID format as descried in subsections of Third Party Data Formats. For
...
example, in case of using PSS/e input files, GenUnitID for a GenUnit at bus 30 whose machine ID is G1 will
...
be gen_30_G1.
All component, parameter,
...
variable and pins names are case-sensitive.
Example
See the Pins
...
page in phasor11_HVDC.xls file in demo PHASOR-11 for Excel Template import
See the Pins
...
page in pins_v0.xls file in demo PHASOR-05 for PSS/e import.