Multiple Rows SingleAxis PV

I am using 2012.5.11 and I am trying to figure out how to model a single axis PV array that has multiple rows. Each row is oriented north south and is in a 2x20 configuration (meaning to panels side by side in the east west direction and 20 panels long in the north south direction). It seems as if I would need something like a subarray to specify the configuration of each row and then specify how many rows are in the field. This is needed for backtracking analysis with different ROM for the single axis tracker. Can anyone point me in the right direction? I see how to specify the row width and the edge to edge distance between rows. I can also see how to specify an array that is 2x20. What I don't see is how to specify how many rows there are in the field.

Hello,

SAM calculates the PV array's output assuming that the array is a single unit with the same physical and electrical characteristics. When you use the backtracking or self-shading options, SAM makes adjustments to the array's output using the parameters that you specify for each of those options. For example, the self-shading and backtracking options each have their own separate parameter for spacing between rows.

To represent the array, all SAM needs to know is how many modules are in the array, and the orientation of the modules in the array. The "Module per String" input helps you ensure that you choose a number of modules that will work with your inverter -- that the array voltage is within the limits of the inverter ratings. In your case, you should first set up the array with the number of modules that meets your capacity requirements, and modules per string that works with your inverter. (At this stage, the 2x20 configuration does not matter to SAM, here you are defining the electrical layout of the array.)

Next, if you want to model backtracking, you should choose a row width value that is consistent with the module you chose on the Module page and your 2x20 configuration: For two modules, the row width should be twice either the length or width of the module. SAM does not store the module length and width in its module libarary, so you will need to get those values from the manufacturer data sheet. (You can confirm that they are consistent with the module area value from the library, which SAM displays on the Module page.) Then, with backtracking enabled, you can experiment with different "Space between edges of adjacent rows" values to see how row spacing affects the array's output. SAM reports the axis rotation angle in the hourly results, so you also can see the hours when the array backtracks.

As for the number of rows, the backtracking algorithm estimates the portion of the array that is shaded by neighboring modules and how that affects its output internally with geometric calculations based on the sun's position and the two backtracking inputs (row width and space between edges of rows). You do not need to specify how many rows are in the array.

One note for the Beta version (to be released at the end of this month, November 2012) and later: SAM models backtracking of each subarray in the same way as above, except that it treats each subarray as a separate array. The four subarrays on the PV Subarray page are not intended to represent the array row sections for backtracking.

Best regards,
Paul.

Thanks Paul,

One other problem I am having is that I get less yearly energy when I increase the ROM for a one axis system from 45 to 70 degrees. I assumed that since backtracking is enabled and 45 degrees is within 70 degrees that at worst case the two systems would have the same energy harvest. I can't figure out why, if backtracking is enabled, the system with a higher ROM would produce less energy then a system with lower ROM. Keeping a consistent GCR I had anticipated that the higher ROM system would simply not reach its full angle potential if that mean that shading the array would happen. Any ideas?


UPDATE: I just downloaded and installed the new version of SAM. The calculations seem to be corrected in this version.