{{include "header.html"}} {{include "nav.html"}}

B08 / ENGINEERING COMPONENTS

Know the reference.
Ask for the evidence.

A structured starting point for component identity, package and pinout references, compatibility questions, documents, and procurement conversations.

DEMO / NOT VERIFIED — every part and technical field on this site is fictional.

{{with Column "components"}}Explore component records {{end}} {{with Column "inquiry"}}Start an engineering inquiry {{end}}
REFERENCE / 00—08DOCUMENT STATUS / UNVERIFIEDMODE / DEMONSTRATION
{{$hero := index .ThemesExt "hero_photo"}}{{if $hero}}Illustrative macro photograph of an electronic circuit board; not a WEIWEI product{{end}} STOCK PHOTO / NOT PRODUCT EVIDENCE
NODE FIELD / AReference before selectionSCHEMATIC OVERLAY
Original abstract circuit-node schematic; not a real PCB layout
01 IDENTITY02 PACKAGE / PINOUT03 COMPATIBILITY04 DOCUMENT SOURCE

01 / REFERENCE CATALOG

Component records,
built around the questions.

Model identity is only the start. A real review needs the source revision, package drawing, pin assignment, electrical conditions, and a traceable compatibility reference.

{{with Column "components"}}Open the full reference catalog {{end}}
{{$items := ColumnContents "components" 4}}{{if $items}}{{range $items}} {{$model := ""}}{{$family := ""}}{{if .Ext}}{{$model = index .Ext "model_id"}}{{$family = index .Ext "component_family"}}{{end}}
REF / {{.Id}}DEMO / NOT VERIFIED
Abstract package and circuit-node schematic; not a real pinout {{$model}}

{{.Title}}

{{.Description}}

{{$family}} {{end}}{{else}}

No component records are published yet.

{{end}}
{{$bench := index .ThemesExt "bench_photo"}}{{if $bench}}Illustrative engineering workbench context; no relationship to a real supplier or test result{{end}} ILLUSTRATIVE WORK CONTEXT / NO TEST PERFORMED Original schematic showing a component reference review sequence, not a measured test result

02 / ENGINEERING CONTEXT

From a part string
to a reviewable brief.

Applications describe where a component might sit in a fictional design. They do not claim a customer, design-in, or verified system fit.

{{$apps := ColumnContents "applications" 4}}{{if $apps}}{{range $apps}}APPLICATION / DEMO{{.Title}}{{end}}{{else}}

Application notes are not published.

{{end}}
{{with Column "applications"}}Browse application contexts {{end}}

03 / EVALUATION PLANNING

Scenarios to structure
the evidence request.

These are fictional review briefs. No hardware was built; no test, measurement, or result exists.

{{with Column "evaluations"}}See all evaluation briefs {{end}}
{{$scenarios := ColumnContents "evaluations" 3}}{{if $scenarios}}{{range $scenarios}}DEMO / NOT VERIFIED

{{.Title}}

{{.Description}}

{{end}}{{else}}

No evaluation briefs are published yet.

{{end}}

04 / BUYER GUIDES

Ask for the source.
Keep the revision.

Practical prompts for identity, pinout, operating conditions, alternatives, and procurement evidence. Specific engineering decisions still require the actual manufacturer documents.

{{with Column "guides"}}Open buyer guides {{end}}
{{$guides := ColumnContents "guides" 3}}{{if $guides}}{{range $guides}}GUIDE / DEMO{{.Title}}{{end}}{{else}}

Buyer guides are not published yet.

{{end}} {{with Column "documentation"}}DOCUMENT DIRECTORYSee source and revision fields{{end}}
RFQ / INQUIRY
VVCMS MESSAGE API

05 / NEXT STEP

Share the context.
Keep the claims verifiable.

Describe the application, reference, document questions, and procurement context you want reviewed. A message is not a quotation or supply confirmation.

{{with Column "inquiry"}}Send a technical inquiry {{end}}
{{include "footer.html"}}