Jump to content

j.meier

Members
  • Posts

    20
  • Joined

  • Last visited

  1. Hello, we have a similar issue, thats why I post it here. We have tried to import a shading scene with 2 different tilts (15° and 20°). If imported, PVsyst also builds the average tilt. Would it be possible to differentiate in 5° steps? It would be really helpful to be able to import a shading scene with different tilts. Best reagds
  2. You can try this https://www.pvsyst.com/previous-versions and I suggest if you update PVsyst always choose the option "parallel install" and not "upgrade". I have experienced a lot minor annoying problems since PVsyst 6.4.. thy get fixed one by one, but I am glad, that I still have my 6.3.9 version installed. Best regards
  3. Hi all, we have the same problem here. Best regards,
  4. Hi André, any new information on that? It has been a while since i send the Helios file.
  5. Dear PVsyst team, I ran into some trouble with importing shading scenes from Helios 3D in the new PVsyst version (6.4.). At a first glance, everything looks fine. But when I save the scene and close the editor erverything seems still to be ok. But as soon as I go back to the editor and read this scene I saved before, a lot of shading objects disappear. I tried the same in v6.39 and here everything seems to be good. Is it possible that this is caused tue to the now faster calculation of the shading table? I hope I was able to explain the problem. Best regards
  6. I did send an example project. Do you have any update regarding this topic? I noticed that the difference still occurs in PVsyst 6.41.
  7. Hi all, thanks for the new v6.40 and all the improvements I have seen so far, but: I have noticed that since I have updated to 6.40 the shadings: electrical loss acc to stings are twice as high as for PVsyst 6.39. I used the same simulation variant, same system same losses, just recalculated the shading table and noticed that these losses increased from around 1% to around 2%. Was the loss calculation underestimated in the older versions or is there another special reason for this? Can you please explain this change? Looking forward for your reply.
  8. Hi, I was wondering about the timestamp in the output file. If I want to check the average between 11-12 which value shall I take 11 or 12?
  9. Ok, thanks for your answer. I hope this will be possible once. ;)
  10. I have got a short question regarding the ground objects tool. Is it possible to Place a Tracker system instead of normal modules with this tool? This would be really helpful.
  11. Hi, I noticed a small bug regarding OND files since I have updated to v. 6.38. In some cases I get the message that the inverter is invalid. If I open the OND file the "Power Threshold" of the inverter is 0. This explains the message. (By the way, the OND file is from the PVsyst Database). Interesting to see that if I open the same Inverter in the same Workspace (should be the same OND file) in PVsyst 6.37 it shows the correct value. I noticed this beavoir for ABB PVS800-57-1000kW. But I recognized this bug in some other OND files too.
  12. Hi, I could imagine that this might be helpful in a case like this: You are working in a international operating company and using the newest version of PVsyst 6 to create a projekt or to help a colleague out. Than you export the project and send it over to your colleague lets say in asia. But he isn't using the newest version, he will have truble to read the project. Thats just a case, I could imagine.
  13. Hi, I'm missing the Iso-shadings diagram on some PDF-Printouts sinsce 6.37. Thanks for help.
  14. Thanks, but unfortunately this doesn't help.
  15. Hi, I have a problem, PVsyst dosen't notice that i defined two different orientations in the 3-D shading scene. I'm using PVsyst 6.34
×
×
  • Create New...