Representation of gaps along tracker when using PVcase scenes

[LauraH]

Hi,

Whenever I read in a PVC file for a shading scene, the array area and number of modules shown by PVsyst don't match the array design.  After some thought, it seems that the array size is being inflated by the size of various gaps along the tracker:  gaps between modules, motor gaps, and potentially joint gaps.  Is there any way to correct this?  It causes error messages. Optimally, PVsyst would get this information from the PVC file.

Edited Tuesday at 05:10 PM by LauraH
Correction

[dtarin]

You can change the settings for both types of messages. The shade scene module count has no impact on simulation results. 

 

[LauraH]

Sure, that's how we handled the generic mismatch problem in the past, but it would be nice if it just worked, taking advantage of the CAD system including specific details.