Jump to content

Jen212

Members
  • Posts

    4
  • Joined

  • Last visited

  1. Hi Julien I downloaded v6.3.0. v6.3.1 still remains on my PC - it was not replaced. When I opened v6.3.0 and tried to load a project, I got the same errors again. As before, every time I press OK, the error reappears with the next filename. This time, when I pressed OK several times, the error message changed to this:
  2. Hi Julien Thanks for your help. I have tried: - Restarting the software - Restarting the computer - Veryfing that no other network users are accessing this folder simultaneously - Opening the folder in Windows Explorer before opening PVsyst But I still get same errors. So it seems that v6.31 thinks the files are already open when it is only itself trying to access them. Is there any way to check at your end if this is what is happening? Jen
  3. Hi We just upgraded to v6.31 using the 'Check for update' function within the PVsyst software. Now when we try to select a site, project or meteo file we see an error saying PVsyst cannot open the file (screenshot attached).When we press 'OK', this message is repeated for every single file in the directory. The directory is definitely mapped correctly as the Workspace and these files are not open in any other software. Thanks, Jen
  4. Hi I am having this same problem. I import a Helioclim file for a UK site. Helioclim data timestamps are in end format (07:00 refers to data between 06:00 and 07:00) and PVsyst works in start format (according to the Help). Helioclim is given in UTC and the site is in Britain so I set the meteo file time zone as 0. But then I get the warning "The meteo values are shifted -60 minutes by respect to the time defined by the Timezone of your reference site". Regardless of the number I enter for the Time Shift Correction, the data in the hourly GHI table does not change and the warning does not disappear. I.e. the value given for 7:00 in the Helioclim csv is quoted for 7:00 in the PVsyst table, even though it should be 1 hour different due to the timestamp format difference. Can you see what is wrong? Many thanks
×
×
  • Create New...