MicheleANE

Hi, It probably wouldn't affect the results but I wonder if the far shading loss shouldn't come first in the list instead of the change in irradiance due to POA angle. My reasoning is that light would be first influenced by the horizon and then by the POA angle. Please feel free to disregard this if it doesn't make sense. Best regards

Hi, it would be great, for large scenes, to know roughly how much the shading calculation progressed. So, a progress counter or bar and/or an estimate time would be a great addition. Best regards

Hi, Thanks for your reply. I could transform the faces to pv but then i am not able to properly set the string partition of the arrays. I think it's because they become polygonal instead of sheds. Any help in this is greatly appreciated. P.s.: the next version you talk about, when is it coming out? Can we expect it soon to fix minor things of the new version?

Hello, Version 6.60 3D view is very nice and speeds up our workflow greatly so thank you very much for it. Though, when setting a view and after running the simulation (at least for large scale projects), nothing appears in the report page for shadings apart from the loss graph. Best regards Michele

Hello, I'm trying the new import possibilities of version 6.60 with DAE files. I can import the scene with no problems and it shows up very nicely and smoothly but I expected to be able to define which parts are modules (active planes) and which are not. Though I cannot find this function. Is this possible or, maybe, planned for the future? Thanks in advance Best regards Michele

Hello, I noticed a mistake in the sizes of UP Solar panels. They are all the size of 72 cells ones even if they are reported as 60 cells. I also verified this on UP Solar website: http://www.upsolar.com/uploads/UploadFile/US-P11-12%20Mono%2060%20Black_compressed_20170203.pdf Best regards

Hello, We often work on quite large projects and the recent speed improvement of PVsyst during the shading calculation phase was a gift from heaven for us. Because of this we maybe became too used to not optimizing the shading scene before porting it to PVsyst because the calculation time was short enough anyway. This brought out a new issue that we never had before, the calculation of the shadings used more than 2GB of RAM memory and, being PVsyst 32bit, crashed. Now, take this as an inquiry more than a request, we would were wondering if you are planning of releasing a 64bit version of PVsyst so it could overcome the memory limit and let us be even more lazy with the optimization. Thanks for the wonderful updates so far and best regards. Michele

Hi, we would like to inherit 2 licenses from a company that ceased operations and of which 2 members are coming to work with us. They already transfered the license to other machines but the name of the licensed company that appear in the bottom of the report pages is, of course, the one of the ended company. How to change it to the one of our actual company? Best regards

Hi, In Japan, for solar projects over 2MW, they require to inject to very high voltage grid (66KV, 154KV) and to do this, often there are several transformers to elevate the voltage first from inverter output to 22KV, then from 22KV to 66KV or 154KV. Would be possible to add a tool to estimate the AC ohmic losses with this kind of configurations? More specifically the possibility to specify cable section and length for the different steps. Thanks in advance and best regards. PS: Please let us know something regarding the post "PVsyst becomes very slow in every part when loading a big 3d scene" in the bugs forum.

Hi again, Just now I upgraded my copy of PVsyst to 6.41 hoping it would solve this problem. It didn't. Could you examine the project I sent you? If yes, could you understand what is the cause of this problem? I don't really understand why it should re-verify the interpenetration of the tables while operating other parts of the software and also if I disable that function. Please let us know something regard this because it's causing a big loss of time. Best regards Edit: Some time passed, new version (6.42) is out, installed it, but this problem is still there. A temporary workaround would be fine too but please let us know something.

Hi, with the new version (6.40), the time for the shading table calculation actually decreased around 20 times like said in the change log but, regarding the slowing of the whole software (also unrelated panels), there is no change. I tried disabling the "Ignore interpenetration of PV fields" or enabling it but there was no difference in the response. I am sending you the project file by email like you suggested using as subject the title of this thread. Please let us know what can be done to improve this aspect or if you can solve it with a patch or update. Best regards

Hi, I can understand that managing big data in the 3d scene can make that part of the software slow but we are experiencing the same problem also after closing the 3d scene window and just browsing around in the software (opening other panels, like detailed losses or system). Is there something we can do to avoid this problem? In another thread I was told that activating optimized shading calculation and ignoring the interpenetration of modules in the 3d scene could help, but it just changed a little and is not enough at all. Could an eventual fix for this be included in the next update? When could this update be expected? Thanks for your time and best regards.

Hi again, The workaround that Andre proposed makes it a little better but it still takes a long time to open various parts of the software. The shading computation I was talking about is actually the one of the tables, inside the 3d editing part of PVsyst, so it can't be postponed because it is required for the simulation, but correct me if I'm wrong. What would you say are the main factors speeding up these calculations, speaking of hardware ? Thanks for your time Best regards

I often do simulations of big sites and they require quite a long time to complete the shading calculations in the 3d scene part. It happened that I left them doing it overnight or anyway when I'm not around and it can happen that for any reason the computer restarts or switch off suddenly, especially after the calculations are over but before I could save the simulation therefore losing all that work. Could you make it so it would save the shading tables automatically when it finishes calculating it? On a different but related point: is it possible to make it so heavy 3D scenes don't slow down every other part of the software? Now if I want to change something after importing a big scene, it takes minutes just to open different panels. Thanks for your time and best regards

Sorry for double post, I just wanted to throw in there another idea; many software that require heavy calculation are shifting to GPU usage (especially rendering and physical simulation software), is such a development even thinkable for PVsyst? Recent GPUs provide a huge amount of computing power for cheaper prices than powerful CPUs so that would help keeping the price for a PVsyst dedicated system in the affordable range. Thanks for your time, best regards.

Very good to know that you are working on it. Good luck on your efforts to make it happen, best regards.

Hello, I imagine it would require quite a big effort from you but, would it even be possible to make PVsyst use multiple threads for the shading table computation and other heavy load operations? If it's possible, are you considering taking that step in the future? Thanks in advance for your attention, best regards. Michele