Rhett

Hi Linda, Thanks for your prompt reply. I look forward to the updated version of PVsyst that can take this into account as this is where the industry is moving towards. Regards

This is a pity as I have the exact same issue. As a utility provider, prioity should always be to charge the battery as this is revenue when discharging in peak periods. Has there been any further developments on this as at present it is a limiting factor to the tool. Thanks

Hi, I am just following the thread, I have the same question. Peak shaving in my mind is about generating revenue as an IPP by manipulating the time of use tariffs. This means that charging the battery should always be a priority to ensure it can be discharged in the peak time of use period. I understand the strategies PVsyst uses but this does not coincide with the industry per se. I am trying to design an 8.2MW plant with 2.5MWh of storage to be able to discharge in peak, particularly in winter where the peak tariff costs 3 x more than the summer peak tariff in South Africa. In winter I get zero values for the battery discharge when I run the simulation. I know why this is but it does not make sense as it is not a true reflection of how the plant would be operated. I would always prioritize charging the battery first with any excess power being evacuated to the grid. Is this something PVsyst is taking into consideration for near future versions, because at present it is a limiting factor?

I agree, it is very labourious and confusing. Struggling for days to make heads or tails of the design tool. Coming from a Helio background its seems very un-userfriendly

Thanks Linda, appreciate the speedy reply. It seemed to work to increase the the tolerance, I am now sitting with 6 orientations. I am busy working through the system config and sub-arrays. Will be in touch if I struggle with it. Thanks

Hi everyone, I am facing a very similar issue. I have complted a roof top design for a 6.7MW rooftop design from Sketchup (using Skelion) and when it comes to rendering the design in PVsyst, I get the same error message. I have looked at the orientation managment tab but cannot figure out how to group various (but similar tilts) together. Worse off, sections of roof that are mixed over a a north and south facing orientation but on the same inverter bank. ie strings split over two orientation roofs. Just want to add, I am new to PVsyst and come from a Helioscope background where the the rendering is far more simple, however on this scale cannot provide what I need. I have spent the last month learning PVsyst through many tutrials and see the potential however I am struggling with the final polished structure. The rendering alone took me 2 weeks to understand.