Alberto

Hello all, I am working on a sensitivity analysis for a grid-connected hybrid system (PV + BESS) and I'm running into an issue with the "Batch mode" (parametric simulation). My goal is to run a simulation where I vary the Number of batteries in parallel to find the optimal storage capacity. The Problem is that I can set the N_bat_parallel as a batch variable, but when the simulation runs, it fails with a warning for each new step. The error is: The problem seems to be one of parameter co-dependency. The batch mode correctly changes the number of batteries, but it does not automatically update the associated "Charging max. power" and "Discharging max. power" parameters in the storage definition. This creates an invalid system. For example, the simulation tries to run a case with 20 batteries but still uses the original charging power that I defined for 10 batteries, leading to an impossible C-rate and the current limitation error. Is there a way to solve this within the batch simulation tool? Ideally, I would like to define the PCharge_max parameter as a function of the batch variable (e.g., PCharge_max = N_bat_parallel* P_charge_per_battery; This would be possible if charge and discharge battery parameters were simply available in the batch mode. I am aware that I can manually create multiple "variants" and adjust both the number of batteries and the charging power in each one. However, this is very time-consuming and defeats the purpose of the automated batch mode for a wide sensitivity analysis. Is there a built-in feature or a known workaround to manage these co-dependent parameters in a single batch run? Thank you for any advice you can provide. Best regards, Alberto

Just bumping this for visibility. I'm still looking for some help with this. Thanks in advance!

Hi everyone, I’ve been running some tests with the Automatic Altitude tool because I was getting some odd results. After completing them, I still don’t understand which point PVsyst takes as a reference to perform the align based on the lowest, middle, or highest point. As you can see in the image, when the object to be positioned has a flat base, the tool behaves as expected; however, when it is tilted (it’s a square polyhedron), the align function doesn’t seem to have any effect. What’s surprising is that if the polyhedron is rotated in azimuth, the align tool does seem to vary the object’s height. Does anyone know the criteria PVsyst uses for this? Is there any documentation available on this? Thanks in advance!

Dear PVsyst Team, First of all, congratulations on the software update. Version 8 represents a significant advancement and will greatly benefit those of us who frequently use PVsyst. Specifically, the new feature allowing topography data import is incredible. However, I’ve encountered a challenge when working with the import function, as it’s difficult to adjust the data to the desired area from the import window. Having a measurement tool within that window would be extremely helpful. Additionally, in the tutorial on topography importation https://www.pvsyst.com/wp-content/uploads/2024/10/pvsyst-tutorial-v8-import-topography-en.pdf, it is mentioned that cropping can be done using the Ground Edition tool. However, I cannot find this button in my PVsyst. It seems to be available for terrain images but not for topography data or ground object. Could you please guide me on this matter? Thank you in advance!

Hello Lazare, Thank you very much for the prompt reply. In my opinion, the implementation of this options would be an interesting improvement for the software. Best regards, Alberto

Hello, In systems with three different orientations, in the "iso-shadings diagrams" section only two graphs, corresponding to orientations #1 and #2, are shown. My question: Is there any way to include all three near-shadings graphs in the report? For example, in the "Horizon profile" section the three graphs are displayed by default. Thanks in advance, Alberto