RunMat
  • Pricing
RunMat
GitHub
GitHub
Sign inTry in browser
DesktopRuntimePhysicsCADAdministrationAgent

Get RunMat updates

New releases, guides and examples.

Product+
  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download
Math+
  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting
Physics+
  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA
Industries+
  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance
Learn+
  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students
Compare+
  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons
Company+
  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms

Product

  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download

Math

  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting

Physics

  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA

Industries

  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance

Learn

  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students

Compare

  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons

Company

  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms
GitHubXLinkedIn

© Dystr, Inc. · RunMat v0.7.1, Nov 17, 2026

RunMat® is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
    • Get started with ECAD
    • ECAD file reference
Docs>CAD>ECAD

ECAD file reference

RunMat ECAD keeps a schematic in a .circuit file and its board in a .circuit.layout file beside it. A .circuit file with no circuit block is a library of footprints, symbols and parts that other files use. The schematic holds the design intent: components, connections, net classes, variants and simulations. The board holds where everything goes: outline, stackup, footprints, copper and rules. This page covers every .circuit statement and the board's top level; Board layout covers the board in full.

A complete circuit

A 3.3 V regulator with its capacitors, a power LED, and an RC filter ahead of an ADC input, with a variant that leaves the LED off and a simulation of the filter:

runmat 0.7
std 1

// A 3.3 V rail from a 5 V input, a power LED, and an RC filter ahead of an ADC input.
circuit sensor {
    root = main
    net_class power = { track_width = "0.40 mm", clearance = "0.20 mm" }
    variant lite = { overrides = { D1 = not_fitted } }

    sheet main {
        component U1 = { part = "LDO-3V3-SOT23" }
        component C1 = { part = "C0805-10U" }
        component C2 = { part = "C0402-1U" }
        component D1 = { part = "LED0603-G" }
        component R1 = { part = "R0402-1K" }
        component R2 = { part = "R0402-10K" }
        component C3 = { part = "C0402-100N" }
        component P1 = { part = "PAD-WIRE-20AWG" }
        component P2 = { part = "PAD-WIRE-20AWG" }
        component P3 = { part = "PAD-WIRE-20AWG" }
        net GND = { class = power, global = true, power_flag = true }
        net VIN = { class = power, power_flag = true }
        net "+3V3" = { class = power, global = true }
        connect = [net.VIN, "P1.1", U1.VIN, U1.EN, "C1.1"]
        connect = [net.GND, "P2.1", U1.GND, "C1.2", "C2.2", D1.K, "C3.2"]
        connect = ["net.+3V3", U1.VOUT, "C2.1", "R1.1"]
        connect = [net.LED, "R1.2", D1.A]
        connect = [net.SENSE, "P3.1", "R2.1"]
        connect = [net.ADC, "R2.2", "C3.1"]
        no_erc = [U1.NC]
    }

    // The 10 k / 100 nF filter ahead of the ADC: a 159 Hz corner.
    simulation filter {
        sheet = main
        source VS = { p = net.SENSE, ac = 1 V, pulse = { from = 0 V, to = 1 V, delay = 1 ms, rise = 1 us, fall = 1 us, width = 20 ms, period = 40 ms } }
        tolerance resistors = { match = "R*", value = 1 % }
        tolerance capacitors = { match = "C*", value = 10 % }
        analysis step = tran { stop = 10 ms, step = 10 us }
        analysis response = ac { from = 1 Hz, to = 100 kHz, points = 50 }
        probe = [net.SENSE, net.ADC]
        measure corner = { of = response, bandwidth = net.ADC, spec = { min = 140 Hz, max = 180 Hz } }
        measure rise = { of = step, rise_time = net.ADC, from = 1 ms, to = 10 ms, spec = { max = 3 ms } }
        measure settled = { of = step, final = net.ADC, spec = { min = 0.99 V, max = 1.01 V } }
    }
}

Its board, before placement:

runmat 0.7
std 1

use circuit sensor

layout sensor {
    outline = [[0, 0], [40, 0], [40, 25], [0, 25]]
    limits = { clearance = 0.15, track = 0.15, via_diameter = 0.45, drill = 0.2, annular = 0.1, hole_to_hole = 0.25, copper_to_edge = 0.3, silk_to_pad = 0.1, microvia_drill = 0.1 }
    net_class power = { track_width = 0.4 mm, clearance = 0.2 mm }
}

Statements

StatementDeclaresSection
root = <sheet>the top sheetSheets
param <name> = <value>a design parameter, such as param supply = 3.3 V ± 5 %Components
net_class <name> = { … }rules shared by a class of netsNets
interface <name> = { members, diff_pairs }a bundle type for harnessesNets
variant <name> = { base, overrides }a build variantVariants
part "<mpn>" = { … }a part declared in the fileParts library
footprint <name> = { … }a footprint declared in the fileFootprints
symbol <name> = { … }a schematic symbol declared in the fileFootprints
sheet <name> { … }a schematic sheetSheets
simulation <name> { … }a simulation sectionSimulation sections and measures

Inside a sheet:

StatementDeclares
port <name> : <direction>a sheet port: in, out, inout, passive or power; port D : in = bus [D0, D1] for a bus port
component <designator> = { part, value, classes, properties, variants, power, renamed_from }a component
net <name> = { class, global, power_flag, renamed_from }a net and its settings; a net first named in a connect needs no declaration
bus <name> = [<members>]a bus
harness <name> = <interface>a harness of an interface type
instance <name> = { sheet, repeat, designators, bind }a sheet placed as a block, or repeated as channels; designators = "{prefix}{n}0{i}" names each channel's parts
connect = [<endpoints>]joins every endpoint listed into one net
no_erc = [<pins>]pins the electrical rules leave alone
diff_pair <name> = { p, n }a differential pair
blanket <name> = { nets, class, <params> }one class and set of parameters over several nets, such as blanket rails = { nets = [VIN, GND], class = power }; a net's own class wins
text <name> = "<words>"a note drawn on the sheet, such as text note1 = "5 V in from J1"; it has no electrical meaning

Library files and use

A library .circuit holds footprint, symbol and part declarations at file level and no circuit block. A circuit or another library brings them into scope with use "<path>.circuit", with the path relative to the file:

runmat 0.7
std 1

use "../library/parts.circuit"

use lines go at the top of the file. Other use forms name designs in other folders: use circuit power from "./power" and use sheet buck from "./power" as reg. See Footprints for how library names resolve.

Project layout

A new project uses the standard layout, and a project that already has its own folders keeps them:

FolderHolds
mechanical/<subsystem>/parts, assemblies and their .m functions
electrical/<board>/a board's .circuit beside its .circuit.layout and lock
electrical/library/library .circuit files: footprints/<name>.circuit, and parts in parts/ or parts.circuit
simulation/.fea studies
drawings/.drawing files

Endpoints are U1.VIN, "C1.1", net.GND, "net.+3V3", port.IN, bus.D.D0, harness.USB.DP and instance.pwr.VIN; see Names and selectors.

Reference pages

PageCovers
Sheets, hierarchy and channelsthe root sheet, ports, blocks, channels repeated with repeat
Components and library partscomponents, values and tolerances, values from .m functions, designators, parts declared in the file
Nets and net classesconnect and endpoints, net settings, buses, harnesses, differential pairs, net classes
Variantsfitted and not-fitted parts, alternates, variants on variants
Rules and checksthe electrical rules, the design-review suites, the board checks, the command line
Simulation sections and measuressources, models, analyses, measures and limits
Board layoutevery .circuit.layout statement and the design rules
Footprintsgenerator strings, footprint and symbol declarations, library files
Fabrication outputs and netliststhe fabrication set and netlists
On this page
  • A complete circuit
  • Statements
  • Library files and use
  • Project layout
  • Reference pages