dtarin

I also have this issue.

Hello, Presently when entering module X and Y spacing, PVsyst takes N modules (X or Y) times the spacing and adds it to either width or length. Should this be N-1 modules times the spacing, and then added? This would present a method which allows PVsyst to match construction design drawings.

Hello, It would be useful to allow the electrical effect parameter to go above 100%. The purpose would be to tune models where there is disagreement with measured data as it is concerned with shading. In cases where the model under predicts, it would serve to add additional shading related losses appropriately, by keeping the additional losses as a function of site conditions, time of day/year, etc.

It is possible to download SolarAnywhere data as a .csv file or as a 'SolarAnywhere' file format, in which the latter would use the SolarAnywhere menu selection in PVsyst.

Hello, Are there any plans to have zones work with tracker systems? Or some other method to modify tracker designs more easily? Presently it is a very manual process and cumbersome process to work with trackers. It would be useful if a selection tool allowed an array block to be split as selected. For example, a rectangle is drawn encompassing a number of tracker rows, and creates new blocks which remain in place. From these three separate tracker blocks, 9 are created, which allows the quick removal if the middle area in the area needs to be removed during a later design stage (image for reference).

Hello, It would be useful if when a table or shed is copied/pasted in a shade scene, it takes the name of the table copied and adds a numerical value which increments by 1 so that each copied table/shed/object has a unique name. Copying/pasting sheds/tables saves time, but when there is an error associated with one, presently it will refer to the name of the table; if copied/pasted, it will have the same name unless a unique name is entered each time, which is time consuming when there are a number of elements copied/pasted. Thanks.

Hello, It would be useful to be able to select multiple 3D polygons and edit the height for all simultaneously. Presently, only color can be modified when selecting multiple polygons. Thank you.

If you imported the SolarAnywhere file as a .csv, you will use the NREL TMY3 format for import, no modifications needed. Edit: I just tried importing a .csv solaranywhere file using the solaranywhere format and I also received that error, so I would suspect that is also what you are doing.

Have you figured this out?

Related to this suggestion and modifying tables, it would be nice to have included the frame size in this menu (picture shown for tracker sheds)

This can be overridden in the OND file. Under Contractual specifications, uncheck the box next to "Maximum PV Current". This has no impact on the simulation results.

There was a previous forum post which said +/- 1 degree would still simulate, but i set my trackers to +0.5/-0.5, and I still received the error.

Hello, Is it possible to model a horizontal N-S tracker system in a single shade scene with different tilts? It seems not. If it is indeed not possible, is it something that could be added in the future? Thank you.

Will we be able to import ground data for terrain and have it selected as a bifacial ground object?

Change the setting in your hidden parameters under Detailed Simulation Verification Conditions

How long is the data set (how many months), and how did you do the comparison to come to a delta of 1.2%?

Hello, Does the inactive frame which borders a module matter for calculating POA, or rather, is it used or not used to calculate POA? This area is included in the module dimensions, so in a shade scene, the area represents the entire area of the module (cells + frame). But for production purposes, I am assuming that the cell area is used, is that correct? Is the amount of incident light used to generate the energy results based on the cell area, or on the module area? Hopefully the question is clear enough. Thanks.

Hello, I have noticed for a project that several parameters under detailed losses are not showing up as such in the waterfall, as they are entered in detailed losses. LID, MQF, and mismatch are all different from what I have entered. I am also getting higher temperature and irradiance losses (compared to 6.7.5). Running the same project in 6.7.5 results in the previous behavior; what is entered for LID, mismatch, and MQF is what shows on the waterfall. Could PVsyst shed some light as to why all of these parameters are now different in 6.7.7? I did not see anything in the release notes mentioning changes such as this. Additionally, the Array Nominal Energy is not being calculated correctly on the waterfall.

HI Mimi, You will need to create three separate variants for each system if you want the outputs to be separated. You can model as many as you want together, but the outputs will be combined. I'm not sure what the specifics are, but if if the building(s) will impact other systems, create a shade scene with all of the buildings, and then have three variants, where in each one the modules are on a different building.

It seems I solved it. I transformed the zones into groups, and went to the edit orientations menu and tried again. This time it stayed.

Hello, I have defined two orientations in my shade scene. I have set the discriminating orientation difference between shading planes to 0.5 degrees (the lowest it will go). My two orientations are 20/0.9 and 15/2 (tilt/azimuth). When I exit the shade scene however, the model always calculates a single average. In hidden parameters, these values are also set to the lowest possible value, so I dont understand why the program won't discern the two different orientations in the shade scene. I have tried this in 6.7.5 and 6.7.7.

Can you just copy/paste the PAN/OND files into the project's folder, rather than use the import function, and restart PVsyst? C:\Users\Username\PVsyst660_Data\ComposPV\PVmodules

This observation I think is independent of any grid limit, max export power, or AC losses. We're seeing production that is higher than what the inverter is defined to be able to output. Not only does the inverter report higher production than the defined maximum, it doesnt show clipping loss associated with these hours in example provided.

PSM can overestimate by 5% under clearsky conditions, and has a GHI MBE of +/-5%. See link: https://www.nrel.gov/docs/fy17osti/67722.pdf

Hello, Is it possible to use relative humidity from SolarAnywhere or TMY3 NSRDB weather files?