Import PAN and OND files
Upload manufacturer files into your team's catalogue.
Reviewed
What this is for
A manufacturer's own measured characterisation, as a PVsyst file. A .PAN is a module. A .OND is an inverter. Batteries and conductors have no equivalent format, so this page is not offered on those tabs.
Nothing is written until you have seen the preview and committed it. The file itself is not kept. Only the file name is recorded on the characterisation.
Steps
- From Modules or Inverters, Import a PAN or OND, or open
/app/components/import. - Choose a PAN or OND file. A real PAN is a few kilobytes; the ceiling is in megabytes. Anything else is refused and pointed at the manual form.
- The file is read and matched against the catalogue. The preview exists only in this session: a refresh has nothing to come back to, because nothing has been written yet.
- Notices on the preview are the reason it exists. A file missing a temperature coefficient still imports - a documented default is supplied - but you are told which numbers were read and which were assumed. Quote from a file full of assumptions only if you mean to.
- The article is make, model, nameplate, dimensions. Spellings collapse onto one manufacturer row. Length is the long edge (PVsyst writes it as Height). Getting length and width the wrong way round transposes every module in a layout.
- If the match is an installation-owned row, the specification cannot be edited here. Your characterisation still attaches to it.
- What the model reads is not editable. Hand-changing one member of a fitted single-diode set produces a curve that satisfies no equation it came from. Correct the file, or type the module by hand so the fit is performed from the corrected points.
- Name the characterisation, say whether it is the default, choose Who can see it, and Commit the import. Uploads start at Only me, so a file you are still testing stays out of a colleague's picker; choose My team once you trust it. Reaching every other team is a staff decision, not something this form does. A new SKU or an extra characterisation on an existing one: the result page says which. If the commit did less than the form offered, the reason is on screen, not swallowed.
An OND file carries no topology field. Topology is inferred from the nameplate, and the preview says so.
Tips and common mistakes
- Prefer this over typing when you have the file. The characterisation is marked PAN or OND, not Datasheet.
- The bytes are not stored. You cannot download the file back out. Keep your own copy.
- A PAN is not a datasheet PDF. The datasheet reader is a different button, metered, and still needs you to check every number.