Skip to main content

Example project collection

Routed-board examples

Use these examples to judge board scale, rendering, routing structure, and migration behavior without treating them as Resin-authored designs.

Projects
3
Files
Downloadable where available
Use
Structure and scale

Projects

Inspect three complex open-hardware boards, their measured structure, and the limits of the available checks.

Front copper, mask, and silkscreen render of the six-layer ScopeFun v2 mixed-signal instrument board
Mixed signalComplex board package

ScopeFun v2 mixed-signal instrument

A production-run open-hardware oscilloscope and waveform generator with dual high-speed ADCs, analog front ends, FPGA control, DDR3, and USB 3.0.

840 footprints11,090 segments6 copper layers27/27 migration checks

Useful for: Byte-exact source preservation, editable-project packaging, structural measurement, front/back rendering, and a 27-check Resin legacy-KiCad PCB conversion record.

All files, source, and known limits
  • This is upstream open hardware, not a Resin-authored design or customer project.
  • The source is a KiCad 4-era project and must be migrated before saving in a current editor.
  • No Resin import-fidelity, DRC-clearance, fabrication, calibration, or current component-availability claim is made.
  • CERN OHL v1.2 attribution and source-sharing obligations remain attached to redistributed source material.
  • All 27 conversion checks met their stated condition, including footprint reference/value preservation and KiCad 9.0.7 acceptance; bounded checks do not establish full semantic or manufacturing fidelity.
  • The bounded Resin DRC record retains per-family completion, timeout, timing, and raw pre-dedup finding data; it is not a complete or deduplicated DRC result.
Front copper, mask, and silkscreen render of the four-layer CIAA-NXP industrial controller
ConnectivityComplex board package

CIAA-NXP industrial controller

A production-scale open industrial controller with protected field interfaces, isolated digital inputs, analog I/O, memory, power, and a dense routed PCB.

443 footprints8,086 segments4 copper layers25/27 migration checks

Useful for: Byte-exact source preservation, editable-project packaging, structural measurement, front/back rendering, and a 27-check Resin legacy-KiCad PCB conversion record.

All files, source, and known limits
  • This is upstream open hardware, not a Resin-authored design or customer project.
  • The source is a KiCad 5-era project and saving it in a current editor may produce a broad format migration.
  • No certification, EMC, safety, environmental, manufacturing-yield, or current component-availability claim is made.
  • The communications interfaces are protected, but galvanic isolation is demonstrated primarily by the digital inputs.
  • Twenty-five of 27 conversion checks met their stated condition; footprint values are not surfaced and KiCad 9.0.7 rejects the converter's target format version.
  • Nine of fourteen bounded Resin DRC families completed with 447 raw pre-dedup findings; five timed out and the full KiCad CLI DRC path errored.
Front copper and silkscreen render of the official KiCad video demo board
PCB routingRouted-board package

Four-layer video-processing reference board

Inspect a dense routed board from KiCad's official GPL-3.0-or-later demo set through Resin's native parser and renderer.

189 footprints7,932 routed segments808 vias

Useful for: Byte-exact KiCad source ingestion, structural counting, native front/back SVG rendering, a completed KiCad CLI DRC report, and a time-bounded Resin-native family run on a dense routed board.

All files, source, and known limits
  • This is an official KiCad demo distributed by the KiCad project; it is not a Resin-authored design or customer project.
  • KiCad CLI completed in 17.38 seconds with 243 reported violations: 25 errors and 218 warnings. This is not a clean-board result.
  • The bounded Resin-native run completed 5 of 14 families and timed out 9 families at 30 seconds each. Its 458 raw pre-dedup findings cannot support a complete native DRC conclusion.
  • No .kicad_pro or .kicad_dru accompanies the board, so project-aware rules and net classes were unavailable.
  • No fabrication, assembly, electrical performance, compliance, or built-hardware acceptance is claimed.

How to use these files

Inspect the source, result, and report as separate things.

A render can show structure, a conversion report can show measured differences, and an output file can be opened by a receiver. None of those alone proves the entire workflow.
Check identity

Use the published revision, hashes, license, and provenance before comparing files.

Open the actual files

Use an appropriate independent tool rather than judging compatibility from a screenshot.

Keep the stated boundary

Do not describe third-party boards as designed in Resin or uninspected outputs as manufacturing-approved.