Jump to content

unilhexio

Members
  • Posts

    85
  • Joined

  • Last visited

Everything posted by unilhexio

  1. Dear Ruslan, I am glad we found the mistake. It is very common to skip the radians conversion to operate with trigonometric operators in excel. Best regards!
  2. Dear Ruslan, I think you are doing something wrong. Our formulas are different. You are substracting cos β (it does not have units) and L (its units are meters). I think the following image can clarify the problem: https://s28.postimg.org/4ufl2kv8p/20170110_173439.jpg For your example (β=36 and L=3.3): θ = arctg ( L*sin β / (Pitch - L*cos β)) Then: θ = arctg ( 3.3*sin 36º / (9 - 3.3*cos 36º)) = = arctg ( 3.3 * 0.58779 / (9 - 3.3 * 0.809) = = arctg ( 1.93969 / 6.33024) = arctg (0.3064) = 17.036º If you do not find the problem, then tell me and I will write you an email to receive your excel calculation. Are you converting the tilt angle into radians in excel calculation? Regards.
  3. You are welcome. Some manufacturers provided me some 1500 Vdc .PAN files. I compared them with the 1000 Vdc version and the only change I found was the Maximum Array Voltage definition. If you use 1000 Vdc string sizing with a 1500 Vdc inverter, the system will be working out the inverter MPPT range Regards,
  4. Dear Rusian, Your formula is the following: θ = arctg ( sin β / (Pitch/L - cos β)) And the one I obtained is: θ = arctg ( L*sin β / (Pitch - L*cos β)) These are not same. Be aware that you are subtracting 'L - cos β' (this is, a distance in meters and cos β with no units)... I have tested my formula and it leads to exactly the same result than PVsyst do. Regards.
  5. I think your formula is wrong. This is the one I obtained: θ = arctg ( L*sin β / (Pitch - L*cos β)) Regards,
  6. You can change the minimum temperature for absolute voltage in 'Albedo - Settings' dialogue. In other term, if you are using a 1500 Vdc inverter, it would be more suitable to use 1500 Vdc PV modules...
  7. Yes... this complete set of simulations is a very demanded info from financials. It wolud be very useful.
  8. No problem. Your suggestion is related with my one.
  9. Would be great if in the final report the point where the limit is applied is mentioned (i.e. @inverter level or @injection point).
  10. Woluld be great an option to simulate in batch mode a long term period of time (i.e. all simulations for 20 or 25 years, for example), by increasing PV module degradation year by year automatically, and geneating pdf reports. Regards.
  11. It is really a bad news...
  12. Solved: I have introduced a negative pitch.
  13. Hi, I'm trying to do a shadow scene for a SA tracking system with a misalign. The problem is I can not introduce a negative value for it, and the consequence is that the system is symmetrical to the scene I need: http://fotos.subefotos.com/1f94f924ca54f692adfa5304dbee57f0o.jpg What can I do to obtain a misaling from left to right (west to east)?
  14. I do not mean that the impact of a very low horizon is significative. My question is more related with the reason of why is this horizon not mentioned in PVsyst report. Even 0% PV losses are mentioned in the final report... But, of course, may be I have no idea...
  15. Hi, I have just defined the horizon line drawing for a project as shown: http://fotos.subefotos.com/b8e7869e471377bdb06b4f79cb8f51f9o.jpg But it does not appear on the final report. Even, as you can see, the 'Horizon' option appears turned off: http://fotos.subefotos.com/b87276a6607ef0f1858f62e55ea1e262o.jpg May it be that the horizon is too low to be taken into account for the simulation?
  16. I have just updated to 6.4.1, but the problem persists.
  17. Hi, I have been working for three days with the latest version, but suddenly the message "An error occured in PVsyst" appeared. I can not execute the software. I have reinstalled the software but the problem persists. Thanks. Edition: Going back to PVsyst 6.39 works. If I update the software, it crashes again and again. Bug report says ""invalid characters in path"
  18. Ok. Thanks.
  19. Hi, In current version of PVsyst v6.35, the following message is generated in the final report, independently of the field type: http://sia1.subirimagenes.net/img/2015/04/15/150415063647517832.jpg See that in this case I have a single axis tracking system. Regards.
  20. Thank you, André.
  21. Hi, Aparna, The exposure to wind has a cooling effect depending on the mounting of the PV modules, increasing the yield. You can read more accurate information about this on PVsyst help ("Array thermal losses"). Regards.
  22. No reply? It is really a problem...
  23. When defining 2 sub-arrays, the arrays characteristics is void in the final report: http://sia1.subirimagenes.net/img/2013/12/11/131211093518893329.jpg It is happening since the latest update, v6.13. Regards.
  24. Hi, Are both systems identical? Same module and inverter manufacturers, shadings scenes, row distance, etc... It may also be related to wind expossure, module degradation, mismatch losses... Regards!
  25. A recurrent failure in iso-shadings diagram (in the pdf final report or in preview) is the following text: http://sia1.subirimagenes.net/img/2013/10/01/131001043542340107.jpg The text doest not match with the studied case, as can be seen in the following pictures: http://sia1.subirimagenes.net/img/2013/10/01/131001043820156607.jpg http://sia1.subirimagenes.net/img/2013/10/01/131001043820611554.jpg It doesn't happen all the time and I can't find a reason for this.
×
×
  • Create New...