MicheleANE

I just installed the new version 7 hoping that several requests of the past would be implemented but with no luck. These are all about the behavior of the report. 1)In page 1 or 2, where it shows the IAM user defined table, the "IAM user defined" string is overlapped on itself and can't be read. 2)For big sites it takes minutes to just open the report. I guess this is related to the 3D scene being rendered every time. Wouldn't be easier to render the image when we save the image for the report and use that image as it is in the report? 3)Please give us the possibility of setting defaults for what pages we want in report and what graphs in those pages. Now we have to change them every time we re open the report. Hoping these get some attention, Best regards

To do this we usually keep the desktop on and connect to it using chrome remote desktop and use PVsyst this way. Best regards

Dear Solarguru, That is indeed how we do it, but you can't set it as default so you have to do this step every time you run a simulation. That was what we were requesting. Best regards

Thanks for your reply. I was using the forum to report bugs and ask info because doing so it contributes to common knowledge and you just have to answer once each item. From now on I will report by email hoping for a prompt response. Best regards

Dear all, It's month I don't see any answer to any question here on the forum from PVsyst members. Is this a forum problem or is it actually absence of PVsyst people? PVsyst forum has been a valuable mean of communication and it would be a pity to let it die. Thanks for your consideration and Best regards Michele

Hi, we recently noticed a strange behavior: setting the Global irradiance threshold (in the hidden parameters) to 0.0W/m2, brings the night consumption loss of the inverter to 0.0% too. We think this is just a bug but if it's not, please explain the reason behind it. Thank you and best regards

Hi, In version 6.80 we got the possibility of adding special graphs to the report and also we have 2 new default graphs. This is fine but it would be great if we could decide what graphs to be used as defaults and/or choose to show or not that page and keep it as default. Thanks for your attention and best regards

I think you should model at least the closest buildings in the 3D scene or you would loose the partial shading behavior that horizon line doesn't produce. Best regards Michele

Thank you for the clarification. It was to calculate First Solar spectral effect but actually that became possible directly in PVsyst now, so we will not need it anymore. Thanks for the good work on improving the software. Best regards

Hello, I recently was in need of exporting one year worth of hourly humidity data (from meteonorm 7.2) and couldn't find a way to do it directly. I know how to export these kind of data for other parameters (for example GHI, could save a hourly file during simulation) but couldn't find the humidity parameter to add to the result export file. I ended up exporting each month separately from the meteo data graphs tool (that doesn't allow for one year hourly graph/export). Is there a way to do it? Thanks in advance and best regards

Hi, Regarding the original topic: the problem is not really the small difference in numbers but the fact that it always changes between the first run and all the successive ones. If it was a rounding it would happen for all the runs in the same way or more randomly in different runs. Regarding the unexpected answer: this is the section of the forum dedicated to reporting bugs and this looks to me as a bug. I never said anywhere that this needs a high priority or anything similar and I didn't mean it as a critique. Usually bug reports from outside are welcome because they are free and bring improvement of the software, if it's not the case you can as well close this section. Thanks for your time and best regards Michele

Hi, You are right, I forgot to write it. I was on 6.75 version when outputting these but we also tried on a 6.74 PVsyst that we still had in the office and the same thing happens. As said before I would like to share the project file with someone from PVsyst but I cannot upload it here, so please advice where to send it. Best regards

Hi, We encountered what looks like a bug while running a second time exactly the same project with the same data. In the picture called "VCP losses" you can see the output of the first run of this simulation. First run output Then in the picture called "VCS losses" you have the output of the second run of exactly the same version just after saving, closing the software, reopening it and pushing simulation button again. You can see that shading related losses and the yearly Energy changed. Second run output I can also send the project file with the two versions saved, but I can't upload it here because it's a commercial project. In case it's needed, let me know where to send it privately. Best regards

Hi, I would run the simulation normally using whatever panel and inverter you prefer and then output hourly data of shading loss. Seen that in your scene there is no other shading apart from the poles, you should be able to distinguish when the shadows are on the panels and use a spreadsheet to count the hours that have more than zero of shading. Best regards Michele

Hi, The possibility of multithreading the shading computation has been a very exciting news for us because we usually work on very large scale project that usually required quite long computation times. But, from tests we did internally, it would seem that all the threads used for the calculation allocate memory in the same 2GB space that is the limit of 32 bits architectures. This creates situations in which having more cores is a disadvantage because it drastically multiplies the used memory and , when it passes the 2GB limit, brings crashes. As an example, I tested this on a model that usually required around 300MB memory during shading computation using single core. Enabling multithread computation (8 cores/16 threads system with 64GB memory) you can see, after pressing the table button, both the percentage of used CPU (therefore the number of cores) and the used memory going up and up in a short time and when the memory almost reaches 2GB, the CPU usage drops to 0% and the process freezes and closing the software is the only possibility. Now, one solution would be to compile PVsyst in 64 bits so it can access the entire memory of the system that is then enough to support multiple threads. Is this possible? Are there other possibilities? Thanks for your consideration. Best regards

Hello, The recent possibility of outputting the report with more than 1 decimal place is very useful and we would like to make it the default for our output. Is there such an option? If not, would be possible to create such a feature? Best regards Michele

Hello, I found a workaround for this. If you just click the scroll bar nothing changes , so you can't see other months data but, after you moved the scroll bar to the desired month (counting steps because you have no indication of the current month) try and resize the window of the diagram to full screen or , if you have it already full screen, shrink it down. This makes it change values for me. We still hope in a smoother operation in the future. Hoping I have been useful, best regards

Hi, I just installed the new 6.6.4 version and the change log says it includes a new tool for grouping orientations and such. It would be very helpful to have a tutorial or just a brief example of how to use it and where to manipulate correctly. Best regards

Thanks for your response. I sent you this DAE file by mail. Please inform us of your results. Best regards Michele

Hi, It is not a "looks" problem. The geometry is completely different. Please look at these two pictures, they are of the same model taken in front view and parallel view (not perspective). If needed I could send you the DAE file to try for yourself. Version 6.62 Version 6.63 By the way, what about my other question in the same post? Any suggestions?

Hello, after upgrading to 6.63 ver. we experienced a problem importing collada .DAE files. Impoted DAE in ver. 6.62 Same DAE in ver. 6.63 As you can see , the same file is imported wrongly in 6.63 so we had to downgrade to 6.62 to keep working. As a side note, all DAE or 3DS files exported from Sketchup are imported as they had the azimuth of the whole scene rotated by 180 degrees in all versions, is this another bug or it is intentional? Best regards

Hi, we mostly work on large scale solar plants following the shape of the terrain and so having a mix of many orientations. It is often difficult to separate them in groups keeping the correct ratio for inverters. It would be great to have a modality in which , during shading table computation, it would also compute the orientation for every single plane and the shadings relative to that orientation. It would probably increase the computation time but we think it would be acceptable anyway. After this it would have to calculate the effective transposition factor for the entire system and allow for mixing several orientations every inverter and actually do it automatically because they would be thousands. For us, having to wait hours for such a simulation would be acceptable in exchange for accuracy and reality of the simulation. Best regards Michele

Hi, I upgraded to 6.61 and this problem is still there, modifying them all by hand is too much. When could we expect a database upgrade or fix?

Sorry, disregard my previous mail and reply. I just sent you the whole project instead. It contains a previous variant that has being calculated successfully and the second one, called 5.2m pitch, that keep crashing when calculating shadings. Best regards Edit1: Normally I enable optimized calculation for shadings believing that it would speed up the process. Well, I found out that in this case, disabling it, the calculations go on without any problem using very little memory and we couldn't notice a speed difference. Please clarify the function of that option.

Hi, I just sent a SHD file that keep crashing on my pc to admin@pvsyst.com Best regards