EFEN

Hello PV*SOL Community / Support Team, I am currently creating a manual entry for a Growatt MAX 100-125KTL3-X LV inverter. To ensure the simulation is correct, I have been comparing the manufacturer's datasheet with the PV*SOL Help Guide and existing native inverter entries in the database. I’ve found several "grey areas" where terminology mismatches make the data entry process confusing for users: 1. DC Power & Clipping Logic The datasheet lists a "Max. Recommended PV Power" of 150 kW for a 100 kW AC model. Should "Nominal DC Power" match the AC rating (100 kW) or the DC input capacity? Is "Max. DC Power" the absolute limit where the software will start clipping the yield? 2. Defining Max. Power per MPP Tracker Since datasheets often do not specify the maximum power limit for a single tracker, I calculated a value of 18.75 kW using the following logic to allow for asymmetric stringing: Formula used: Max Power per MPP = (Nominal AC / Number of Trackers) * 1.5 (DC/AC Ratio) * 1.25 (Flexibility Factor) The 1.25 factor is derived from the ratio between Max. Short-circuit current (40A) and Max. Operating current (32A). Is this a valid workaround for PV*SOL, or is there a standard "rule of thumb" recommended by Valentin Software? 3. Global DC Data vs. Tracker Data It is unclear if the "Max. Input Current" in the main Electrical Data DC tab is a global hardware limit (sum of all trackers) or a per-tracker limit, as there is a separate field for this in the MPP tab. When comparing with native entries, this isn't always consistent. 4. Physical Inputs vs. Trackers For an inverter with 10 Trackers but 20 physical inputs (strings), should the "Number of DC inputs" be 20? My reference native entries show different criteria for this field. Feedback on Software Clarity (User Experience) I would like to suggest that the database entry interface could be significantly improved. Currently, the terminology used in PV*SOL (e.g., "DC Nominal Output") often differs from the standard terms used in modern manufacturer datasheets (e.g., "Max. PV Power" or "Full power MPPT voltage range"). Suggestions for the development team: Tooltip Synonyms: Add tooltips that list common datasheet synonyms for each field. Input Mapping Guide: A simple "How-to" graphic showing where to find each value on a standard datasheet would reduce the learning curve and prevent simulation errors. https://help.valentin-software.com/pvsol/en/databases/components/inverters/ I have attached a PDF mapping these discrepancies to illustrate my point. I look forward to your guidance on these technical values. Best regards, Juan Create Inverter.pdf

Hello PV*SOL Community / Support Team, I am currently creating a manual entry for a Growatt MAX 100-125KTL3-X LV inverter. To ensure the simulation is correct, I have been comparing the manufacturer's datasheet with the PV*SOL Help Guide and existing native inverter entries in the database. I’ve found several "grey areas" where terminology mismatches make the data entry process confusing for users: 1. DC Power & Clipping Logic The datasheet lists a "Max. Recommended PV Power" of 150 kW for a 100 kW AC model. Should "Nominal DC Power" match the AC rating (100 kW) or the DC input capacity? Is "Max. DC Power" the absolute limit where the software will start clipping the yield? 2. Defining Max. Power per MPP Tracker Since datasheets often do not specify the maximum power limit for a single tracker, I calculated a value of 18.75 kW using the following logic to allow for asymmetric stringing: Formula used: Max Power per MPP = (Nominal AC / Number of Trackers) * 1.5 (DC/AC Ratio) * 1.25 (Flexibility Factor) The 1.25 factor is derived from the ratio between Max. Short-circuit current (40A) and Max. Operating current (32A). Is this a valid workaround for PV*SOL, or is there a standard "rule of thumb" recommended by Valentin Software? 3. Global DC Data vs. Tracker Data It is unclear if the "Max. Input Current" in the main Electrical Data DC tab is a global hardware limit (sum of all trackers) or a per-tracker limit, as there is a separate field for this in the MPP tab. When comparing with native entries, this isn't always consistent. 4. Physical Inputs vs. Trackers For an inverter with 10 Trackers but 20 physical inputs (strings), should the "Number of DC inputs" be 20? My reference native entries show different criteria for this field. Feedback on Software Clarity (User Experience) I would like to suggest that the database entry interface could be significantly improved. Currently, the terminology used in PV*SOL (e.g., "DC Nominal Output") often differs from the standard terms used in modern manufacturer datasheets (e.g., "Max. PV Power" or "Full power MPPT voltage range"). Suggestions for the development team: Tooltip Synonyms: Add tooltips that list common datasheet synonyms for each field. Input Mapping Guide: A simple "How-to" graphic showing where to find each value on a standard datasheet would reduce the learning curve and prevent simulation errors. https://help.valentin-software.com/pvsol/en/databases/components/inverters/ I have attached a PDF mapping these discrepancies to illustrate my point. I look forward to your guidance on these technical values. Best regards, Juan Create Inverter.pdf