Generators

1. Overview

This chapter covers on-site electricity generation: solar panels (Generator:PVWatts and Generator:Photovoltaic), the load centers that make EnergyPlus simulate them (ElectricLoadCenter:Distribution), the generator lists those load centers hold (ElectricLoadCenter:Generators), and the inverters that convert the panels’ direct current (ElectricLoadCenter:Inverter:PVWatts and ElectricLoadCenter:Inverter:Simple). All of them are objects in the object dialog, opened the way any other object is (EP3 Interface and Model Settings).

Panels do nothing in EnergyPlus until a load center lists them, so every model with panels needs three things besides the panels themselves: a generator list that names them, a load center that uses the list, and an inverter when the load center’s bus needs one. EP3 writes any of these that you have not made (§6), so a model with only a generator is still simulated.

The chapter assumes the building’s roofs, walls, and shading surfaces already exist (Creating Building Geometry). Shading surfaces that carry panels, such as canopies, are drawn as shading collections (Creating Building Geometry).

2. The two panel models

  • Generator:PVWatts is the simple model. It takes a rated DC System Capacity in watts, a Module Type, an Array Type, and the system losses. It uses the tilt, orientation, and shading of the surface it sits on, or its own tilt and azimuth when it has no surface.
  • Generator:Photovoltaic is the detailed model. It takes its efficiency from a PhotovoltaicPerformance:* object (named in Module Performance Name) and its tilt and shading from its surface.

Both have the same Applies To field and the same collection choices (§3).

A Generator:PVWatts can also have no surface at all. Set Array Geometry Type to TiltAzimuth and give a tilt and an azimuth. It is then one generator with its own orientation, and the surface and collection fields are hidden.

3. Where the panels go

Applies To has two settings:

  • OneSurface puts the panels on the one surface named in Surface Name: a roof, a wall, or a shading surface. The Surface Name list shows each shading surface under the name it is exported with, such as “Shading 1 (shading)”. EP3 keeps the surface itself, not the name, so renaming a shading group does not break the choice. A shading surface that faces down, or that lets light through, gets no panel, as in a collection; for a surface that faces down, EP3 asks whether to reverse it.
  • Collection puts panels on every exterior wall and roof surface and every shading surface of a collection. EP3 writes one generator for each matching surface when it exports, named after the surface (for example “Roof PV Roof 1”), so you set the panels up once. Nothing replicated is stored in the model.

Panels are never put on windows or doors, whatever the collection. They also skip shading that lets light through and surfaces that are too small (§3.3).

When you switch Applies To to Collection and no collection is chosen yet, a window asks you to pick one from the same choices as the Collection field. Cancel leaves Applies To on Collection with no collection chosen, and the Collection field stays available to choose one later.

3.1 The collection choices

The Collection field offers:

Choice What it takes
Site The exterior walls and roofs of every building, and all site and building shading surfaces.
A Building The exterior walls and roofs of that building and the collections inside it, including its shading.
One Floor See below.
One Wall collection Only the exterior walls in that collection.
One Roof collection Only the roof surfaces in that collection, including the overhang faces of the roof.
Site shading groups The shading groups that belong to the site rather than to a building.
Building shading groups Only the shading groups you created under a building. Roof overhangs are not shading groups.

Site and Building always include the collections nested in them. A single Wall or Roof collection never does. A Floor collection holds the floor’s own surfaces, which never take panels; when it has no exterior surface of its own, EP3 reads it as nested and takes the collections inside it and the Wall and Roof collections that were grown from that floor. The Matching surfaces line under the dialog says so when that happens.

The two shading group choices show a checkbox for each shading group of that kind, all ticked. Untick the ones that should not carry panels. All groups ticks them all again. EP3 remembers the groups you untick, not the ones you leave ticked, so a shading group you add later is ticked automatically.

3.2 Facing and tilt

Two graphics under the collection narrow which of its surfaces get panels. Click a part of a graphic to switch it off or on. Everything is on by default, and All directions and All tilts put a graphic back to all.

Facing is a compass of eight 45 degree sectors: N, NE, E, SE, S, SW, W, and NW. The sectors are true directions, so South means true south. The compass has true north at the top, with a yellow arrow pointing to it, and the sectors never move. A small faint “plan up” marker shows where the top of the plan lies. It is turned by the building’s North Axis, and the caption under the compass says so (for example “Plan up is 30° clockwise from north”), which relates the compass to the drawing. A model rotated for a baseline comparison therefore picks different surfaces in each rotation, because the marker follows the EEM’s North Axis while the sectors stay put.

Each sector starts at its first angle and runs up to, but not including, the next. N is 337.5 up to 22.5 degrees clockwise from true north, NE is 22.5 up to 67.5, E is 67.5 up to 112.5, and so on. An angle exactly on a boundary belongs to the sector it starts, so 22.5 degrees is NE.

Tilt is a quarter circle of four bands, from flat along the bottom to a wall up the side:

Band Tilt
Flat 0 up to 10 degrees
Low slope 10 up to 30 degrees
Steep 30 up to 60 degrees
Wall 60 to 90 degrees

Exactly 10 degrees is low slope, exactly 30 is steep, and exactly 60 and 90 are wall. A shading surface that faces down gets panels once you reverse it (§3.3); a wall or roof that faces down never does. A flat surface (tilt under 10 degrees) has no direction, so it passes any facing selection.

Under the graphics, the dialog says how many surfaces match and how much area they have, and lights those surfaces in the 3D view while the dialog is open. If nothing matches, no generator is written and Model Validation says so. §3.3 lists the surfaces that never get panels.

3.3 Surfaces that never get panels

Three rules apply to a collection’s surfaces besides facing and tilt. The dialog counts the surfaces each one leaves out.

  • Shading that lets light through. A shading surface whose transmittance schedule is anything but always 0 gets no panels. A surface with no schedule, or with a schedule that is 0 all year, is opaque and can carry them. A schedule EP3 cannot read hour by hour (a yearly or file schedule) counts as letting light through. See Creating Building Geometry for setting a shading surface’s transmittance.
  • Minimum face area. Minimum Face Area leaves out any surface smaller than it. Blank means 1 m² (about 10.8 ft²), so slivers and tiny faces carry no panels. Set it to 0 to allow every size. It applies to walls and roofs as well as shading, and it is a setting of the generator, so an EEM can change it.
  • Faces that look down. A shading surface drawn facing down, such as a canopy drawn from above with its points running clockwise, gets no panels. When you pick a collection that has such horizontal surfaces, EP3 asks, for example, “4 horizontal surfaces in the selected group face down — reverse them so they face up?” Yes reverses those surfaces in your model as one undo step, so they face up and can carry panels. No leaves them as drawn, and they carry no panels. The matching line keeps a Reverse 4 down-facing faces button while any remain, so you can change your mind. EP3 does not offer a surface when another face of the same shading group lies above it: the underside of a closed shading box, for example, stays facing down and gets no panels, while the box’s top and sides can. A roof’s own overhang faces are never offered for reversing.

Under the graphics, the dialog says how many surfaces match and how many were left out for each reason.

3.3 Panels in the 3D view

Every PV generator written in the active EEM draws blue panels on the surfaces it applies to: a dark blue fill with a faint grid of cells. This covers a Generator:Photovoltaic and a PVWatts whose geometry is Surface, on a single surface or on a collection. The panels cover the area your capacity needs, not the whole surface:

  • For a PVWatts, the panel area is the DC System Capacity divided by 1 kW/m2 and the module efficiency of its Module Type (Standard 19 percent, Premium 21, Thin film 18). On a collection the capacity is shared as the Capacity On A Collection setting says.
  • For a Photovoltaic, the panels cover the performance object’s fraction of surface area with active solar cells.

The panels are drawn as a smaller copy of the surface, centred on it, so a surface that needs half its area shows panels over the middle of it. A surface that needs more than its whole area is covered completely. Use the sun button in the view toolbar to show or hide all the panels.

3.4 Arrays with their own tilt and azimuth

A PVWatts with Array Geometry Type: TiltAzimuth is an unshaded array with no location, so it is not drawn in 3D; its dialog says so. Its Surface Name, Applies To and collection fields are hidden, because EnergyPlus ignores them for this geometry, and the surface name is not written to the EnergyPlus file. With Surface geometry, the Tilt Angle and Azimuth Angle fields are hidden instead: EnergyPlus takes them from the surface, and the dialog shows the tilt and azimuth it will use (the range, for a collection).

4. Capacity of a PVWatts on a collection

A PVWatts has a rated DC System Capacity in watts. Capacity On A Collection says how it applies to the many generators written for a collection:

  • SharedByArea (the default): the capacity is the total for the whole collection, shared out by surface area. The total stays what you typed.
  • EachCopy: every generator gets the capacity.
  • PerArea: the capacity is watts per square meter of surface.

4.1 Zone multipliers

EnergyPlus applies a zone’s multiplier to a Generator:Photovoltaic on one of its surfaces, but not to a Generator:PVWatts. EP3 therefore multiplies a PVWatts for you: the multiplier is the one its zone is simulated with: the floor’s Floor Multiplier times the zone’s own multiplier. SharedByArea shares the typed total by area times multiplier, so the total stays the building’s and the multiplier is not applied twice. EachCopy multiplies each generator’s capacity. PerArea is watts per square meter times area times multiplier. A Generator:Photovoltaic is left alone, since EnergyPlus multiplies it.

5. Load centers and inverters

Open ElectricLoadCenter:Distribution in the object dialog:

  • The Generators table under the fields lists the panels in the load center, in order, with how many generators each one is written as. Add a generator from the list below the table, remove one, or move it up or down. The table edits the load center’s generator list; a load center with no generators is not written.
  • Create PVWatts inverter and Create simple inverter make an inverter and name it in the load center, and set the bus to direct current with an inverter. Use the PVWatts inverter only with Generator:PVWatts generators: EnergyPlus stops with an error when a PVWatts inverter shares a load center with a Generator:Photovoltaic. A simple inverter takes both.

The load center’s dialog always shows its generator list and its inverter as links that open them.

Two load centers may share one generator list, but a generator can be in only one load center, so list each generator once.

6. The automatic load center

A generator dialog always lists the objects it is connected to: its load center, its generator list, and its inverter, each as a link that opens it. When no load center object is connected to the generator, the three rows read Automatic, and the dialog says: “Load center and generator list are required for EnergyPlus simulation. There are no existing objects connected to this PV generator. EP3 will create default required objects on translation to EnergyPlus (epJSON). You can make these objects editable.” The last words are a button. A generator that is only partly set up reads Missing for the piece it lacks, with a short line such as Missing: load center, Missing: inverter, or two together, and the same button. Each piece is checked on its own:

  • the generator list is automatic when no list names the generator (nothing is set up yet);
  • the load center is missing when no load center uses a list that holds the generator, for example after the load center was deleted and its list left behind;
  • the inverter is missing when a load center holding the generator has a direct current with inverter bus and names no inverter.

When a piece is automatic or missing, EP3 writes it at export. A generator in no list gets a list, a load center (“EP3 PVWatts Load Center” or “EP3 PV Load Center”, one per kind of generator, baseload), and an inverter. A list whose load center is gone gets a load center. A load center with no inverter gets one. Nothing is stored in the model, and Model Validation reports each generator that relies on this.

Press make these objects editable (in the generator’s dialog, the load center’s dialog, or Model Validation) to store the automatic and missing pieces as objects of your own. It creates only what is missing and reuses what exists, such as a list left behind and an inverter no load center uses. Afterward the connection links in the dialog show the new objects, with “(new)” after each one it made (a reused one has no mark), and each name opens that object’s dialog. In Model Validation the objects made are listed under “Made for you”, because that dialog has no connection list.

7. Generators in EEMs

A generator, like any object, can be switched off in an EEM. In that EEM it drops out of its generator list, and a list left with no generators, the load center that uses it, and an inverter that only that load center used, are not written. To compare a model with and without panels, switch the generators off in one EEM. The facing and tilt choices, the collection, and the capacity are ordinary fields too, so an EEM can change them. Setting them in an EEM adds nothing to the model; the generators for each surface are written at export.

8. Checking the generators

Model Validation lists, under HVAC, a Photovoltaics and Load Centers section: generators that rely on an automatic or missing piece, a collection that matches no surface, a PVWatts inverter with a Generator:Photovoltaic, and a direct current bus with no inverter. After a simulation, the generators’ produced electricity is in the output variables Generator Produced DC Electricity Energy and Electric Load Center Produced Electricity Energy (Viewing and Interpreting Results). The load center’s total is the direct current side, before the inverter.

When you import a file with a generator list, the list and its generators come in as they are, each on its own surface (Importing EnergyPlus Files). Generators that EP3 wrote one per surface of a collection are then restored: the import looks for generators of one kind that differ only by surface (and capacity), sit in the same generator list, and together cover exactly the surfaces that one collection with one facing and tilt choice would give. It picks the most specific such collection (a single Roof, Wall, or Floor collection first, then shading groups with the groups left out, then a Building, then the Site), prefers no facing or tilt choice over one when both give the same surfaces, and collapses them into one generator. A name such as “Roof PV Roof 1” is restored as “Roof PV”; without that pattern the common start of the names is used. A PVWatts capacity is restored as EachCopy when every generator has the same capacity (after dividing out its zone multiplier), or as SharedByArea with the sum as the total when the capacities follow surface area times multiplier; otherwise the generators are left alone. A group that does not match exactly, for example because one copy was deleted from the file, stays as single-surface generators and is never matched approximately. The import report has a line for each group restored (for example “12 generators ‘Roof PV …’ restored as one PVWatts on Roof collection ‘Roof 1’”) and for each group that could not be, with the reason. Shading groups come back as the groups they were (see Importing EnergyPlus Files), so a generator that leaves a shading group out is restored with that group left out. A list row that names a generator type EP3 does not import (a combustion turbine, for example) is left out, and the import report says which.

4.1 How much a surface can hold

For a PVWatts on a surface, the dialog works out the most capacity the surface (or the collection’s matched surfaces) can hold: its area times 1000 W per square meter times the efficiency of the Module Type (Standard 19 percent, Premium 21, Thin film 18). Leave DC System Capacity blank and that maximum is used, and the dialog shows it as the default with “(from area)”. If you enter more than the maximum, the dialog shows a red line such as “Exceeds what 53.9 m2 of standard panels can hold (10232 W)”, and Model Validation reports a warning. EnergyPlus accepts the larger capacity, so it is still written as you entered it. A little over (0.5 percent) is allowed for rounding. For a collection, “Shared by area” is checked against the total, “Each copy” against the smallest surface, and “Per area” against the watts per square meter. A tilt and azimuth array has no area, so it has no default and no check. A Photovoltaic with the Simple performance object takes its output from the surface area and the cell fraction and efficiency you enter, so it has no capacity to check.

This handbook is also built into EP3 (Help), where its EnergyPlus links open the EnergyPlus Reference. Technical specifications · Book a demo

EP3 for Mac

Tell us you'd use it on a Mac. It helps us decide what to build next, and we'll email you when it's ready.

Which computers would you run it on?
Mac is included because you asked about EP3 for Mac
Send me occasional news about EP3 software

Sending…

Thanks!

We've noted that you'd like EP3 on a Mac. Our reply is on its way to : check your inbox, and your spam folder if it isn't there in a few minutes.