soldermaskdocs

Workbench

The workbench shows one version of one board. Here you move parts, draw tracks, change how the board is built, and rebuild it.

The address is where you are: the board, the version, the view, the pick, the drawer tab and the findings you are reading. A reload, a shared link and Back land in the same place. See The address.

The workbench with a part selected

The screen

The board sits in the middle, and nothing covers it. Five regions surround it.

RegionWhat it holds
HeaderThree zones. Left: the project name (click to rename it) and the version menu. Middle: the views Copper, 3D and Schematic. Right: the poll and Export, with Rebuild, Accept and Discard when there is something to decide.
LeftThread: your messages, the replies and the build log. Library: blocks and parts you can add.
StageThe board, its rulers, the findings and the layers control in its corner.
RightThe inspector. With nothing picked it shows the board: its checks, Why, then its facts. It also holds the board's findings. Pick a part, a net or a track and it shows that.
SeamThe bar under the stage. It starts with the drawer's tabs: Chain, Scope and Cost. Then comes the readout.
BottomThe drawer, under the seam. It is shut until you open one of its tabs.
  • The thread and the inspector run the full height of the window. The stage, the seam and the drawer stack between them.
  • Fold any region with the chevron in its title bar, or with Bracket-left, Bracket-right and Backslash. Each browser remembers what you folded.
  • Cmd+Backslash gives the board the whole window. Both columns and the drawer fold, and the header and the foot stay. Press it again to bring back what was open.
  • The inspector's title is a breadcrumb, such as Board › Findings › J1. Click a step to go back to it, or press Esc to go back one.
  • The inspector opens on the board's checks, then its Why cards.
  • The inspector opens by itself when you pick something.
  • The version chip opens the version menu. Picking a version shows it, and your next message edits it.
  • On an older version, the chip says which version is newest, such as v004 of v006. Latest takes you there.
  • On a phone, the inspector is the Board tab of the details sheet, and the findings are its Findings tab. Layers sits beside the poll's pill.

The poll

The poll says whether the board works. It is one pill in the header, beside Export, such as NO-GO Copper 4 err.

It shows the board's word and what holds it:

WordMeans
GOEvery station passed.
NO-GOAt least one station holds. The board does not work as built.
UNJUDGEDNothing failed, but a check the verdict needs did not run.

A board built before verdicts existed also reads UNJUDGED, with no verdict under the word. Rebuild it to judge it.

The inspector opens with the checks: one chip for each part of the pass rule.

StationPasses when
PartsEvery part resolved
NetsNo net or pin the design asked for was dropped
ERCThe electrical rule check ran and found no errors. Warnings show here but do not hold it.
RouteEvery pin is reached. It reads off when routing was not asked for.
CopperKiCad's DRC judged the finished copper and found no errors, and no net's copper is too narrow for its current

A check that holds is red and says what it found, such as Copper 4 err. A check that passed is a green dot and its name.

Copper too narrow for its net's declared current reads Copper 2 hot. It holds when the copper would rise 100 °C or more. A rise past 20 °C is an advisory.

After the stations, a chip counts the advisories when there are any. These are what the build reported and the verdict does not read, such as unverified footprints.

  • Click the pill, or a check that holds, to open Why. A check that passed opens what it checked in the findings.
  • Click Advisories to open their list in the findings. All findings, the last chip, opens every group.
  • The poll uses the rule the evaluator scores with. The word here and the pass rate on the benchmarks page cannot disagree.
  • On a phone, the pill sits under the header. The checks are in the details sheet.

Why

With nothing picked, the inspector starts with one card for each thing that keeps the board from GO. There are no cards when the board is GO.

Each card says:

  • which station holds, and which card of how many it is when there is more than one
  • what was found and where, in one sentence
  • the facts: how many errors, the cause, the version it started in, and what found it
  • the actions that can clear it, with the likeliest one filled
  • which actions cannot help, and why

The actions depend on the cause:

CauseActions
A part's own footprint, such as pads too close to the part's own holesAsk for another part, browse the catalogue, show it on the board
Two parts too close togetherShow it on the board, place again, ask to move them apart
Copper where it meets a partRoute again, show it on the board, ask about it
Pins the router did not reachRoute again, show the net, place again, ask about the layout
Copper too narrow for its net's currentRoute again, show the findings
An electrical rule errorAsk to fix the circuit, show the findings
Parts that did not resolveAsk for parts that resolve, browse the catalogue
Connections that were droppedAsk to fix the connections
A check that did not runRebuild to judge it

An Ask action writes a question in the thread's message box, scoped to the parts it names. Nothing is sent until you send it.

Keys

KeyDoesView
1 2 3Switch to Copper, 3D or SchematicAny
TabNext view (Shift+Tab for the previous one)Any
EscLet go of the selection and the finding you are looking at. With nothing picked, close the findings.Any
Cmd+KOpen the command barAny
QuestionShow the keysAny
LOpen or shut the layers controlAny
Bracket-left / Bracket-rightFold the thread, fold the inspectorAny
BackslashOpen or shut the drawerAny
Cmd+BackslashGive the board the whole window, or bring the panels backAny
N / Shift+NLook at the next or the previous finding on the copperAny
Cmd+Z / Shift+Cmd+ZUndo / redo a move, a turn, a flip or a track you drewAny
Del or BackspaceDelete the picked track you drew, or remove the picked partAny
Arrow keysMove the picked part one grid step (with Shift, ten)CU
R / Shift+RTurn the picked part a quarter turn, one way or the otherCU
FFlip the picked part to the other side of the boardCU
Page Up / Page DownMake top or bottom copper the active layerCU
X (or W)Start or stop drawing tracksCU

While you draw a track:

KeyDoes
VDrop a via and carry on on the other layer
/ or SpaceFlip the corner: straight first, or diagonal first
BackspaceTake back the last corner
Enter, double-click or right-clickFinish the track here
EscDrop the track. Press it again to stop drawing.
Alt + clickLift a track you drew earlier

Pointer and touch:

GestureDoes
Drag bare boardPan
Shift + dragPan from anywhere, even while drawing
ScrollZoom about the pointer
Double-click bare boardFit the board to the window
Two-finger pinchZoom, on a touch screen
Alt while dragging a partStop the part snapping

The command bar

Press Cmd+K (Ctrl+K on Windows and Linux) and type what you want.

It reaches the board's parts, nets and findings, the views, the layers and the versions. It also runs Route again, Place again, Rebuild, Simulate and the file downloads, and searches the catalogue for what you typed.

  • Words match in order, each as the start of a word or a run of letters.
  • Use the arrow keys to move, Enter to run, and Esc to close.

Copper

The copper view draws the board the way the fab will make it. It shows the pads, the top and bottom copper, vias, silkscreen and reference designators.

Inner layers are not drawn

On a four-layer board, the copper view and the 3D view draw only the two outer layers. Tracks and fills on In1.Cu and In2.Cu do not show, and Layers has no switch for them. The Gerbers and the KiCad file carry every layer.

The palette switch at the foot of Layers changes how it looks:

  • Editor (the default) looks like a PCB editor. Copper is translucent, so crossings stay visible.
  • Board looks like the finished board, with solder mask and gold, as the 3D view draws it.

Before you click, the part under the pointer is outlined. The outline is exactly what a click will pick. Tiny parts get a target about 12 pixels wide, so they stay easy to grab.

One copper layer is active. It takes new tracks and draws in front, and the other layer fades. Switch with Page Up / Page Down, or click a layer swatch.

The grid step changes with the zoom, from 0.1 mm to 25 mm. Every fifth line is brighter. Boards built before 15 Sep 2026 have no silkscreen drawings, so each part draws as a plain box.

The picked part and a picked track glow in the selection colour. So does a track while you draw it. Nothing else on the board glows.

Rulers

Rulers run along the stage's top and left edges, in millimetres.

  • They read from the board's bottom-left corner, in the same frame as the readout.
  • Their ticks are the grid's lines, with a figure on every fifth.
  • A white mark on each ruler follows the pointer.
  • The picked part's extent shows on both rulers in the selection colour.
  • The Board palette has no grid and no rulers. A phone has no rulers either.

Move a part

  1. Drag the part. Or pick it and press an arrow key to move it one grid step.
  2. A pad within 1.2 mm of a pad on the same net snaps to it. Hold Alt to stop the snap.
  3. The part gets a pin mark in its corner, shown while it is picked. Turn on Pins in Layers to see every pinned part. The position saves a second after you stop.
  4. Press Rebuild. The placer keeps your part where it is and arranges the rest around it.

A move does not edit the built board. It writes a pin into the design's constraints, and every later build keeps that part where you put it.

Until you rebuild, the board shows a preview:

  • Tracks on the part's nets fade, and its ratsnest appears. Poured nets have no ratsnest.
  • Track ends on the part's pads follow the part. The router decides the real copper at the next build.
  • A bar in the header says what changed, such as 1 part moved, with Rebuild beside it. Hover over it for the whole sentence.

Only a rebuild makes a new version.

Turn or flip a part

  • R turns the picked part a quarter turn. Shift+R turns it the other way.
  • F flips it to the back of the board, and back again. On a touch screen, use to back / to front in the panel.

Some parts stay on top, where a person can reach them: connectors, switches, LEDs, modules and displays. A part with leads through the board cannot flip either, because it is on both sides already. If a flip is refused, the hint line says why.

A part on the back draws with a dashed outline and bottom-copper pads. In 3D it hangs under the board.

Pick, keep or delete a track

Click a track to pick it. The panel shows its net, layer, width and length, and whether you or the router drew it.

  • A track you drew: press Del, or click Delete this track.
  • A track the router drew: the next build routes it again, so deleting it would change nothing. Click Take this track over instead. The track is copied into constraints.tracks, and the next build keeps it. It is then yours to delete or redraw.

Where things overlap, a click picks a part first, then a track you drew, then a router track.

Draw a track

  1. Press X. Every pad gets a ring you can land on.
  2. Press on a pad and drag to where the track should end. Or click a pad, then click once for each corner.
  3. Finish on another pad of the same net, or on that net's existing copper.

The track takes the net and width of the pad it starts from. Each click lays two segments: one straight and one at 45°. You can also start from existing copper. That is how you fix a track the router got half right, or finish a net by hand.

Your track is an input to the next build, the way a pin is. It is saved in constraints.tracks, and the router must route around it. A track can stop halfway: the router finishes the net. The build's notes say which of your tracks it kept. The gaps list names any track it could not keep.

Layers and overlays

The Layers control sits in the stage's top corner and says how many layers are on, such as 6/8. Click it or press L. Press Esc or click outside it to shut it.

It opens a grid of switches: top copper, bottom copper, pads, vias, silkscreen and the ratsnest, each with a count. Findings, Pins and Congestion join them when the board has them. The ratsnest, Pins and Congestion are off by default. A switch that is off is dashed. Below the grid, click a net in Nets to isolate it, and everything else dims. View switches the palette.

The stackup and the fabrication sheet are facts about the board, so they are in the inspector, folded under the board's facts. The stackup's bands still switch copper and silkscreen.

Congestion is the predicted congestion. It shows where the routability model expected copper before routing. It also rings the pins the model expected the router to miss. Turn it on over the routed board to compare the two.

Findings on the copper

The Findings overlay marks each place KiCad's DRC found a problem in the copper. It is on by default, and it appears only when there is something to mark.

  • A white reticle with a red glow is an error that holds the Copper station.
  • An amber reticle is an advisory, such as a thermal relief short of spokes.
  • Findings on the same pads share one reticle. Its numbers show when you zoom in or look at it.

To look at one:

  1. Click Copper in the poll, press N, or click Show on the board under a finding.
  2. The board flies to the part, and the part is picked.
  3. A crosshair runs through the finding, with its position in millimetres and what DRC found.
  4. Press N for the next one, or Esc to let go.

The reticles take no clicks. A click on one picks the part under it.

A version built before 8 Oct 2026 kept no positions. When its copper holds, the workbench asks KiCad's DRC again on the version's own file. That takes a few seconds once, and nothing in the version is written.

3D

The 3D view with vendor models

The 3D view renders the finished board: FR4, glossy mask, gold pads and silkscreen. Parts use their vendor's 3D model where one exists (see KiCad and 3D models). Other parts are built from their package's outline.

  • The pill at the bottom sets what a drag does: Orbit, Pan or Zoom. Frame fits the board.
  • Shift + drag pans, and the wheel zooms.
  • The axis ball in the corner turns the camera. Click X, Y or Z for a side view, the dot opposite for the other side, or the centre to reset.
  • On a phone, Tilt orbits the board as you tilt the phone.
  • On a four-layer board, the inner copper is not drawn.

Schematic

The schematic sheet

The schematic is a real KiCad sheet, drawn with KiCad's own symbols. Power and ground are port symbols. The <board>.kicad_sch file in the version comes from the same record, so KiCad opens the sheet you see.

The server lays it out (soldermask/sheet.py):

  • Signals flow left to right, from power and inputs to outputs and indicators.
  • Pull-ups sit above the chip they serve. Pull-downs and decoupling capacitors sit below it.
  • A short net between two nearby pins is drawn as a wire. Every other net gets a label at each pin.

Two marks show real gaps in the design:

  • A no-connect X on a pad means the pad is on no net.
  • An open circle with a net name means the net has only one pin.

Arrange the sheet

  • Drag a symbol to move it. Its wires redraw, and its helpers move with it: an LED with its resistor, decoupling with its chip. The position is saved in constraints.sheet.
  • Drag a trunk up or down. A trunk is a net of three or more nearby pins on one horizontal lane. The lane is saved in constraints.wires. A net drawn as labels has no lane to move.
  • Symbols snap to KiCad's pin grid. Cmd+Z undoes.
  • Shift + drag pans, scroll zooms, and double-click shows the whole sheet.

Blocks

Library → Blocks lists circuit fragments. Examples are a regulator with its capacitors, or a CAN transceiver with its termination. A block comes from one of two sources:

SourceWhere it comes fromIts grounds for trust
MinedFinished boards from the corpusIt appears on at least three boards. The row shows how many.
AuthoredDiode's Zener reference designsA person wrote it against the datasheet. It has no board count.

Where both sources describe the same part, the authored block is the one listed.

Each row also shows the block's ports and whether it builds. A block builds when its parts resolve and it passes ERC. A block nobody has checked says unchecked. Blocks that do not build are still listed, with the reason. The usual reason is a part that is no longer stocked. Blocks that build come first.

Add to the board merges the block in. A port with the same name as one of your nets joins that net. The change arrives as a proposal.

Parts

Library → Parts searches JLCPCB stock by part number or description, for example AMS1117-3.3, 10k 0603 or USB-C. It lists only parts in stock.

Each row shows the package, unit price and stock. It also says where the footprint comes from: this pipeline's own drawing, or the vendor's unverified drawing for that exact part.

To add a part:

  1. Click Choose… on its row.
  2. Check its kind, value and purpose. The kind sets which electrical rules apply, so it stays blank when the catalogue is unclear.
  3. Pick a net for each pin. The list offers only pin names the build will accept.
  4. The part arrives as a proposal.

The part is pinned by its LCSC code, so the build uses exactly that part. You can leave its pins unwired. The build then reports an ERC error naming the part, and you can wire it later here or in the chat.

Proposals

A change to a board that already exists arrives as a proposal. A bar above the board says what accepting it would do:

Proposed · changes R1 · 1 net change: GND · 1 fewer ERC error · +$0.40 a board [Discard] [Accept]

The board under the bar is the proposal, already built and routed.

  • Accept makes it the next version.
  • Discard puts the board back as it was.

Nothing is written to the project until you press one. A proposal survives a reload.

Scope a change by selecting first. Pick a part, a net, or several parts with Shift-click. They show as chips under the message box. The model may change or remove only what is in scope, and it may add anything. So if you ask about the LED circuit, the regulator stays.

With nothing selected, a change can touch the whole board. A project's first board skips the proposal step.

The build log

While a build runs, the thread shows one row per stage:

Thinking · Resolving parts · Simulating · Placing · Routing · Writing fab files · Checking stock · Fetching 3D models · Saving

The running stage shows a clock. Finished stages show their time, and stages still to come are dimmed.

When the build finishes, the log stays under the reply. Each row says what its stage produced: parts resolved, placements rated, what the router did, the price and the version. Every log folds to one line, such as Built · 8 steps · 1m 12s, with a bar showing where the time went. Click it to open the rows.

The log is saved with the turn. A reload or a second device shows the same log. A page opened mid-build picks up at the current stage.

Placing, live. While the placer runs, the board gives way to six small boards, one per anneal. You watch the parts move and settle. Each board then shows the model's rating, and the one the router tries first is outlined. The rating is a guess, and the router decides. Within one board, the model's order is close to chance (see Routability).

The thread opens on your last message. Everything before it folds into one line, such as Show 6 earlier versions. Click it to open the history.

The thread has five kinds of row:

RowLooks like
Your messageA bubble on the right
A replyPlain text on the left. A paragraph the thread has already shown, such as the board's description, is not repeated.
A versionA card under the reply. The version on screen has an accent edge, its word, what holds and its price. Any other version is its light, id and word. Click it to open it.
A build the app startedOne line, such as Route again → v006 · NO-GO · 5.3s. Click it for the note, the log and the version's row.
An action the app started: Rebuild, Route again, Place again, or a file read inA quiet line in small grey text
A turn that failedRed, with the reason. It stays after a reload.

When a version turned away from GO, a line under its row says how and why. An example is GO → NO-GO: Copper 4 err, hole clearance. 2 unplated holes in the file, 0 in v003. A turn to GO needs no line: the row's own word says it. The version menu shows every turn, unfolded under its version.

A build that failed its checks and was revised makes two versions. It still shows as one reply, marked revised from v001.

The launch sequence. While a build runs, the poll's pill shows BUILDING with a clock and the stage that is running. The thread's log has every stage. When the build lands, the poll returns.

The message box says when it cannot send, for example when the server has no model. While a build runs, the thread stays where you scrolled it.

The inspector and the drawer

The inspector is the right column. It shows one thing at a time, and its breadcrumb says which.

PickedThe inspector shows
NothingThe board: its checks, the Why cards, then Generation, Board and Parts, then the stackup and the fabrication sheet, each folded to one line
Nothing, with the findings openThe findings
A partThe part card, led by any Why card that names the part
A trackThe track's layer, width and net
  • Generation holds the prompt, the model, tokens, cost and the model's assumptions.
  • Board holds parts, pads, nets, copper length and vias.
  • Parts lists every reference designator. Click one to pick that part.

The part card leads with the reference, and the buttons that turn the part or remove it. Its facts are the part number, package, JLC type (Basic or Extended), price, stock, position and rotation. It lists each pin with its name and net. On a phone it is in the details sheet.

The findings

The findings are every check on the board, in groups. They open in the inspector, and its breadcrumb reads Board › Findings.

ToDo this
Open every groupClick All findings, the last of the board's checks
Open one groupClick its check, the pill when the board is GO, or a box in the chain
Move between groupsClick a group, or press ↑ and ↓
Look at what a finding namesClick its reference or net. Click Findings in the breadcrumb to come back.
Close themClick Board in the breadcrumb, or press Esc with nothing picked

The findings start with one line in the poll's words, such as NO-GO. Copper 4 err. The groups follow, each with its count: Verdict, Electrical, Routing, Stock, Advisories, Precedents and Live sync. The picked group's findings show under the list and scroll on their own. The findings open on the worst group.

Under Routing, each place on the copper is one row, such as J1: 4 hole clearance, 0.171 to 0.213 mm against 0.25 mm. Its Show on the board flies to it. On a phone the findings are the details sheet's Findings tab, and the groups fold.

Advisories lists everything the build reported that the verdict does not read. Its count is the one on the poll. It holds three kinds of line:

  • What the design asked for and could not carry, the model's unsupported list.
  • The build's gaps, such as unresolved pins, substitutions, unverified footprints and copper that runs warm.
  • The build's notes, such as the physics review, the datasheet's layout rules and JLCPCB's fabrication limits.

The drawer

The drawer holds the build: its chain, its scope and its cost. It opens under the seam, the bar below the board.

ToDo this
Open a tabClick it in the seam, or press Backslash for the last one
Shut the drawerClick the open tab again, or press Backslash
Size itDrag the seam up or down. Drag it to the bottom to shut it.
Make it tallDouble-click the seam. Double-click again to put it back.

Cost shows the price per board on its tab. The drawer opens at the size you last gave it.

TabHolds
ChainThe build's stages and knobs
ScopeThe simulation traces
CostCost and stock at 1, 10, 25 and 100 boards, and a table of every part

On Cost, catalogue means stock was read from the parts catalogue on disk, which is the default. live means a parts server was asked, with SOLDERMASK_PARTS=jlcsearch. Anything that blocks a run is listed under the table.

Remove a part

Click Remove, or pick the part and press Del. The workbench builds the board without the part and offers it as a proposal.

  • Nothing is lost until you press Accept.
  • A net left with one pin goes too. The proposal names those nets.
  • Shift-click several parts to remove them in one change. You cannot remove every part at once.

The readout

The seam runs under the stage. After the drawer's tabs, it shows, from left to right:

  1. What is under the pointer: a pad (U1.1 · GND), a part (J1 · PZ254V-11-02P · HDR-1x2) or copper (+3V3 · B.Cu · 0.25 mm).
  2. What you can do with what is picked, dimmed. While you draw a track, how to finish it. With nothing picked, it points at Question and Cmd+K.
  3. At the far end, the pointer's position in millimetres while it is over the board, then the grid step and the copper layers. Click a layer to draw on it. While you draw a track, its length so far.
  4. Stock and sync, only when they want a look.

The board's size and layer count are the Board line in the inspector, such as 42 × 26 mm · 2 layers.

CheckShows
StockShort at the selected quantity. Hidden while every line is in stock.
SyncOff when this page has lost the server. Hidden while it is live.

The verdict is in the poll, and its checks lead the inspector. Click a check to open its findings. On a phone, the readout sits under the poll and scrolls sideways.

The scope

The Scope tab is an oscilloscope over the simulation. It plots voltage against time for every net the simulation traced.

  • The picked net is the highlighted trace. Pick it on the board, in the net list or in the legend.
  • Alt-click a legend chip to hide that trace.
  • Hover to read every net's value at that moment.
  • Click to set cursor A, and Shift-click to set cursor B. The legend shows Δt, its frequency and ΔV.
  • Scroll zooms the time axis, drag pans, and double-click shows the whole run.
  • Drag the bar above the tabs to make the region taller.

Zoomed out, each pixel column draws the lowest and highest sample it covers, so spikes stay visible.

A version with no simulation says so, and draws no trace. Simulation explains what is simulated, and when no simulation is written.

The data is sim.json, next to the version's board.json:

{"kind": "transient", "engine": "ngspice 44",
 "t": [0, 1e-6, 2e-6],
 "nets": {"VIN": [0, 4.9, 5.0], "+3V3": [0, 0.2, 1.1]},
 "stimulus": [{"net": "VIN", "kind": "step", "v": 5.0}],
 "unmodelled": ["U2"], "notes": [], "seconds": 0.8}
  • t is in seconds, ascending. Every trace in nets has the same length.
  • unmodelled names parts the simulation could not represent. The chain's Sim box shows them as warnings.

The chain

The Chain tab shows the build that made this board, as a row of boxes: Design, Resolve, Sim, Place, Route, Pour, Check, Fab and Price.

  • Each box shows the stage's time and result, such as the parts resolved or the router used.
  • Anything a stage could not do appears under its box, in the warning colour.
  • Click a box to open that stage's findings. A stage that did not run is dimmed.
  • Pour warns when ground had to be routed as tracks under the pour.

Three boxes have a button that runs their stage again:

ButtonDoesNew version?
SimulateRuns the simulation on this version's netlist, in secondsNo. It adds sim.json to this version.
Place againRebuilds with the next anneal seedYes
Route againKeeps the parts and placement, and routes again under the current constraintsYes

Route again picks up what changed since the build, such as a track you drew, a new floor, or a part you flipped.

The rack

The rack sits above the boxes. Its nine knobs change how the board is built, not what is on it.

KnobSetsSaved as
RouterWhich router lays the copper first: Lightcycle (default) or the A* routerrules.router
SeedThe anneal seed. The same design, pins and seed give the same placement.rules.seed
PourGround poured as a plane, or routed as tracksrules.pour
PrecedentWhether a similar corpus board may seed the annealrules.precedent
MarkThe maker's mark on the silkscreen, or nonerules.mark
FloorThe narrowest track any routed net may use, in mmrules.min_track_mm
SidesWhether the placer may use the backboard.sides
LayersTwo copper layers, or four: signal, a ground plane, signal, signal. SOLDERMASK_PLANES=gnd+power makes In2.Cu a power plane.board.layers
OutlineWhether the board may grow to fit its partsboard.fixed

Each knob is saved in the design's constraints a second after you turn it. Every later build uses it.

  • A knob you have set shows a dot under its label.
  • Until you rebuild, the stale bar counts the knobs you turned. Hover over it for what the next build will use, such as next build: the A* router, seed 3, no pour.
  • Place again raises Seed by one and rebuilds. Each version records the seed it was built with.

Variations are saved sets of knobs:

  • + save stores the knobs as they are now, under a name.
  • Click a chip to apply its set to the next build. Knobs the set does not include are cleared. Pins and your tracks are untouched.
  • The chip that matches the current knobs is lit. Double-click a chip to rename it, and click × to delete it.

The address

The address bar carries where you are. Copy it to share exactly what you see.

/p/mcp-esp32/v004/cu?pick=J1&drawer=chain&findings=route

PartValues
Path/p/<board>/<version>/<view>. The view is cu, 3d or sch.
pickA reference designator, net:GND, or finding:3 for the third finding
drawerchain, scope or cost, and on a phone findings. Leave it out and the drawer is shut.
findingsThe group open in the findings, such as route, or all. Leave it out and they are shut.
  • Each move to a new place is a step in the browser's history: a view, a pick, a version, a drawer tab or the findings.
  • Moving between groups of findings is not a step, so Back closes them.
  • Back and Forward walk those steps. Going back to another version opens it, as picking it in the version menu does.
  • A pan, a zoom or a hover is not a step. Neither is a move another device makes through sync.
  • A part or a net this version does not have is let go of.
  • /p/<board> opens the newest version and keeps the rest of the address.

Versions

The version chip in the header opens the version menu. It lists every version, newest first, with its verdict light, label, prompt and cost.

  • Click a version to open it. Your next message edits it.
  • Click its chevron to see what it changed, take its files, label it, add notes or fork it.
  • Import a file, at the foot of the menu, builds a design.json or reads a .kicad_pcb as the next version.
  • Esc shuts the menu.

See Versions and history.

On this page