| What is the Fields article about? | It explains the properties of a selected field in HELIOS 3D. A field consists of a closed Polyline or 3D Polyline located entirely inside an area, and HELIOS 3D automatically connects the field to the area in which it is situated. (Helios 3D | HELP CENTER) |
| Where is the Fields topic located? | It is part of the vertical menu placement workflow in the HELIOS 3D Palette. The Help Center navigation lists it under Overview of Commands > Vertical Menu > Placement > Fields. (Helios 3D | HELP CENTER) |
| What is a field in HELIOS 3D? | A field is a closed Polyline or 3D Polyline inside an area. It defines the placement zone where arrays can be placed and configured with field-specific placement parameters. (Helios 3D | HELP CENTER) |
| What must be true for a field geometry? | The field geometry must be a closed Polyline or 3D Polyline and must be entirely located within an area. HELIOS 3D then automatically establishes the connection between the field and that area. (Helios 3D | HELP CENTER) |
| What is the Field tab used for? | The Field tab is used to configure placement options for the selected field, including sun settings, row distance, module inclination, array distance, conflict limits, power limits, array groups, tracker parameters, array assignments, and placement statistics. (Helios 3D | HELP CENTER) |
| Are the placement commands inside the Field tab permanent? | Not necessarily. The article notes that the commands within the Field tab may be removed in a future version, and the command descriptions are referenced in the Command Group Placement section. (Helios 3D | HELP CENTER) |
| Can field-specific sun data override project settings? | Yes. The field can override the sun position data from the project page so that shadow casting direction can be adjusted for all placements in the selected field. (Helios 3D | HELP CENTER) |
What does Date / Time control for a field? | It defines the date and time for the specific placement. This value overrides the project settings for the selected field. (Helios 3D | HELP CENTER) |
| How is the field sun angle calculated? | The sun angle is calculated from the project’s geographic location and the field-specific date-time setting. The article also states that the sun angle can be manually overridden if required. (Helios 3D | HELP CENTER) |
| When should I manually override the sun angle? | Use a manual sun angle only when a specific shadow direction must be tested or documented and the calculated value should intentionally be replaced. The article states that manual override is possible, but it does not give detailed decision rules. (Helios 3D | HELP CENTER) |
What does Shadow behavior – No shadows with secure distance do? | It adjusts the safety margin between the shadow and the array’s bottom edge to maintain shadow-free conditions for all modules. (Helios 3D | HELP CENTER) |
What does Shadow behavior – Allowed shadows in module plane do? | It generates row distances so that the longest shadow from the previous row aligns with the configured shadow depth on the modules of the next array row. (Helios 3D | HELP CENTER) |
What do Row Distance Min. / Max. define? | They define the minimum and maximum distance between one row and the following row. (Helios 3D | HELP CENTER) |
What does Array placement direction define? | It sets the direction for array rows according to the arrow direction shown in the field settings. (Helios 3D | HELP CENTER) |
What does Start rows opposite side do? | It can switch the first row to the opposite side of the field when a minimum row distance is set. This uses the arrow and sun settings, rotates the array blocks, and can change fixed-tilt array azimuth, for example from 0° to 180°. (Helios 3D | HELP CENTER) |
What should I consider when using Start rows opposite side? | The shadows still follow the configured sun settings. If shadow positioning remains important, the sun azimuth must continue to be used and checked carefully. (Helios 3D | HELP CENTER) |
What does Module Inclination define? | It sets the module inclination for each array within the selected field. (Helios 3D | HELP CENTER) |
What does Array Distance define? | It defines the distance between neighboring arrays, taking their rotation within a row into account. (Helios 3D | HELP CENTER) |
What does Array Height define? | It overrides the insertion height of a PV table above the surface, which was originally set in the Array Generator. (Helios 3D | HELP CENTER) |
What does Allowed Overhang define? | It defines the allowed overhang for arrays at the end of a field. This is useful when many rows have gaps at the field end and the gaps are only slightly smaller than one array. (Helios 3D | HELP CENTER) |
What does Hatch shadowed arrays do? | It creates a hatch over arrays affected by the shadow of an array from the previous row. This is useful when a shadow-free placement criterion is intentionally disregarded during placement. (Helios 3D | HELP CENTER) |
What are Limits / Conflicts used for? | They define field-specific limits and conflict rules for placement, including slope, module distance to DTM, post height over DTM, height difference to neighboring arrays, angle difference to neighboring arrays, and flood-level restrictions. (Helios 3D | HELP CENTER) |
What does Max. Slope – North/East – South/West do? | It allows the field to override the general slope limit specified in the array definition. If the override is disabled, the slope limit from the array definition is applied. (Helios 3D | HELP CENTER) |
What does Module distance to DTM – Min. / Max. define? | It defines the minimum and maximum permitted distance between modules and the surface. The limits are evaluated at the front and back module edges and between adjacent module rows so elevation variations below the array can be detected. (Helios 3D | HELP CENTER) |
What does Post height over DTM – Min. / Max. define? | It defines the minimum and maximum height of the post head relative to the ground. (Helios 3D | HELP CENTER) |
What does Height difference to neighbor array evaluate? | It evaluates the height difference relative to the previously installed PV table to help prevent shading within the table row. (Helios 3D | HELP CENTER) |
What does Angle difference to neighbor array evaluate? | It evaluates the angle difference between neighboring modules. The article states that this may be necessary for tracker systems. (Helios 3D | HELP CENTER) |
What does Elevation of flood level do? | It treats all surface points below the specified height as flooded and excludes them from placement. (Helios 3D | HELP CENTER) |
| How are placement conflicts displayed? | Placement statistics display all detected conflicts with corresponding colors. Conflict markers are assigned to conflict-specific layers and colors. (Helios 3D | HELP CENTER) |
| Which conflict colors and layers are mentioned? | Side slope uses H3D_Table_MaxSidePitch with default cyan, module distance to DTM uses H3D_Table_InvalidTableHeightMarker with default orange, post height over DTM uses H3D_Table_InvalidPostHeightMarker with default red, and flood-level conflict uses H3D_Table_WaterLevel with default blue. Height and angle differences to neighboring arrays also have dedicated marker layers. (Helios 3D | HELP CENTER) |
| What options are available for detected conflicts? | A conflict can be ignored and the PV table placed with an X marker on a conflict-specific layer, or the lower end of the array or the entire array can be raised to meet the relevant limit. Adjusted arrays can receive ellipse markers on an _Aligned layer. (Helios 3D | HELP CENTER) |
| What happens when a conflict is not addressed? | A temporary rectangle is inserted instead of the array. It can be hidden manually or removed automatically at the next update of internal objects. (Helios 3D | HELP CENTER) |
What does Use Array Increment do for unresolved conflicts? | It skips affected arrays during placement and creates a gap in the row where the full array length would have been. This helps arrays in the rows above remain aligned in a straight line. (Helios 3D | HELP CENTER) |
What does User Defined Increment do for unresolved conflicts? | It moves the affected arrays further along the row direction until a valid location is found. The entered value defines the step width for each move. (Helios 3D | HELP CENTER) |
What do Arrays per Row – Min. / Max. control? | They define the minimum and maximum number of arrays per row. A row is not inserted if the minimum count is not met, and the row stops once the maximum count is reached. Placement then continues with the next row. (Helios 3D | HELP CENTER) |
What do Power per Row – Min. / Max. control? | They define row limits based on total row power in kWp. A row is not inserted if the minimum power threshold is not met, and the row stops once the maximum power is reached. (Helios 3D | HELP CENTER) |
What does Field Power – Max. control? | It defines the maximum number of arrays for the field based on the total power of the entire field in kWp. (Helios 3D | HELP CENTER) |
What are Array Groups and Row Groups used for? | They allow arrays to be placed in groups within a row and define distances between those groups. This can be used, for example, to create access paths or service roads through a field. (Helios 3D | HELP CENTER) |
| What should I consider when using array groups for service roads? | The starting points of all rows should be aligned so that arrays in subsequent rows and the gaps between groups remain aligned. (Helios 3D | HELP CENTER) |
| Can varying group distances be defined? | Yes. The article states that a list of groups can be added when varying distances are needed. Distances can be separated by semicolons, and decimal values use a dot as the decimal separator. (Helios 3D | HELP CENTER) |
| Can different array definitions be assigned to different groups? | Yes. For array groups, a specific table of the requirement type can be used in each group. The article gives an example using a YL 2×22 table for one group and YL 2×11 tables for another group. (Helios 3D | HELP CENTER) |
| Can the array group keys be changed manually? | No. The keys are displayed in the array list of the field, but they cannot be changed manually. (Helios 3D | HELP CENTER) |
| What does mirroring groups around a Start Point Adjustment Line do? | It toggles between the original group design and a mirrored design around the Start Point Adjustment Line, allowing the group layout to be adjusted in the opposite direction. (Helios 3D | HELP CENTER) |
When is the Tracker System Parameters command group active? | It is active only if the field is generated as a tracker field. This setup can be applied to an area before the first field is created. (Helios 3D | HELP CENTER) |
| What are Tracker System Parameters used for? | They define limiting values and checks for rotation axes within a tracker row and for the drive shaft controlling tilt within a tracker block. (Helios 3D | HELP CENTER) |
What does Max. Slope Drive Shaft define? | It sets the maximum allowed slope between drive shaft segments, such as A to B or B to C, and marks shaft segments if the slope limit is exceeded. This usually applies in the x-direction. (Helios 3D | HELP CENTER) |
What does Max. Slope Rotation Axis define? | It sets the maximum allowed slope between segments on each side of the drive shaft and marks table segments with a cross if the slope limit is exceeded. This usually applies in the y-direction. (Helios 3D | HELP CENTER) |
What does Drive Shaft Distance define? | It defines the distance between the drive shaft and the post head. (Helios 3D | HELP CENTER) |
What does DTM Collision define for tracker systems? | It sets the minimum distance between the drive shaft and the Digital Terrain Model for collision detection. Detected collisions are highlighted for the affected shaft segments. (Helios 3D | HELP CENTER) |
| What changed for tracker insertion in version 2024? | The insertion and rotation of tracker arrays to the ground were modified for improved surface grading. The article states that using overground post height would otherwise result in a different orientation after surface grading, and that post lengths for trackers are slightly longer with the new algorithm. (Helios 3D | HELP CENTER) |
| Why are tracker placement rules different from fixed-tilt systems? | Trackers have adjustable tilt and two module edges that must be checked for ground clearance in extreme positions. These edges can come closer to the ground than in fixed-tilt or east-west systems, so tracker placement must consider movement, variable ground clearance, and possible collisions. (Helios 3D | HELP CENTER) |
| How does HELIOS 3D react if tracker module clearance is too small? | HELIOS 3D can increase the insertion height of the tracker to restore the specified distance, which increases post overhang. It can also check for collisions or insufficient distances along the tracker length, allowing the user to raise the entire tracker or reduce the distance to a tolerance value. (Helios 3D | HELP CENTER) |
| What alternative exists if raising the tracker is not desirable? | A local grading surface can be created to generate the required minimum distance over the terrain. The article notes that more detailed grading information is provided in the main grading section. (Helios 3D | HELP CENTER) |
What is the Arrays tab used for? | The Arrays tab is used to create different requirement types and assign array definitions to each one. At least one requirement type with one or more connected and selected array definitions is required for placement. (Helios 3D | HELP CENTER) |
| What is the connection chain for field placement? | The article describes the chain as Array Definition → Default Requirement Type → Field. Requirement types define conditions, array definitions provide the array configurations, and placement uses the selected requirement type and connected array definitions. (Helios 3D | HELP CENTER) |
| Can multiple arrays be assigned to one requirement type? | Yes. Multiple arrays of different sizes can be assigned to one requirement type. HELIOS 3D tries to place the first array in the list first, then proceeds top-down to the next array if the first one cannot be placed. (Helios 3D | HELP CENTER) |
| Why is the order of arrays important? | The first array in the list is attempted first. Array order also determines placement priority, especially when the number of instances per field is limited for a specific array definition. (Helios 3D | HELP CENTER) |
| Can multiple requirement types be used in one field? | Yes. Multiple requirement types can be used to place different arrays, or the same array with different parameters, within one field. Requirement type zones are needed to connect specific requirement types to specific zones. (Helios 3D | HELP CENTER) |
| Can different modules be assigned to the same PV table record? | Yes. Alternative modules can be assigned to the same array without copying the database record, as long as the alternative modules have the same dimensions, such as length, width, and thickness. (Helios 3D | HELP CENTER) |
| Do alternative modules have to be from the same manufacturer or series? | No. The article states that there is no required relationship between the modules, so they may come from different manufacturers or series as long as the dimensions match. (Helios 3D | HELP CENTER) |
| What does the button for adding a requirement type do? | It adds a new requirement type to the list so that additional placement criteria can be defined and customized for field-specific conditions. (Helios 3D | HELP CENTER) |
| What does the button for adding an array definition do? | It adds an array definition to the list. The available selection includes the full structure of connected “next smaller arrays”, but those connected arrays are not automatically selected for placement. (Helios 3D | HELP CENTER) |
| What does the delete button in the Arrays tab do? | It deletes the current selection, removing the selected array or requirement type from the list or configuration. (Helios 3D | HELP CENTER) |
| What does the refresh button in the Arrays tab do? | It refreshes the list so that recent changes or additions are shown and current data is displayed. (Helios 3D | HELP CENTER) |
| What do the move up and move down buttons do? | They move the selected array or requirement type up or down in the list. For arrays, this changes placement priority. (Helios 3D | HELP CENTER) |
What does Edit Component (Array) do? | It opens the master data editing dialog for the selected array definition, including the default component sections and the array-specific component data section. (Helios 3D | HELP CENTER) |
| What should I consider before editing an array component? | Changes to component master data affect other drawings and projects as well. The article recommends considering a copy of an existing array definition if the change should only apply to one project or drawing. (Helios 3D | HELP CENTER) |
What does Edit Parameters (Rack) do? | It lets the user overwrite parameters of selected arrays in the Arrays by Requirement Types list. These changes are linked to the selected list entries but are not saved to the array definition database record. (Helios 3D | HELP CENTER) |
Why is Edit Parameters (Rack) useful? | It allows the same array definition to be used for different requirement types with different parameters, so a rack can be adapted to different surface or environmental conditions without splitting the field or changing the master definition. (Helios 3D | HELP CENTER) |
What is the Statistic tab used for? | The Statistic tab contains a protocol of the last placement run. It helps analyze the placement outcome and identify areas for optimization before subsequent placement runs. (Helios 3D | HELP CENTER) |
| What should I check if a field is not connected to an area? | Verify that the field polyline or 3D polyline is closed and entirely inside an area. HELIOS 3D establishes the field-to-area connection automatically only when the field is situated inside the area. (Helios 3D | HELP CENTER) |
| What should I check if placement uses the wrong shadow direction? | Check the field-specific Date / Time, calculated sun angle, and any manual sun angle override. Field settings can override the project page sun position data. (Helios 3D | HELP CENTER) |
| What should I check if row spacing is too small or too large? | Check the shadow behavior setting, Row Distance Min. / Max., sun angle settings, module inclination, and whether allowed shadow depth in the module plane is being used. (Helios 3D | HELP CENTER) |
| What should I check if arrays are rotated in the wrong direction? | Check Array placement direction and whether Start rows opposite side is enabled, because this option can rotate array blocks and change the azimuth of fixed-tilt arrays. (Helios 3D | HELP CENTER) |
| What should I check if arrays are not inserted because of terrain conflicts? | Check the active conflict limits: slope, module distance to DTM, post height over DTM, height difference to neighboring arrays, angle difference to neighboring arrays, and flood-level elevation. Placement statistics show the detected conflicts and their colors. (Helios 3D | HELP CENTER) |
| What should I check if temporary rectangles remain after placement? | Temporary rectangles appear when conflicts are not addressed. They can be hidden manually or removed automatically at the next update of internal objects. (Helios 3D | HELP CENTER) |
| What should I check if too many gaps are created in rows? | Check unresolved conflict handling. Use Array Increment skips affected arrays and leaves full-array gaps, while User Defined Increment moves affected arrays further along the row until a valid location is found. (Helios 3D | HELP CENTER) |
| What should I check if rows stop too early? | Check Arrays per Row – Max., Power per Row – Max., and Field Power – Max. because these settings can stop rows or limit the entire field based on array count or kWp. (Helios 3D | HELP CENTER) |
| What should I check if no row is inserted? | Check Arrays per Row – Min. and Power per Row – Min.. A row is not inserted if the configured minimum number of arrays or minimum power threshold is not met. (Helios 3D | HELP CENTER) |
| What should I check if service-road gaps are not aligned across rows? | Check that all row starting points are aligned before using array groups for access paths or service roads. The article states that aligned starting points are essential for keeping group gaps aligned across rows. (Helios 3D | HELP CENTER) |
| What should I check if varying group distances are not interpreted correctly? | Check the distance list syntax. Use a dot as decimal separator and semicolons to separate different distance values. (Helios 3D | HELP CENTER) |
| What should I check if the wrong table type is used in an array group? | Check the requirement type group configuration and the array keys shown in the array list. Specific tables can be assigned to specific groups, but the keys cannot be changed manually. (Helios 3D | HELP CENTER) |
| What should I check if tracker drive shaft segments are marked? | Check Max. Slope Drive Shaft and DTM Collision. Shaft segments are marked if slope limits are exceeded or if the minimum distance to the DTM is violated. (Helios 3D | HELP CENTER) |
| What should I check if tracker rotation-axis segments are marked? | Check Max. Slope Rotation Axis. The article states that table segments are marked with a cross when the slope between segments on each side of the drive shaft exceeds the limit. (Helios 3D | HELP CENTER) |
| What should I check if tracker post lengths appear longer than expected? | The article states that the 2024 insertion algorithm may result in slightly longer tracker post lengths because insertion height is adjusted to maintain required ground clearance after surface grading or terrain variation. (Helios 3D | HELP CENTER) |
| What should I check if tracker arrays collide with terrain? | Check module edge clearance in extreme tilt positions, DTM Collision, drive shaft distance, tracker insertion height behavior, and whether a local grading surface is needed to maintain the desired minimum distance. (Helios 3D | HELP CENTER) |
| What should I check if placement cannot start because no array is available? | Check the Arrays tab. At least one requirement type with one or more connected and selected array definitions is required for placement. (Helios 3D | HELP CENTER) |
| What should I check if HELIOS 3D does not try the desired array first? | Check the order of arrays in the requirement type list. HELIOS 3D attempts placement from the top of the list downward. (Helios 3D | HELP CENTER) |
| What should I check before changing array master data from the field workflow? | Check whether the change should affect other drawings and projects. If not, create and use a copy of the array definition instead of modifying the shared master data. (Helios 3D | HELP CENTER) |
| What should I check if field-specific rack parameters do not appear in the database record? | Edit Parameters (Rack) changes are linked to the selected entries in the field’s Arrays by Requirement Types list and are not saved to the array definition database record. (Helios 3D | HELP CENTER) |
| How does Fields relate to Areas? | A field must be located entirely inside an area. HELIOS 3D automatically connects the field to the area in which it is situated. (Helios 3D | HELP CENTER) |
| How does Fields relate to Requirement Type Zones? | Fields use requirement types and assigned array definitions for placement. Requirement type zones can be used to connect different requirement types to specific zones within one field. (Helios 3D | HELP CENTER) |
| How does Fields relate to the Array Generator? | Field settings can override some limits from the array definition, such as slope limits or insertion height. Array definitions assigned in the field can also be loaded into the Array Generator for viewing or editing. (Helios 3D | HELP CENTER) |
| How does Fields relate to tracker systems? | Tracker fields activate tracker-specific parameters for drive shaft slope, rotation-axis slope, drive shaft distance, and DTM collision. Tracker placement also uses special rules because tracker modules move and require clearance checks at extreme tilt positions. (Helios 3D | HELP CENTER) |
| What is the main takeaway from the Fields article? | Fields are closed placement zones inside areas. The Field tab controls field-specific placement behavior, including sun and shadow settings, row and array distances, terrain and conflict limits, power limits, array groups, tracker parameters, requirement types, array assignment priority, and placement statistics. (Helios 3D | HELP CENTER) |
