Fredy

Good afternoon I’ve updated PVsyst to v6.70 but this error is still there. I've noticed why PVsysts always assumes Pitch (Sheds spacing in 6.7) 5m in the report when you import a layout from Helios3d. When you go to construction perspective and open a single table that you imported from helios3d the default values for pitch is 5m. But this is wrong in the full layout we have different pitch so is there any way to remove this option from the report or fix it? Thank you for your support

Good Morning I’m using the New Version of PVsyst 6.68 and when I do "Construction / Perspective" I usually import from Helios3D i have an Pitch on the Layout but in report it always show 5m (I’ve tested in different layouts with different distances its always 5m on report) Is there any way to remove this option from the report like in the previews versions?

Good afternoon Im revewing an old simulation and with the exact same IAM profile i get diferent losses in the end (this profile is imported from .PAN file, in the V6.67 i had to copy the values) is there any explanation for this or is it an error?? IAM profile 6.65 6.67 thank you for your support Best reggards

Hello We are trying to do montlhy PR calculations, but when we do the final monthly average the value is different from the PVsyst final PR Could you please help us with this issue? Thank you for your support Best Reggards

Hello In module Layout I’m trying to simulate the dirt and dust loss that accumulates in the corner of the modules: Is it Possible to do this in the module layout? Add a triangle as an “Inactive area of the modules? I can’t see the Option to add a shading area is it bugged? I’m using PVsyst 6.39 Thank you for your support

Hello I need to set smaller time intervals to measure the angle of a tracker In this simulation our tracker is a tilted axis tracker with: Axis tilt: 0 Axis Azimuth: 0 Phi min.: -45 Phi min.: +45 I see in near Shading the "Shadow animation" gives us sun azimuth and sun height each 15min Can we Export a table with the following data: Time: 00:00 ; 00:15 ; 00:30 etc... 23:45 Sun azimuth Sun height Phi angle (-45 : +45) Thank you for your support

Good afternoon I'm comparing 3 different Meteo databases and in this 3 simulations i used all parameters losses modules inverters are the same just changed the Meteo, I get the following results: I don’t understand why Meteonorm VS PVgis have almost the same Global Radiation and the PR changes so much (81.6 - 82.2)? and Meteonorm VS Meteosat have the same difference on PR (81.6 - 82.2), with lower radiation and higher GlobINC i have more gain in (Hor / Inc) that i understand Is there some other parameter that affects this when using different Meteo files? Thank you for your support

Hello I have the PVsyst 6.39 Version andI'm having trouble importing an inverter File from Version 6.43: I get this error: Is there any way to import recent files to old versions of PVsyst? thank you for your support Best reggards

Hello I had to come back at this Post because, We are trying to find out how the azimute was calculated when we have multiple orientations and we had to use higher "Discriminating orient. difference between shading planes", we did several tests the azimuth it show's on the image bellow: Is the azimut of the "Main Table" the one that we creat first or in cause of Helios 3D it alwas show the same azimuth in "constraction prespective" im assuming it is average? or is it the azimute of the "main table"? We are now doing a project with very hight slopes what's the best since PVsyst "during the simulation, the incident irradiance will be calculated once for the average orientation, and applied to all tables in the same way, resulting in a (little) orientation loss." We wanted to know how should we treat this case? Should we add some losses to consider this "orientation loss."?

Same problem here Iso Shading diagram doesn't show on the pdf reports

Hello I'm trying to do a few simulations with the Design on Helios3D with multiple tilts (Multiple helios3D files) then i combine the CSV files in order to see the production / PRs for the PV plant with the tilts corresponding to the days i find better. When using daily values we get some PR's that doesn’t make sense and when i do the average PR I get lower PR with this multiple tilts but better production On the CSV with the multiple tilts I’m excluding Values under 10% of the maximum value for each month and it gives me something near the average PR of the 3 Tilts configuration But I don’t know if it makes sense either the PR should be +/- constant because if we have low irradiation the production should fall down as well making the PR +/- the same as a high Irradiation day? At least when we measure with our pyrometers the PR goes +/- constant with low deviations between max and min and without that low values that shows on the image bellow Do you have any idea how to make this seem right? This image is just an example of the PRs from 1 month Thank you for your support

Hello Is it possible to import trackers from helios3d? Or to import an fixed layout and convert the tables into trackers? Look forward for your feedback Best regards.

Hello I'm doing some big PV plants and i got this error in one of them: When we have big slopes on helis3D sometimes this happens. Is there any way to simulate even if this happens, anything on the hidden parametters or something? Best reggards *PVsyst 6.34

Thank you for your help, Ok so PVsyst considers some days covered cloudy? Normally I see monthly values when importing from external Meteo data This hourly tables are interpolated by PVsyst when we do the synthetic hourly data generation? It is a probability calculation? Sometimes 0 for beam irradiance and sometimes x% for Beam irradiance? Where can I find this? Thank you for your support in advance

Hello I’m sorry for the spam I found that for Horizontal Beam there are some values missing or low values a lot actually, Maybe this could be the reason why I’m getting this For this test I’m using another Meteo file from PVGIS On the first Post I was getting BeamHor = 0 in every cell for 21-December, but now even with this one from PVGIS there are some missing values. In the images bellow the red/green cells corresponds to the acceptable / unacceptable values for BeamHor Blue Cells were calculated: (ShdLoss / GlobInc.) to have a perception of the loss % In this table we can see that there are some missing values and low values that doesn't make sense more losses at the mid of the day then at morning I found this one acceptable at least make more sense than the other two This one seems good too more losses at morning/afternoon and less on mid-day It was harder to find correct values then wrong / missing values. 1- Could you see if this is a bug from the program it fails to generate some values or something? 2- The program calculates the shadows for every hour with the corresponding shading factor but it needs the beam Irradiation right? Thank you in advance for your support