This tutorial contains GIF images.
If they fail to load please visit the help center via web browser.
You can zoom this page with Ctrl+.

Currently there are two possible ways as to how tables are generated on a terrain and what their height is in PVcase:

  1. Generation without enabled terrain tolerance.
  2. Generation applying terrain tolerance.

Generation without enabling terrain tolerance.

In the first case, the tables both for fixed-tilt & trackers are placed at a minimum distance to the ground. This minimum distance to the ground is described using the Frame height by lowest point input. The important thing to understand is that by specifying this number you're not only describing the height by the lowest point but also the height for the entire frame based on this point.

When PVcase is generating without the applied height tolerances (the 1-st approach) it is placing all of the frames to be at least this input distance from the ground.
Which means, for the front side it is at least 800 and for the back side upper point it is at least 2534 mm. for instance. So if there's a hill in the middle of the frame - it is elevated to meet the minimum distance requirement at the specific point of the frame.
An example of this can be seen below in a front view:

Generation applying terrain tolerances.

In this second option - when we start using terrain tolerances we can change the way that this height is being handled by allowing the frame height to get closer or lower to the terrain.

When we Enable terrain tolerances this opens up the inputs of Allowed hill size under frame and Allowed frame elevation to fit.

With the Allowed hill size under frame input you can specify what size mounds/hills underneath the frame are okay to be placed.

For instance, if my input Frame height by lowest point is 800mm. and I were to enter 200 mm. into the Allowed hill size under frame value this would indicate that any tables that have a hill or mound underneath the table of 200mm. or smaller - the frame can be placed.

Keeping in mind that the Allowed frame elevation to fit is set to 0 mm. the generation algorithm would work in this way:

  • Frames are placed at 800mm. from the ground by default (if it's a flat ground).
  • Frames that have a hill of 200mm. or smaller will be placed without elevating the frame.
  • Because Allowed frame elevation to fit is set to 0mm. the frame cannot be elevated. Therefore hills that are bigger than 200mm. will force frames to not be placed.

If we look at the Allowed frame elevation to fit value alone we can see the ability to manipulate how high up the frame can go. For instance, I will input a value of 0 mm. for Allowed hill size under frame and input a value of 200 mm. for the Allowed frame elevation to fit.

The table placement would then look like so:

  • Frames are placed at 800mm. from the ground by default (if it's a flat ground).
  • Frames that have a hill of 200mm. or smaller will be placed BUT they will be elevated by the size of that mound underneath by a maximum of 200mm. - the input allowed frame elevation to fit.
  • Frames that have to be elevated more than the allowed 200mm. from the ground will not be placed.

The final approach is to change both the Allowed hill size and Allowed frame elevation to fit. For instance, I will set the Allowed hill size value at 300 mm. while still keeping the 200mm. for Allowed frame elevation to fit.
This will result in the side view looking like this:

  • Frames are placed at 800mm. from the ground by default (if it's a flat ground).
  • Frames that have a hill of 300mm. or smaller will be placed. (at any point of the frame)
  • Because Allowed frame elevation to fit is set to 200mm. the frame can be elevated by 200mm and still be okay to be placed. So, if there's a bigger mound (500mm in example) the frame will be elevated by 200 and still placed.
  • If there's a mound that's bigger than 500 then the allowed elevation will not permit the frame to be placed.
Did this answer your question?