@nexgen-os/panond — PAN and OND product files → plain products

Reads the files PVsyst writes and manufacturers publish next to their datasheets — PAN for a PV module, OND for an inverter, in PVsyst's text format (version 6 and later) — into a product and its physics. Read only: a PAN or OND file is never written (decision 0012). MIT; no dependency, no database, no network. The table names the product's fields, and where the importer of the solar module writes them.

| File | Product, and its row in Nexgen OS | Notes | |---|---|---| | Manufacturer, Model | products.manufacturer, model | a product the catalogue already knows gains its physics | | PAN PNom, Width × Height | unit_power_kw, unit_surface_m2 | | | OND PNomConv | unit_power_kw (AC) | | | PAN Gamma, muGamma, RShunt, Rp_0, Rp_Exp, RSerie, muISC, NCelS | solar.module_products, model pvsyst: gamma_ref, mu_gamma, R_sh_ref, R_sh_0, R_sh_exp, R_s, alpha_sc (A/°C), cells_in_series | pvlib's keys for calcparams_pvsyst; EgRef 1.121 eV for silicon | | PAN Isc, Voc at TRef | I_L_ref, I_o_ref | solved: see below | | the whole PAN file | module_products.metadata.pan | incidence profile, bifaciality, STC point, dimensions | | the OND file but its commercial block | solar.inverter_products, model ond, parameters | the file's keys, efficiency curves (ProfilPIO…) as [x, y] pairs, as pvlib's read_panond gives them | | the OND commercial block | inverter_products.metadata.ond | data source, dimensions, remarks | | Price, Currency, PriceDate | left out | the line between open and paid data runs on prices |

import { readPan, readOnd } from '@nexgen-os/panond';
import { importProduct } from '../modules/solar/src/products.js'; // the solar module, inside this repository

const module = readPan(panText);
await importProduct(db, module, { organisationId, sourceCode: null, fileName: 'module.PAN' });
await importProduct(db, readOnd(ondText), { organisationId });

What it never does: look a product up, write a catalogue, open a connection. importProduct() of the solar module (modules/solar/src/products.ts) adds the product to products, or gives its physics to the one the catalogue already knows by manufacturer and model, and refuses physics given twice (already_imported). A module imported this way runs as it is through the pvlib engine (packages/connectors/pvlib, DC model pvsyst) once an array names it.

The diode currents

PVsyst stores the series and shunt resistances and the diode factor, not the light current and the diode's saturation current. At short circuit (V = 0, I = Isc) and open circuit (V = Voc, I = 0) the one-diode equation is linear in both, so diodeCurrents() solves them exactly: the model then gives back the file's Isc and Voc, and its maximum power lands within half a percent of PNom on the files tested.

Refusals

panond_unreadable (not a PVsyst text file), panond_binary_unsupported (a binary file of PVsyst before version 6: export it again as text), pan_unreadable / ond_unreadable (another kind of object, or a value the model needs is missing), pan_inconsistent (the file's numbers give no diode), already_imported (the product already has its physics).