Component library
Browse and search modules, inverters, and other catalogue rows.
Reviewed
What this is for
The hardware this team can design with: modules, inverters, batteries and conductors. Provenance sits on the list, not two screens later. A row from a certification register, a PVsyst file, a typed datasheet and a standards table can carry the same six numbers and make different claims. The column is which.
This is not a shop. It is the catalogue a design picks from.
Steps
- Open Component library. Four tabs for the hardware: Modules, Inverters, Batteries, Conductors. A fifth, Requests, lists what this team has asked to have added.
- Search manufacturer or model. Sort by name, power, or recently added. Favourites float to the top; the star is a team favourite, not a personal one. Filters (manufacturer, technology or topology, a power range, team's own, bifacial or hybrid) draw chips under the row so a narrowed list never has an invisible cause.
- Read Provenance before you pick. A CEC badge is a certification register, not a test report. Unvalidated is the normal state: nobody here has independently checked the figures. Treat them as indicative. A PAN or OND file is the manufacturer's own measured characterisation. Datasheet is typed from a published sheet. Datasheet, read is a language model plus a person. Conductor rows marked Standard are sourced from a published table anybody can check; a size your team added is not.
- Open a row for the full characterisation. That is a different article.
- Add hardware this team actually stocks.
- Import a PAN or OND on Modules or Inverters. Those formats do not apply to batteries or conductors, so the button is not there.
- Type one in on every tab, including a conductor size the standard table does not carry.
- Read a datasheet when this deployment has the integration on. A language model fills the form. Nothing is added to the catalogue until you have looked at every number and saved it. Every read is metered and counts against the team's daily cap. Prefer a PDF you already have over a page that may not load. A read takes about a minute, longer from a page; Stop reading cancels one you can see is the wrong document, and nothing is saved.
- A published datasheet usually covers a family, not one product. Where it describes more than one, the reading lands on What the datasheet describes (
/app/components/reading/…): check the figures that differ against the document, then add the ones you stock. The reading outlives the upload: you can add four of eight, close the tab, and come back from history. A datasheet for a single product opens straight on the form. - Missing something you install? Request a component, from the Requests tab or under a search that found nothing. Say what kind it is, the make and the model, and send the datasheet or the page it is published on. A curator reads it into the catalogue, and it appears for every team, including yours. Asking works on every plan; adding a component yourself depends on yours.
- Requests says what came of each one: Waiting, Added with the tab it went under, or Not added with the curator's reason.
Tips and common mistakes
- Search on Modules and Inverters is a query, not a filter-as-you-type: the catalogue is thousands of rows and the list pages. Batteries and Conductors are short tables and filter as you type; batteries sort by usable energy rather than power.
- A module marked Needs dimensions is a register row with a complete electrical model and no published size, so it has no page and cannot be laid out yet. Its row menu offers Type the figures in, which takes the dimensions and keeps the register's electrical figures unchanged, and, where datasheet reading is switched on for this deployment, Read the datasheet, which can search for the manufacturer's page for you to choose.
- Nothing on these screens edits a catalogue row in place. Your own figures for a module or inverter attach as another characterisation beside the row's, from a PAN or OND import, a datasheet reading, or typing it in. A row this team added can be deleted from its page while it is unpublished and unused; correcting a row's figures in place is a curator's job, and it reaches every design already on the row.
- Unvalidated is a claim, not a broken row. A zero in a column that was never measured is a dash on the detail, not
0.00. - Do not pick a module because the name matches. Two 270 W panels of different area are different products.
- Request the component rather than typing a near match into a design. Send the datasheet itself where you have it: a curator reads the product off the page, and a link to a page that has moved gives them nothing to read.