4 Ways to Handle Not Being Able to Select Modules in PVSyst

Table of Contents

• First, isolate the cases where modules cannot be selected

• Solution 1: Review the database search criteria and filters

• Solution 2: Verify whether module data has been registered and confirm the specification values

• Solution 3: Correct inconsistencies between the inverter and string conditions

• Solution 4: Review the project conditions and design assumptions

• Practical checks to avoid stumbling during module selection

• Summary

First, isolate the cases where a module cannot be selected

When you feel you cannot select a module in PVSyst, the first thing to do is break down exactly what is happening. Saying "cannot select" covers several different situations: the target module does not appear in the search screen; it appears in the list but is not enabled as a selectable option; after choosing the module the array configuration cannot be completed; or you cannot proceed because of pre-calculation errors or warnings.

If you continue to adjust settings without performing this isolation, you may end up altering other conditions without understanding the cause and stray from the original design intent. In practice especially, module type, installed capacity, PCS capacity, number of strings, series-parallel configuration, installation orientation, and tilt angle are all interrelated. If you arbitrarily change any one of them, even if the simulation results pass, the model may no longer reflect the actual design conditions.

The first thing to check is whether the module you need exists in the database. PVSyst has a module database, and simulations are performed by selecting from the registered modules. However, not every model is necessarily registered. New models, domestic-only specifications, project-specific variants, legacy model numbers, or products whose model number notation differs in part may not be found immediately even when searched.

Next I want to check whether candidates are being hidden by search criteria or filters. If you narrow the results by manufacturer name, output, cell technology, module type, certification category, or the like, the module you’re looking for may be excluded from view as outside the conditions. In particular, if filter settings used for a previous project remain, the number of candidates can become extremely small, making it easy to mistakenly conclude that “no modules are registered.”

Furthermore, even if the module itself can be selected, errors may occur when combined with the inverter. This is more a problem of electrical design conditions than of module selection. Examples include the number of modules in series per string being too small to fall within the operating voltage range, or too large so that the open-circuit voltage at low temperature exceeds the upper limit; an extreme imbalance between DC capacity and AC capacity; or the MPPT input current or power conditions not being met. In such cases, before replacing the module with a different one, you need to check the number of modules in series, the number of parallel strings, the inverter capacity, and the input conditions.

PVSyst warns about contradictions in design conditions, but for beginners the warning messages can be difficult to interpret. Even in situations where it appears that a module cannot be selected, it is often not that the module is "unselectable" but that the chosen conditions do not constitute a valid system. Therefore, it is important to first distinguish whether the issue is with the module search, database registration, electrical combinations, or project settings.

By performing this separation, the order of steps to take becomes clear. If a candidate does not appear, check the search criteria and the database. If a candidate appears but cannot be used, check the specification values and compatibility of the module data. If a combination error occurs, check the inverter and string configuration. If you are stuck on the overall project settings, review the location, weather data, system type, and installation conditions. Below, following this flow, I will explain four common countermeasures used in practice.

Solution 1 Review the database search criteria and filters

One of the most common reasons you can’t select a module is that candidates are not displayed due to the database search criteria or filters. In PVSyst, when selecting a module you can narrow candidates by manufacturer name, model, power output, technology classification, registration category, and so on. This feature is convenient, but if even one criterion doesn’t match, the desired module won’t appear in the list, so to beginners it looks like “not registered” or “cannot be selected.”

The first thing to check is the string you’re entering in the search box. Solar module model numbers may be represented slightly differently across documents. Even small differences — the presence or absence of hyphens or spaces, how output values are written, trailing specification codes, or regional identification codes — can prevent the search from finding a match. For example, if entering the official model number from a catalog doesn’t return results, effective approaches are to search using only part of the model number, search by output value alone, or broaden candidates by searching with the manufacturer’s name.

Next, check whether any previous search conditions remain. On the PVSyst screen, the conditions or filters you selected previously may still be applied. For example, if you narrowed the results to a specific output band for one project, modules with a different output you search for in another project may not appear as candidates. Clear the conditions once to return to a state where all candidates are displayed, and then search again — you may be able to find the module you are looking for.

Also, it is important not to over-filter by manufacturer name. In practice, the manufacturer name listed on catalogs or quotations may not exactly match the registered name in PVSyst. Differences in company name notation, division name, group name, abbreviations, or former names can cause no candidates to appear even when you think you are searching for the correct manufacturer. If you cannot find it by manufacturer name, temporarily remove the manufacturer filter and try searching using part of the model number or the nominal output.

Care is needed even when searching by output value. The nominal output of a module is often listed as an integer in catalogs and quotations, but in databases it may be registered by series or as an approximate value. Also, multiple models with the same output can differ in cell count, voltage characteristics, current characteristics, dimensions, and temperature coefficient. Therefore, rather than simply selecting candidates whose output values match, you must always check the detailed specifications of the candidates you find.

When setting filter criteria, pay attention to the classification of module technologies. If classifications such as monocrystalline, polycrystalline, thin-film, bifacial, monofacial, or special cell configurations are applied, you may not find any candidates if the filter is narrowed to an unintended technology category. In particular, bifacial modules and high-power modules may be treated in separate categories from common monofacial modules, so it is effective to remove the technology-classification filter and check.

Also, if you are reusing old project files, you need to pay attention to the database environment they reference. When you copy a project created in the past and apply it to a new project, old conditions and some selection information may remain. Duplicating a project for reuse is efficient in itself, but on equipment selection screens—such as for modules and inverters—it is important to always reselect items to match the current project.

When reviewing search criteria, it's best to search broadly first and then narrow down, rather than starting with complex filters. First, clear the filters and expand candidates using the manufacturer name or part of the model number. Then check output, voltage, current, cell count, temperature coefficient, and so on, and select those closest to the desired specifications. If there are too many candidates, gradually add output ranges or technical classifications to narrow them down. Following this order makes it easier to avoid overlooking items due to overly restrictive criteria.

Practitioners should be particularly careful not to rush into choosing a similar item simply because the correct one cannot be found. If a candidate does not appear due only to the search criteria, the correct data may already be registered. Choosing a different module with similar output can lead to differences in voltage, current, temperature characteristics, area, power generation, and string configuration. What appears as a small difference in the early stages of simulation can become an impact that cannot be ignored in design comparisons and project feasibility evaluations.

Simply performing basic operations—clearing all search conditions, shortening the model number for searches, searching by output or specifications instead of manufacturer name, and removing the technology-classification filter—can resolve many of the "unable to select modules" problems. The database's candidate display is the entry point to design. Expanding the search criteria here and checking calmly, without rushing, leads to accurate simulations.

Solution 2: Check Whether Module Data Is Registered and Verify Specification Values

If you still cannot find the module you are looking for after reviewing your search criteria, consider the possibility that the module data itself has not been registered. PVSyst includes many module datasets, but not every model available on the market is necessarily registered. In particular, new models, limited specifications, model numbers intended for domestic projects, OEM-supplied products, and variants with different power outputs may be absent from the database.

In this case, the first thing to do is to check the electrical characteristics listed in the catalog or datasheet. Typical items you will need include the nominal maximum power, the voltage at maximum power, the current at maximum power, the open-circuit voltage, the short-circuit current, the temperature coefficient, the number of cells, the module dimensions, and whether it is single-sided or bifacial. These are not only used to calculate energy production, but also affect string configuration and compatibility checks with the inverter.

If the desired model is not in the database, a module with similar specifications may be used as a substitute, but this must be judged carefully. For practical rough estimates or initial comparisons, it can be acceptable to provisionally use a module with very similar specifications. However, for simulations intended for submission, financing documents, internal approvals, or studies close to construction design, it is not desirable to proceed with a provisional substitution. This is because even modules with the same rated output can have different voltage and current characteristics, which will change the number of modules in series and parallel, wiring losses, temperature-related losses, and the occurrence of clipping.

In PVSyst, users may need to create or edit module data themselves. When registering new data, it is important to enter the catalog values accurately and not confuse units or conditions. Special care should be taken not to mix values given under standard test conditions with those applicable to actual operating conditions. Module specification sheets may list values for multiple test and temperature conditions. If you transcribe numbers without understanding which values should be entered, the simulation results can become unrealistic.

Entering the temperature coefficient is another common point to watch. Because a module’s output is affected by temperature, the temperature coefficient is related to annual energy generation. If you get the sign, unit, or target parameter of the temperature coefficient wrong, temperature losses may be over- or under-estimated. For example, you must be careful not to confuse the temperature coefficient of power output with that of voltage or current. When entering values while referring to the datasheet, it is important to verify each item name one by one.

Extra caution is required when handling bifacial modules. In settings related to bifacial reception, rear-side light reception rate, ground surface reflectance, racking height, row spacing, and the conditions of the mounting surface all affect power generation. If you cannot select a module or the expected candidates do not appear, it may be because you are searching under the monofacial (single-sided) category. Also, using an approximate module that is not registered as bifacial may result in the handling of rear-side generation differing from the design intent.

When module data are entered manually, do not proceed straight to the power generation calculation after input; first verify the consistency of the specification values. Check whether the open-circuit voltage is abnormally high, whether the short-circuit current is off by orders of magnitude, whether the product of the maximum-power operating voltage and current is roughly close to the nominal output, whether the sign of the temperature coefficient is reasonable, and whether the dimensions and area are realistic. Many input errors arise from unit mismatches, order-of-magnitude mistakes, misplaced decimal points, or misreading symbols.

Also, when you newly create module data, verify that the project is correctly referencing that data. Even if you believe you created the data, the actual system configuration may have selected a different existing dataset. It is important to cross-check on-screen not only the module name but also key values such as output, voltage, current, and dimensions to confirm that the intended data is being used.

If multiple people in a company use PVSyst, rules for managing module data are also important. If each person creates their own data, there may be multiple entries with the same model name but slightly different input values. This can cause simulation results to differ between projects. In practice, keeping track of the creation date of registered module data, the source specification used for input, the person who entered the data, the verifier, and the projects in which the data was used makes later verification easier.

Even if a module is not in the database, you can proceed with the simulation if you register it using the correct specification values. However, the registration process is not merely data entry; it is an important step that establishes the assumptions for the power generation calculation. Rather than carelessly choosing a similar model just because a search did not find the exact one, confirm whether the target module is unregistered, missing due to a different notation, or whether a substitute is acceptable, and then proceed—this will enhance practical reliability.

Countermeasure 3: Correcting Incompatibilities between the Inverter and String Conditions

If modules are displayed in the list and can be selected, but errors or warnings appear during the subsequent system configuration that prevent you from proceeding, the cause is often a mismatch between the inverter and string conditions. In this case, the problem is not the module data itself but the electrical design conditions: how the modules are connected in series and parallel and which inputs they are connected to.

In a photovoltaic power system, modules are connected in series to form a string, and that string is connected to the inverter input. In PVSyst, this configuration is checked to ensure it is valid in terms of voltage, current, and power. For example, if the number of modules in series is too small, the operating voltage may not reach the inverter's operating range. Conversely, if the number of modules in series is too large, the open-circuit voltage at low temperatures may exceed the input upper limit. In either case, simply selecting modules alone does not constitute a valid system.

A common pitfall for beginners is mistaking a warning that appears after selecting a module for a failure in module selection. In reality, even when the module was chosen correctly, errors can arise because the number of modules per string or the number of parallel strings is inappropriate. In such cases, before searching for a different module, you should review the number of modules in series, the number of strings in parallel, the number of inverter inputs, and the connection conditions for each MPPT.

First, what you should check is whether the number of modules in series falls within the voltage range. A module's operating voltage changes with temperature. In general, voltage increases at low temperatures and decreases at high temperatures. Therefore, judging only by room-temperature values can lead to problems such as exceeding the upper voltage limit during cold winter conditions or the operating voltage falling below the lower limit during hot summer conditions. PVSyst issues warnings that take these temperature conditions into account, so it is important not to ignore the warning messages and to verify that the design conditions are appropriate.

Next, check the number of parallel strings and the input current. When using high-output modules or high-current modules, too many parallel strings can cause the inverter's allowable input current to be exceeded. In particular, with recent high-output modules the current values tend to be larger, so setting the number of parallel strings based on traditional intuition can result in errors. It is not that you cannot select the modules; rather, the existing input configuration does not match the selected modules.

The balance between DC capacity and AC capacity is another point that should be checked. In PVSyst, warnings may be issued when module capacity is too large or too small relative to inverter capacity. Designing with DC oversizing in mind is common practice, but excessive DC capacity can lead to clipping losses and input-condition issues. Conversely, if DC capacity is too small, the inverter cannot be fully utilized and the design becomes inefficient. If a warning appears, verify whether the capacity ratio is reasonable with respect to the design intent, rather than merely clearing the error.

Also, attention must be paid to the connection conditions for each MPPT. If you combine arrays with multiple orientations and tilts, different string lengths, or layouts with partially different shading conditions into the same input, the simulation settings become more complex. In PVSyst, if the string conditions connected to the same inverter are inconsistent, warnings or configuration constraints may appear. Even if it looks like you cannot select modules, you may actually need to reorganize the array splitting and input assignments.

To address the issue, first check the target module's maximum power operating voltage, open-circuit voltage, maximum power operating current, and short-circuit current, and then check the inverter-side input voltage range, maximum input voltage, maximum input current, number of MPPTs, and number of input circuits. Based on that, adjust the number of modules in series and in parallel. While referring to PVSyst's automatic proposal feature and warning displays, it is important to manually adjust the configuration to fit the actual design constraints.

One thing to note is that just because errors disappear in PVSyst, that does not necessarily mean the design is immediately acceptable as a construction-ready design. There are items that must be checked outside of PVSyst, such as wiring routes for construction, junction boxes, cable ampacity, voltage drop, protective devices, laws and technical standards, and the detailed conditions of equipment specifications. PVSyst is very useful for energy production simulation and checking electrical compatibility, but separate technical verification is required for the final design decision.

When you get stuck selecting a module, before changing candidates it helps to organize “if you use this module, how many modules in series, how many in parallel, and which input they will be connected to,” as that makes the cause easier to see. Especially when copying an existing project and replacing it with a new module, the previous string configuration can remain. It is not uncommon for warnings to appear because the module output or current has changed but the numbers of modules in series or parallel were not adjusted.

In practice, it is important not to consider module selection and inverter selection separately, but to verify them together as a set. If you cannot select a module, cannot proceed with calculations, or warnings persist, many issues can be resolved by reviewing not only the module itself but also the string configuration and the inverter input conditions.

Countermeasure 4: Reexamine Project Conditions and Design Assumptions

If checking the module data and inverter conditions does not resolve the issue, review the overall project settings and design assumptions. In PVSyst, the project type, site information, meteorological data, installation conditions, and system type form the basis for the simulation. If these settings are incomplete or differ from the intended system type, you may not be able to proceed as expected on the module selection or system configuration screens.

The first thing I want to confirm is the type of project. Grid-tied, self-consumption, battery-coupled, standalone, etc.—the system’s purpose changes the settings screens and the required fields. For example, if a project that should be created as a grid-tied model is started under a different system type, the expected equipment configuration and input items may not match. As a result, settings may not align before and after module selection, making it difficult to proceed with the work.

Next, verify the site information and meteorological data. Module selection itself may appear to be an equipment-data issue, but in PVSyst the project location and weather conditions affect temperature conditions and simulation assumptions. In particular, for string voltage checks the low-temperature and high-temperature conditions are important. If the site settings remain provisional, meteorological data are unset, or conditions from a different region are being used, the way warnings appear and the design decisions can be affected.

Installation conditions are also important. Azimuth, tilt angle, mounting structure (racking type), row spacing, ground conditions, ventilation, installation height, and so on affect power output and temperature conditions. Even if they seem to be of little direct relevance at the module selection stage, inconsistencies in the overall system configuration can cause problems in subsequent calculations and loss settings. In particular, when dealing with arrays with multiple azimuths or multiple tilts, you need to confirm that how sub-arrays are divided is consistent with the module selection.

Sub-array settings are another easy-to-overlook point when modules cannot be selected. In PVSyst, you can configure multiple sub-arrays within the same project. If there are multiple roof surfaces, separate ground-mounted blocks, different orientations or tilts, or different shading conditions, you need to split into sub-arrays. However, if sub-array conditions are mixed together, it becomes difficult to tell which array each module is assigned to, causing selection mistakes and warnings.

When copying a project for reuse, check whether settings from previous projects have been left behind. This is a very common cause in practice. If you reuse a past project's modules, inverters, string counts, installation orientation, weather data, and loss conditions and only try to change the model designation for the new project, inconsistencies will occur. Even if it looks like a module cannot be selected, old settings and the new conditions may actually be mixed.

In such cases, it is easier to find the cause if you first organize the design conditions on paper or in a spreadsheet and then return to PVSyst. List the project name, site, system type, module model, module capacity, inverter capacity, number of modules in series, number of modules in parallel, number of installation surfaces, azimuth, tilt, presence or absence of shadow analysis, presence or absence of a storage battery, etc., and compare them with the settings in PVSyst. Rather than making ad-hoc corrections on the screen, organizing the assumptions externally makes it easier to find omitted settings or inconsistencies.

Also, even if you are stalled at module selection, the necessary preparatory steps may actually be incomplete. If you haven't selected the meteorological data, the definition of the mounting surface is ambiguous, the system type hasn't been finalized, the subarray configuration hasn't been decided, or the inverter sizing policy hasn't been determined, choosing the modules first alone will not allow the overall design to come together. PVSyst is software that requires inputs in order, but in practice, if the design assumptions aren't settled, it's easy to get lost partway through.

When reviewing project conditions, it is also important to clarify the purpose. Whether it is a preliminary estimate, a design comparison, an internal briefing, or something close to submission materials will affect the required level of accuracy and the strictness of inputs. In the preliminary stage you may proceed by clearly stating provisional assumptions, but at the stage when the results will be used for submission you need to carefully verify module data, inverter conditions, meteorological conditions, loss conditions, and shading conditions.

When you can’t select a module in PVSyst, it’s important not to focus on a single on-screen action but to return to the overall project assumptions. Module selection is not a choice of an individual component but part of the design conditions for the entire power plant. Because location, meteorological data, mounting conditions, electrical design, and loss settings are interconnected, if any assumption is off, issues can surface at the module selection stage.

Practical Checklist to Avoid Getting Stuck When Selecting Modules

To prevent problems with being unable to select modules, it is effective to organize the design information before operating PVSyst. PVSyst is a high-functionality simulation software, but if the information you enter remains ambiguous, you are likely to become uncertain in the middle of the process. In particular, module selection involves model/type information, electrical characteristics, installation conditions, and inverter conditions, so differences in prior preparation greatly affect work efficiency.

First, prepare the official model numbers and datasheets for the modules you plan to use. Abbreviations listed on quotes or proposals alone may not be found during database searches. Keeping documents that show the official model, series name, nominal output, cell configuration, whether the module is monofacial or bifacial, and the key electrical characteristics on hand will make it easier to find suitable candidates in PVSyst.

Next, plan in advance how you will combine the modules with the inverter. Decide on an approach such as how many modules to connect in series, how many in parallel, which inverter input to use, and whether to separate subarrays if there are multiple orientations, as this will make it easier to respond to warnings in PVSyst. PVSyst’s interface can automatically search for configurations, but it is important to verify them with an understanding of the actual design constraints.

Standardizing input rules for each project is also effective. When multiple people in your company use PVSyst, deciding in advance how to create module data, how to handle provisional data, how to document the use of approximation models, how to name files, and how to manage versions will make it easier to verify results later. In particular, if submission files and working files are mixed together, it can become unclear under which conditions a result was calculated.

When registering new module data, it is important to keep a record of the supporting evidence. By briefly recording the specification version, the date of entry, the person who entered the data, the reviewer, and the change history, you can later verify the validity of the figures. Even if you only save the PVSyst results, if there are errors in the original module data it will be difficult to perform reproducible verification. In energy yield simulations, managing the input conditions is as important as the calculation results.

Furthermore, when selecting modules, you need to consider not only power generation but also constructability and site conditions. Even if a design is feasible in simulation, the actual arrangement can change due to the local topography, racking layout, shading, orientation, tilt, access ways, maintenance space, and wiring routes. Because module selection and layout are closely related, verification based on site conditions—not just desk-based settings—is essential.

Especially for ground-mounted installations, developed sites, sloping terrain, or locations with existing structures, accurate location and topographic information is important. Even slight changes in the number or arrangement of modules can alter string configuration, shading effects, cable lengths, and maintenance access routes. To bring a model in PVSyst closer to the actual site conditions, it is necessary to properly obtain on-site survey data and topographic information and reflect them in the design conditions.

The problem of being unable to select a module can sometimes be resolved just by using PVSyst, but fundamentally it often stems from insufficient organization of design information. When model numbers are ambiguous, specification sheets are not on hand, inverter conditions are undecided, layout plans keep changing, or site dimensions and slopes are unknown, it becomes difficult to make a determination even within PVSyst.

Therefore, in practical work using PVSyst, information sharing among the simulation team, the design team, and the field survey team is important. If coordinates and terrain data collected on site, allowable installation areas, locations of obstacles, heights of existing structures, delivery/access routes, maintenance spaces, and other information are well organized, setting up the conditions in PVSyst will go smoothly. Conversely, if simulations are advanced while site information remains ambiguous, changes to the conditions are likely to occur later, often requiring module selection and array configuration to be redone.

To avoid getting stuck with PVSyst, it's important not only to learn how to use the software but also to prepare the prerequisite input information. Many issues—modules not appearing as candidates, warnings after selection, strings failing to form, or results becoming unrealistic—can be resolved by checking the search criteria, specification values, electrical conditions, and site conditions in that order.

Summary

When you can't select a module in PVSyst, it's important to first distinguish whether it doesn't appear among the candidates, it appears among the candidates but can't be chosen, or it can be chosen but the system cannot be validated. If you continue changing settings without isolating the cause, the issue may seem resolved while the design conditions have in fact become misaligned.

The first thing to check is the database search criteria and filters. Differences in model notation, manufacturer names, narrowing by output range or technical classification, or leftover conditions from past projects can mean the module you’re looking for simply isn’t being shown. By broadening the search criteria and searching by part of the model number or specification values, you may find candidates.

Next, check whether the module data is registered, and if it is not, verify that the specification values can be entered correctly. New model types and project-specific specifications may not be in the database. In such cases, confirm the electrical characteristics based on the specification sheet and create accurate data as necessary. Simply substituting a similar model can cause differences in voltage, current, temperature characteristics, and power generation, so a decision appropriate to the intended use is required.

Furthermore, it is often the inverter or string conditions—not the module itself—that prevent progress. Check the number of modules in series, the number in parallel, the input voltage range, the maximum input current, the DC/AC ratio, and the connection requirements for each MPPT, and reassess whether the overall system is viable for the chosen module. If a warning appears, it is important to verify the electrical design conditions first before changing the module.

Finally, review the assumptions for the entire project. System type, site, meteorological data, installation azimuth, tilt angle, subarray configuration, shading conditions, and settings carried over from past projects can surface as issues during the module selection stage. Because PVSyst has many input fields, when you find yourself unsure on the screen it is especially effective to revisit and reorganize the project parameters.

When using PVSyst, module selection is not merely choosing a component; it is a critical step that determines the accuracy of the entire energy-yield simulation. Only when correct module data, an appropriate string configuration, and design assumptions matched to the site conditions are all in place will the calculation results be reliable.

Furthermore, to improve the accuracy of the installation, shading, and layout conditions entered into PVSyst, it is essential to accurately capture on-site location information. When planning a solar power plant, it is necessary to verify on site not only the desktop selection of modules but also the site shape, locations of obstacles, racking layout, inspection access routes, and the terrain after earthworks. If you want to obtain such on-site information efficiently, using the LRTK, a high-precision GNSS positioning device that can be attached to an iPhone, makes it easier to reflect on-site positional data in design and verification work. Bringing the simulation conditions in PVSyst closer to measured on-site data is effective not only for improving the accuracy of power generation forecasts but also for reducing design changes and rework during construction.