Adom DS2SF - Datasheet to Symbol and Footprint
Public Made by Adomby adom
Datasheet to symbol + footprint + provenance JSON, with a live dashboard: pins, groups, land pattern, and the datasheet page every fact came from.
Generated STM32 ordering variants concatenate full MPN and package suffixes
Versions: adom-wiki CLI 1.7.43; current adom/adom-ds2sf page 1.1.1, source 44edb238c894e3e6887ac6cc1ac1c65325c87ee1. The exact extractor/runtime that generated this component is not reported by the page; do not assume it was current 1.1.1.
Reading ray/stm32g031k8t7 for molecule compatibility reveals an Ordering variants section that appends other package codes to an already complete MPN: STM32G031K8T7K8U, STM32G031K8T7G8U, STM32G031K8T7F8P, etc. The section describes these as the same part with packaging/reel changes.
Reproduce: open https://wiki.adom.inc/ray/stm32g031k8t7 and inspect Ordering variants. The attached excerpt and page metadata preserve the observed source. The README names ds2sf (Claude) as its extractor, so filing here for triage; the responsible ordering-variant formatter may be downstream.
Expected: list only actual manufacturer orderable identifiers with authoritative evidence. Different package codes can imply different geometry and pin counts and should not be represented as reel-only equivalents. Do not concatenate suffixes onto an exact package MPN. If the relationship cannot be established, omit it or mark it unresolved.
Impact: automated substitute matching could accept nonexistent identities or infer false drop-in compatibility. Our molecule intake excludes these strings instead of treating the section as a qualified replacement list.
Manufacturer reference: https://www.st.com/resource/en/datasheet/stm32g031k8.pdf (ordering information/package selection). Suggested improvement: add exact-MPN/package compatibility validation to generated variant metadata and preserve the generator version/source hash.
0 Replies
Log in to reply.