Generic PV plant

Description and demonstration of the capabilities of the Generic PV Plant component.


The usage of microgrids has been steadily increasing over the last few years, and so has been the need to model and test their control system. In short, the microgrid field is currently on the rise, accompanied by a growing need for more efficient microgrid components.

To address this need, Typhoon HIL software currently deploys three types of components in its Microgrid Library: Switching, Average, and Generic, all of which are ready for use and for their respective applications. Switching components are mainly used in situations where real-world converter testing is required at the system level, where highly detailed models of power electronics are required to interface with PWM outputs. Average components are used when you want to have a realistic emulation of dynamics without the need for a PWM interface and serious optimization of the use of HIL hardware resources. The main use of generic components is to allow you easily parametrize through provided nominal values, without a need for adjusting the details of the grid filter and control. As such, Generic components are especially convenient in grid stability and system integration studies, where the main interest is parameterization of the component with desired nominal values. The main purpose of these components is to emulate the characteristic behaviour of the grid connected PV plant in the following scenarios:
  • active power curtailment and reactive power control
  • plant state machine, faults detection, and limits according to nominal values
  • ramping functionalities for reference signals and MPPT

This model demonstrates how you can use the Generic PV Plant components and what the advantages of these componets are for your own applications in this domain.

Model description

The model consists of a PV Power Plant (Generic) connected to the Grid. There are also two user interface blocks which are intended to be used for sending and reading signals associated with Grid and PV Power Plant components respectively.

Figure 1: PV plant connected on the grid

Generic components, unlike switching and average components, have inputs and defined outputs within the user interface. The PV Power Plant (Generic) component consists of two main parts: a high-level control subsystem and a low-level control subsystem with the power stage and all the measurements. You only need to change the parameters on the mask of the component while all the inner logic and the power stage itself will be automatically scaled according to the parameters.

Figure 2: PV plant (generic) properties

User Interface components make it easier for you to use Generic components. Unlike common microgrid components where you need to define all inputs and outputs, within the user interface all the inputs and outputs necessary for the operation of PV plant components are already defined for you. This is shown fully implemented in PV Power Plant (generic) UI. All that you have to do is just connect the Generic component with the appropriate User Interface block. Within this block, there are also some reserved inputs and outputs that can be used for additional functionalities and improvements. In addition to the usual inputs and outputs set by the Power Management System (PMS), there are external inputs related to external plant factors. In this case, the external inputs are temperature and solar irradiation.

Figure 3: PV Power Plant (generic) UI


This application comes with a pre-built SCADA panel shown in Figure 4. It offers the most essential user interface elements (widgets) to monitor and interact with the simulation at runtime, allowing you to further customize it according to your needs.

The PV Power Plant operates only in the grid following mode which eliminates the possibility for droop control, since this is only possible in a component which can operate in grid-forming mode (e.g. in a battery inverter). The inverter has four operational states:
  • Disabled – the state when the inverter is turned off and the main circuit breaker is open.
  • Starting up - the state of the inverter between the moment of enabling signal activation and the moment when the inverter starts operating, e.g. the synchronization time.
  • Running – the state when the inverter is operating.
  • Error – the state when a fault is detected. If the inverter is in the error state, in order to start the plant again, it is necessary to reset the alarm.

    Figure 4: SCADA_panel

PV Power Plant Interface is shown in Figure 5. The left of the figure shows the Inverter Control and Status where you can read the state of the inverter as well as get information if protection is active. Here you can also read the measurements of active, reactive and apparent power, as well as the power factor. Parameters, such as temperature and irradiance, can be changed in the External commands group.

Figure 5: PV Plant Power Interface

One of the main advantages of generic components is the included protection. Here the following types of protection are impelmented:
  • Overcurrent protection – this type of protection occurs when some of the input phase currents are 1.5 times over the maximum allowed instantaneous current.
  • Grid voltage is out of range - appears in case when the grid voltage is outside the specified relative range [0.5, 1.5] pu. This protection is active in grid-following mode.
  • Grid frequency is out of range – activation of this type of protection is caused by grid frequency which is outside the specific relative range [0.5, 1.5] pu. 
  • Overpower protection – this type of protection kicks in when the measured apparent power is 1.2 times greater than the maximum allowed apparent power.

    Figure 6: Grid voltage out of range protection is activated

Figure 7: Frequency out of range protection is activated

Table 1. Minimum requirements
Typhoon HIL files

examples\models\microgrid\pv plant\pv plant (generic)

pv plant gen.tse,

pv plant gen.cus 

Minimum hardware requirements
No. of HIL devices 1
HIL device model HIL402
Device configuration 1

Test automation

We don’t have a test automation for this example yet. Let us know if you wish to contribute and we will gladly have you signed on the application note!


[1] Jovana Markovic