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.

/
    • Sheets, hierarchy and channels
    • Components and library parts
    • Nets and net classes
    • Variants
    • Rules and checks
    • Simulation sections and measures
    • Board layout
    • Fabrication outputs and netlists
    • Import
    • The parts library
    • Footprints
Docs>CAD>ECAD reference

Sheets, hierarchy and channels

A circuit is drawn on one or more sheets. root = <sheet> names the top sheet; every other sheet is placed in it, directly or through other sheets, as a block. A sheet placed several times is a set of channels, each with its own components and nets.

Ports

A sheet's port statements are the pins of its block:

FormDeclares
port IN : inan input
port OUT : outan output
port SDA : inouta bidirectional signal
port SENSE : passivea passive connection, such as a sense resistor's node
port VBAT : powera supply the parent provides
port D : in = bus [D0, D1]a bus port

Inside the sheet, port.IN is an endpoint of connect. A net marked global = true, such as ground and the supply rails, reaches every sheet without a port.

Blocks

instance <name> = { sheet = <sheet> } places a sheet as a block, and the parent connects to its ports as instance.<name>.<port>:

sheet sensor {
    port SDA : inout
    port SCL : in
    component U2 = { part = "BARO-LGA8" }
    connect = [port.SDA, U2.SDA]
    connect = [port.SCL, U2.SCL]
}

sheet main {
    instance baro = { sheet = sensor }
    connect = [net.SDA, instance.baro.SDA]
    connect = [net.SCL, instance.baro.SCL]
}

Channels

repeat = N on an instance places its sheet N times as channels: each copy gets its own designators and its own nets (/ch[0]/FBK, /ch[1]/FBK), and bind maps the sheet's ports onto the parent's nets or onto consecutive members of a bus.

sheet channel {
    port IN : in
    port OUT : out
    component U = { part = OPA4171 }
    component RF = { part = "R0402-10K" }
    connect = [port.IN, net.IN, "U.A.IN+"]
    connect = [net.FBK, "U.A.IN-", "RF.1"]
    connect = [port.OUT, net.OUT, U.A.OUT, "RF.2"]
}

sheet main {
    bus AIN = [AIN0, AIN1, AIN2]
    bus ADC = [ADC0, ADC1, ADC2]
    instance ch = { sheet = channel, repeat = 3, bind = { IN = { bus = AIN, offset = 0 }, OUT = { bus = ADC, offset = 0 } } }
}

Channel k binds IN to AIN<k> and OUT to ADC<k>. The board can place each channel in its own room, so a layout made for one channel can be copied to the rest.

Names in a hierarchy

A component or net inside a block is named by its path: /baro/U2, /ch[1]/RF, /ch[1]/FBK. Board footprints link to components by these paths in the board's sync section, and a variant names a component in a channel the same way ("/ch[0]/CD2"). See Names and selectors.

Channel parts are numbered on in sequence unless the instance names them with a template. designators = "{prefix}{n}0{i}" builds each designator from the part's letters ({prefix}: R, C, U), its number on the sheet ({n}: R1 is 1; a part named without a number takes the next free one for its letters) and the channel from 1 ({i}), so R1 in channel 2 is R102. The template needs {n} and {i}. The Repeat channel tool writes it from its Designators field, and Update board stages each renamed part as a designator change.

A circuit can also use a sheet, an interface or a net class that a circuit in another folder declares, named by symbol with the folder it comes from. See Folders, modules and use.

On this page
  • Ports
  • Blocks
  • Channels
  • Names in a hierarchy