Layout

Maximizing placement and half tables

Two options that fit more capacity onto an awkward boundary, what each costs in regularity, and when a regular plant is worth more than the extra tables.

A regular grid on an irregular site leaves ground unused. A table is placed only where it fits entirely inside the usable area, so every diagonal fence, every curve and every row end rejects the last position and leaves a wedge of ground with nothing on it. Two options recover that ground, and both are off by default.

They recover it in different ways. Maximize placement moves each row sideways until it touches the boundary. Add half tables drops a smaller unit into the gap that is left. You can use either, or both, and in both cases what you buy is capacity and what you pay is regularity.

OptionDefaultWhat it changesWhat it costs
Maximize placementOffEach row is positioned independently, hugging the boundary edgeTable columns do not line up across rows; longer to compute on a large site
Add half tablesOffA shorter unit holding whole strings is dropped wherever a full one will not fitA second unit type in the plant, counted separately

Both live at the bottom of the MMS-Table Configuration card on the Array tab — or the Tracker Configuration card in a tracker design — alongside the geometry they modify. See Table configuration and Tracker configuration.

Maximize placement

With the option off, the whole grid shares one origin. Every row starts from the same east–west position, so the tables form clean vertical columns from the top of the plant to the bottom — and every row is limited by the same starting offset, whether or not that offset suits the boundary at that latitude.

With the option on, each row is positioned independently, pushed up against the exact boundary edge it meets. A row crossing a narrow part of the site starts further in; a row crossing a wide part starts further out. Where the fence runs diagonally, or curves, the row ends follow it instead of stopping short at a shared column line, and extra tables fit into the wedges the shared origin had wasted.

The gain is largest where the boundary is least like a rectangle: an irregular parcel, a curved river frontage, a site with a long diagonal edge. On a rectangular site aligned east–west there is nothing for the option to recover, because the shared origin already reaches both edges.

What it costs

Table columns will not be vertically aligned across rows. That is not a cosmetic detail:

  • The drawing reads as untidy. On the general arrangement sheet of the drawing set, and in its DXF twin, the north–south lines that a reviewer's eye follows are broken. Rows step in and out relative to each other.
  • Generation takes longer on a large site. Every row is fitted against the boundary separately instead of being derived from a single grid.

When to use it

Turn it on when capacity is the binding constraint and the boundary is genuinely irregular — a site where the target capacity does not fit, and where a few per cent more tables decides whether the project works. Leave it off when you are producing a drawing for a bid, or when the plant will be built and maintained on a repeating block pattern.

The honest way to decide is to run the site both ways. Generate once with the option off, note the table count and capacity in the Summary view, turn it on, generate again, and compare. Nothing else in the design changes, so the difference is entirely the option.

A layout edited in Sketch Mode is re-plotted on the aligned grid at the next Generate Layout, with this option off for that run, so that pile coordinates stay uniform for construction.

Half tables

A half table is a shorter MMS-Table — the module mounting structure carrying the modules — that holds whole strings only. It is dropped wherever a full table will not fit: the end of a row, and the narrow strips along an angled boundary.

It is half the modules wide, rounded up, and keeps the full table's height. Each of its strings runs along one half row and back along the next, so it holds half the full table's strings, rounded down. That rule decides what a half table is on your configuration:

Rows per MMS-TableHalf table holdsShare of a full table's modules
1No half table exists—
21 stringOne half
31 string; the third row stays emptyOne third
42 stringsOne half

Everything else about it is the same as a full table. It sits on the same row pitch, at the same tilt, inside the same usable area, and it is placed only where it fits entirely inside it. A half table is not a partly-clipped full table — it is a shorter structure, which is why it can stand in ground a full one cannot.

What the card tells you

The card works this out as you change Rows per MMS-Table or Modules per row. With one row per table, Add half tables is greyed out and the hint under it reads "A half table here would hold only half a string." With an odd number of rows the hint says how many strings a half table carries and which row stays empty. Sketch Mode's ➕ Half Table tool is greyed out with the same words.

The MMS-Table Configuration card with three rows per table and the line Each half table carries 1 string; its third row stays empty.
The half table hint on a three-row table

On a tracker plant

The tracker equivalent is a half tracker, and it is halved along the other axis: half the north–south length, by whole strings. The option reads Add half trackers and is off by default, like its fixed-tilt counterpart.

TrackerHalf tracker holdsShare of a full tracker's modules
1 string, 1 module acrossNo half tracker exists—
2 strings, 1 module across1 stringOne half
3 strings, 1 module across1 stringOne third
1 string, 2 modules across1 stringOne half

With a single module across, it holds half the strings rounded down. With two or more across, it is half the length and holds half the strings on the whole tracker, rounded down.

The place a half tracker earns its keep is the north and south ends of a column, where a full-length unit runs out of ground before the boundary does.

How half units are counted

Half units are never mixed into the full-unit count. The Summary view reports them in their own row, and where a count feeds another calculation the rule depends on the calculation:

Where it appearsHow half units are treated
The Summary viewTwo separate rows — Full tables and Half tables (Full trackers and Half trackers on a tracker plant)
Plant capacity and module countA half unit contributes its own modules, so it lifts capacity by less than a full one
The number of control roomsCounted at its share of a full unit's modules, both when the rooms are counted and when the tables are divided between them. See Inverter control rooms
Sizing the plant to a DC targetCounted as 0.5 of a unit
Cleaning fleet sizingCounted as 0.5 when a line's length is judged too short to justify a robot
PilesEach half unit carries the half pile pattern — derived from the full one, or your own — and counts its own piles. See Pile layout

When to use it

Turn half tables on when the boundary has many short row ends — a long perimeter relative to the area, several angled edges, or a site broken up by obstructions and corridors. The more edge the plant has, the more infill positions there are.

Leave them off when the plant is built from a repeating block that the procurement and construction schedule depends on. A second structure type means a second bill-of-materials line, a second pile pattern, and a second erection method on site, for a capacity contribution that is by definition small.

You can also place a half unit by hand. Sketch Mode's ➕ Half Table tool (➕ Half Tracker on a tracker plant) places one where you click, which is the better route when you want two or three of them in specific places rather than every one the application can find. See Sketch Mode.

Reading the result

The Summary view reports full and half units in separate rows — labelled for tables in a fixed-tilt design and for trackers in a tracker design — so you can see at a glance how much of the plant came from infill. A plant with a large half count on a small full count is a plant whose capacity is leaning on the awkward edges of the site, which is worth knowing before you commit to it.

Read them together with the plant area and the module count. The three figures tell you what the plant is: how much ground, how many structures of each kind, and how much capacity came out. Every row is listed in Summary rows.

Both options make the plant less regular, and regularity has a value that does not appear in any row of the Summary view. A bid drawing, a construction sequence and a maintenance plan are all easier to defend on a plant whose rows line up. It is entirely reasonable to ship the regular version at lower capacity.

What neither option changes

Both options only decide where a unit may stand. Everything else about the plant is untouched, which is what makes a before-and-after comparison meaningful:

  • The row pitch and the tilt angle are unchanged. Rows stay on the same spacing, so the ground coverage ratio of the plant is not quietly altered and the shading loss behind it is still the shading loss you signed off.
  • Rows still run east to west and panels still face the equator. Neither option rotates anything.
  • The usable area is unchanged. The perimeter road, the obstructions, the corridors and the excluded terrain are all subtracted before either option is consulted, and a unit is still placed only where it fits entirely inside what is left. Neither option lets a table encroach on ground the site rules kept clear.
  • The equipment stages are unchanged. More tables mean more capacity, which can mean an extra control room and more arresters — and those remove tables in turn. The extra capacity you read in the Summary view is the figure after all of that, not before it.

Using both together

The two options do not conflict, and used together they compound: the rows move out to the boundary first, then half units fill what the moved rows still leave behind. Expect the least regular plant the application can produce, and the highest table count.

If you are going to run a site both ways in any case, run it three times — off, Maximize placement only, and both — and compare the capacity against how the drawing looks. The decision is not which number is largest; it is which plant you are prepared to build.

Where to go next

On this page