Jump to content

Recommended Posts

Posted

I recently updated to PVSyst 8.0. When I import a shading scene from PVCase, the row (field) sizes are larger than how many modules there actually are due to motor/joint gaps in the rows. Subsequently, with the 8.0 update, I get an error saying that there are more modules in the 3d scene than is specified in the sub array. For example, I have a row with 100 total modules, but PVSyst thinks there are 103 modules based on the size of the module and the size of the row. I am not sure how to modify a large number of these rows to align with how many modules are specified in the sub-array. Can you advise on how to align the system subarray strings/module quantity with the 3d fields? 

image.thumb.png.687ebb2641c5fe574e4fd9346d6cce64.png

 

Posted

It should not matter much that there is a difference. The shading losses calculated in the shade scene are applied to the output determined by the system size as it's defined in the system menu. As you've noted, the motor gaps and joint gaps (depending on the manufacturer) are not considered which leads to the discrepancy. You will need to delete tables to get them to equal, but this may not result in a material difference. 

Posted

Okay so your guidance would be to (a) ignore this error or (b) remove trackers until they are equal? 

Just to confirm I am not missing something, is there a way to apply a specified number of modules to a selected group of fields, similar to how that can be done with partitions? 

image.thumb.png.a70ef76206445a3ecd64ff05cd27410c.png

image.thumb.png.d078ef92a7b9609ed85517aa156b140c.png

Posted (edited)

It is common practice (I think) to ignore this and I would suggest ignoring this, I'd rather have the full area of the table represented when calculating shading loss, rather than changing the size of the table to match module quantity and using a reduced table area (it's this area that determines shading loss after all, not the quantity of modules).

But you can change table size quickly. Determine the lengths associated with each table size according to string size, you can do this by clicking a table, changing the table length according to # of modules, record the length in meters, then go into equipment list, filter for trackers, and filter by length each table type (3/2/1 string), select all of that type and change length. Top picture is before adjust, bottom after, # of modules has decreased after one table swap. 

2024-11-13_20-12-50.jpg

Edited by dtarin

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...