Device modules

What it is

The number of modules on one device of this type: modules along the length times modules across the width, from the layout. It weights the placement in the blend of orientations; it is not checked against the device rectangle or against the module section's outline. The system nameplate still comes from the racking section's stringing; when the scene's module total differs from the system's, POST /api/run warns.

Typical values and how to get it

Count as built. A DC nameplate given with the layout, in a drawing's title block or a file name, is a count too: divide it by the module's power for the module total and share that among the devices. When the layout gives neither, estimate the count from the rectangle: the length over the module's short side, times the width over the module's long side (1 for one-in-portrait, 2 for two-in-portrait). Take the module outline from its datasheet or PAN file; a library module converted from the CEC list carries only its area, as an outline 1 m wide. With row-to-row shading off, as on a roof, the type's length and width only draw the device, so an outline estimated from the module's area leaves the result unchanged. Only the ratios between the types' counts change the result: with a single type any count gives the same result and feeds only the module-total warning. On an ewf type, count both faces: the number is even and each face carries half.

API

scene.types.modules