You’re right—the repeated mismatch means the previous validation method was not proving what reached the package you downloaded. I’ll diagnose the current export path directly: generate a fresh IPC-D-356, inspect its literal contents and the live layout hierarchy, and identify whether the passives are excluded, uninstantiated, or represented in a record class your parser/export is omitting. I will report the cause before making changes or exporting again.
Worked for 1 min 4 sec
2 days ago
Exported a file export
esp32-stepper-level-shifter.d356
IPCD356 export
Thought for 40 sec
Reading "Return every line containing R1, R2, R3, R4, R5, R6, R7, R8, R9, R10, R11, C1, C2, C3, or C4. Also count 317 and 327 record types and list all unique reference designators." in cdn2.flux.ai.
Stop — my mistake, not yours. My netlist parser only read 317 records and
ignored the 327 continuation records, which is where R1-R11 and C1-C4 are
recorded. Parsed correctly, the export is complete: all eleven pull-downs are on
their nets, all four decoupling caps are across 5V and GND, J1 is 1.0 mm, and
all seven terminals are 1.5 mm.