Jump to content

dtarin

Members
  • Posts

    775
  • Joined

  • Last visited

Everything posted by dtarin

  1. Yes, it is correct that a 3D shade scene is more representative. The edge refers to the the modules which are along the edges of the array. If you have a square block, it is the first row, top row, left side, and right side. These modules receive less shading, more reflected irradiance, etc, and hence more energy.
  2. Check your PAN file. Your Vmp value does not seem correct, it is too high. For a 1500V system, you should be in the mid to high 20's for string length. You also want a higher DC/AC ratio, 1.2 to 1.3 good range. I suggest getting a new PAN file, or double checking the IV characteristics against the datasheet.
  3. dtarin

    CSV file

    Find this template, and populate it with your data. The template is located here: C:\Program Files\PVsyst7.1\DataRO\PVsyst7.0_Data\Templates (or whichever version you are using). The template filename is PARAMS_Hourly_Parameter_Template.csv. This is what it looks like after loading the template file.
  4. Once you're ready to simulate, click advanced simul. menu, select output file, check filename so that a 8760 file will be generated, press ok. click batch simulation, check the box create hourly files, and create pdf report; verify your variable under test, and the output variables under results variables specification, press okay. run simulation. 8760 files will be in /UserHourly, PDF files will be in /UserData, BatchParams and BatchResults will be in /UserBatch
  5. When importing a custom weather file, create a new conversion format based on your data file. There is a place to update the time shift. You will need to import the meteo file first each time to see the time shift, and then go back and adjust in the conversion format as shown. If you want to upload the excel file for your data as a template, I can create a conversion format file for you. Just fill in all of the data with 1's, leave the headers, date, and other formatting as is.
  6. Disable mppt share. Set to 14 modules in series, 30 strings.
  7. They will select one of the default values PVsyst has generated to the right of it.
  8. Construct two identical zones, one in E direction, one in W direction. Populate, then relocate the modules from one zone next to the other.
  9. If you are using backtracking, all tracker tables in the shade scene need to be at the same tilt angle. They can have different Z-axis heights, but the tilt must be the same throughout. The software isn't there yet for accommodating trackers on terrain with varying tilt angles while backtracking.
  10. It is done the same way as with fixed tilt, by defining the partition size.
  11. You should increase the number of modules in series.
  12. You can set this in hidden parameters to allow a lower DC/AC ratio.
  13. It means you have the MPPT enabled for multiple subarrays (4). Config 1 or 2 means you can have two different configurations if you wanted subarrays 1 and 2 to be together (input into same inverter), and 3&4 into another (or some other combination). To utilize the mppt share, check the square boxes you wish to have operate as such, and assign to a configuration, then balance Pnom ratios if that is the correct approach for your system.
  14. The trackers imported with PVcase are single, individual tables. PVsyst requires a set of tables to be present in the shade scene. If you select a table in your existing shade scene and open the options, you will see there is one tracker row. If you set the number of trackers to 2, you will be able to utilize backtracking. Make note that when importing from PVcase, if your trackers are at different slopes in the N-S direction, you may run into errors, especially if trying to model bifacial.
  15. Hello, I am getting what seems to be a bug for the HV transformer definition, cannot enter generic values. Anyone else? Version 7.1.5
  16. Be sure to count the number of MPPT inputs in the system definition, so that it totals to one inverter. If you have 15 mppt inputs on the inverter, you should have 15 utilized in total between the mixed sub-arrays: sub array 1: 8 mppt inputs, N strings of module A sub array 2: 7 mppt inputs, N strings of module B Total mppt inputs: 15 Total inverters: 1
  17. Yes, I believe this has been an occurrence for quite some time.
  18. Determine the power gain due to the back side through simulation, and multiply it with the front side current you would use with a monofacial module.
  19. It does not include the electrical loss according to strings, as this is an electrical loss, not a light loss, and dependent on partition definition, electrical effect %, etc.
  20. User NREL viewer, download the PSM TMY3 meteo file for albedo. https://nsrdb.nrel.gov/ Edit: SolarGIS also provides satellite based albedo for specific sites.
  21. Are you referring to the mismatch loss? Yes, it should be lower for microinverters, <1%.
  22. Hello, It would be great if users could select which variants they wanted exported when exporting a project. An expanding submenu where users check which variant to include is one example.
  23. Search the forums, there are some existing posts. https://forum.pvsyst.com/viewtopic.php?f=25&t=5073&hilit=mppt Arrays 1 and 2 are straight forward. Arrays 3 and 4 in PVsyst are the two configurations for the last array. In these two arrays, you will check the mppt share box, and balance power Subarray 1: 48 strings, 33 modules in series, 4 inverters total Subarray 2: 24 strings, 32 modules in series, 2 inverters total Subarray 3: 10 strings, 32 modules in series, 5 mppt inputs (check "use mppt sharing") Subarray 4: 2 strings, 33 modules in series, 1 mppt input (check "use mppt sharing") I dont know what inverter you are using, but you can modify it to have 6 mppt inputs. Allocate 5 to subarray 3, and 1 to subarray 4. The link above should help. This will be equal to 1 inverter.
×
×
  • Create New...