dtarin

I would check graphics card drivers, install a different pdf program, and instead of saving to pdf, print it to pdf like cute pdf, etc.

Depending on the inverter you can use the multi mppt feature to model across different sub-arrays assigned to different orientations. This can be done to model different orientations, modules, etc.

Replacing that with average would be good (and stating it as such).

Hello, It would be nice if we could hide a ground CSV data like we can a ground image. I would like to keep it in the shade scene but not have it show in the report.

Hello, In 6.7.0, when a monthly soiling profile is used, the yearly loss factor value is also being displayed on the report. It doesn't seem to affect the calculation, but is a little misleading when reading the reports.

Hello, In PVsyst 6.68, when I load a project with a shade scene utilizing multiple zones that was created in an earlier version (usually 6.63 for me), not all of the zones are present in 6.68. Usually just the first zone is, and the rest are deleted, not present at all, but all of the objects in the shade scene are there in the same manner as they were constructed in. The zones are present in 6.63 but not 6.68. I also tried saving the shade scene in 6.63 and then reloading it in 6.68 (by reading scene) and they were still missing.

There is not as far as I know. You will need to create two variants.

Thank you for the reference. However the issue I have arises when the angle tolerance is less than 1 degrees. In hidden parameters, we can define a tolerance of 0.1 degrees, but it doesnt seem possible to manually define orientations with such a tolerance. The result always reverts back to a single orientation (in my recent case).

Hello, I have a shade scene with ground terrain, and I'd like to divide the design up into four sections that are relatively close together in terms of average tilt and azimuth. In Hidden parameters under Detailed Simulation Verification Conditions, I have set the first six values to 0.1. However under project settings > other limitations, the minimum value allowed is 0.5 for discriminating orientation difference between shading planes, and 1.0 for maximum orientation difference for defining average (spread) orientation. What I think is happening is that the project settings are overriding the hidden parameter settings, and because my orientations are close together, the orientations I manually define in the shade scene using the orientations tool keeps reverting back to a single effective azimuth. Can the minimum values allowed in project settings > other limitations be reduced to 0.1 degrees to allow for more granularity in defining orientations?

What type of fence?

I see it in mine. This is for a N-S horizontal tracker with backtracking enabled. Version 6.6.8. See image for reference.

Hello, It would be very useful for testing and validation of plants if one were able to select a single, specific table for which the software calculates and exports global incident irradiance for, and outputs separately 8760 data, a variable called something like GlobInc2. For example, I have a site with terrible undulations, and it is constructed with a single irradiance sensor in a particular location near a module. It would be useful to report the global incident irradiance for that location, while still running my simulation in the usual fashion that it does. I imagine it to be an option under tools called irradiance analyzer or something like that, where a dialog opens up for which I can select the table or tables for which to output a separate global incident irradiance for. I dont know if this is already possible, please inform me if there is some existing way to extract such data. Thank you.

Maybe this picture helps.

What if you increase tolerance to say 20 or 30 degrees and identify orientations? You can also update the setting under project settings. Also try saving the project and reopening. Sometimes it sticks on a previous error message.

You can use the "edit orientations" feature under tools to remove all of the orientations, and then create a single new orientation where you add all of the different zones to the one orientation. Once completed and you exit the shade scene, you will update orientation parameters.

Good question. I would like to know if anyone has a link to some studies on this.

It is 2.

Unlimited sheds for trackers is available in version 6.67. However depending on the design constructing a shade scene can result in slightly lower losses compared to unlimited sheds method.

Hello, It would be helpful if module specific inputs were listed for each module in the PDF report, such as IAM profile, LID, etc. For LID it looks like it gives an average both in the waterfall and in the simulation parameters section on page 1 or 2, which makes it impossible to confirm which test data has been used for each module. Thank you.

Hello, I have two tracker arrays shown in attached image one, where the length of rows is different for the two blocks. If they are set to zero azimuth and placed adjacent to one another (with the spacing shown in image 1), there are no errors. If I change the azimuth to say 12 degrees (image 1), I get the error message shown in image two. The two arrays are separated by >5m. Is there a bug which arises when the azimuth is changed? The arrays need to be separated by more than 11.12 meters for the error message to go away. PVsyst version 6.63. Thanks.

What PVsyst version are you using? I am using 6.63, and the -30 time shift saved for me. I updated the .MEF file, saved, ran it, closed PVsyst, and reopened, and it was still there. When I run it again, a -30 time shift shows up.

Not to my knowledge. Trackers are not as flexible as fixed tilt systems in terms of modeling in a shade scene, and there are limitations to them (ie misalign and ground terrain situations).

#1) In a N-S tracker system, pitch is the E-W distance from post to post for the tracker. This can be verified in the shade scene once constructed. #2) The option is called Tilted Axis to select N-S tracker.

Hello, I am trying to use the parameter optimization feature with a shade scene to simulate different azimuths, but the feature is not working. It works with unlimited sheds, but not when I have a shade scene. There is only one orientation in the shade scene. PVsyst version is 6.66. Also occurs with 6.63. Does anyone else have this problem?

If you are talking about DC ohmic losses, just enter the percentage you want to use. Click the cursor into the wire resistance field above after updating the percentage, and then click back below into the percentage field. The mOhm should update when you first click into it after updating the percentage.