Desktop metal mill + bit-exact digital twin

Cut it in the twin. Then cut it for real.

Twinwright Studio runs the MC-1’s own firmware against a physics model of the machine: drives, spindle, cutting forces, chatter, collisions. Learn CNC and prove your G-code for free. When the part comes out right in the twin, run the same file on the same machine.

Windows 10/11 · English and Chinese · free preview

MC-1
MC-1 twin
TwinReal

The MC-1 as Studio simulates it (left) and as it is built (right): one model, rendered twice from the CAD.

UnmodifiedgrblHAL core — the firmware the real machine runs
245 checksautomated acceptance tests, all passing
15 partsexample programs run to the end; 14 compared cell by cell with their CAD
Bit-identicalresults on Windows and Linux; every run replays exactly
5 reportsfirmware and simulator issues found by the twin, filed upstream
How it works

Learn and verify in the twin. Make on the machine.

The simulator and the mill share one design, one firmware and one set of settings, so what you practise is what you will operate.

1LEARN

Learn without breaking anything

Start in demo mode and move up through five interface levels, from operator to researcher. Crash the spindle into the vise, trip a limit switch, lose the VFD link — then read what the controller said and why.

In Studio · free
2VERIFY

Prove the program before metal

Check mode parses every line the way the controller will, and twelve rules catch what it accepts but should not. The run finds rapids into stock, collisions, soft-limit alarms and chatter, compares the part with your CAD, and the optimizer makes it faster without a heavier cut.

In Studio · free
3MAKE

Cut it on the identical machine

The MC-1 runs the same grblHAL build with the same settings. Each machine ships with its own calibrated twin, and shadow mode flags the moment the machine and the twin disagree.

On the MC-1
Inside the twin

Not an animation of G-code. A model of the machine.

Most simulators draw the toolpath. Studio simulates the controller, the drives, the spindle and the cut, at the timing of the real hardware.

Controller

The real firmware

The grblHAL core, unmodified, with the MC-1’s pin map and settings. Error and alarm codes come from the firmware itself and are explained in plain language.

Drives

Closed-loop steppers

Following error, pull-out torque and drive alarms; at the higher levels, ball-screw stiffness, backlash and the impacts inside the play.

Spindle

VFD over RS-485

The Huanyang VFD’s Modbus protocol, ramps, load and stall, DC-bus hold-up — and what happens when the cable breaks mid-cut.

Material

Material removal

A height-map workpiece down to 0.01 mm with real tool shapes: flat, ball, bull, V, drill, thread mill, T-slot and dovetail, undercuts included.

Cutting

Forces and chatter

Cutting force and torque for 17 materials, spindle load, tool deflection and stability lobes: Studio suggests a spindle speed that will not chatter.

Accuracy

Errors that real machines have

Lead-screw error tables, straightness, squareness, backlash and thermal growth. Run ISO 230-2 positioning and ISO 230-4 circle tests on the twin.

Electrics

Switches, wires and power

Inductive limit switches, tool setter, E-stop and contactor, power loss and cold start. Inject a broken wire or a glitching sensor and watch how the machine fails.

Workholding

Vises, clamps and tape

Place blanks in a vise, under clamps or on tape, or load your own STL blank. If the cut outgrows the grip, the part slips — as it would.

Programming

An editor that knows the machine.

Write G-code in Studio and the twin answers line by line: how long each line took, why a feed was not reached, which of twelve rules it breaks. Stop the run at a line or when the force climbs, restart from any line, compare versions — then let the optimizer make it faster.

  • Times in the margin that add up to the run time exactly
  • Breakpoints on a line, a force, a load, a near miss or a chatter margin
  • An optimizer that proves every change in the twin: all 15 examples 0.2–8.1 % faster, parts unchanged
The optimizer's result next to the version before it: 30.4 s → 27.2 s, only feeds and one spindle speed changed.
The optimizer's result next to the version before it: 30.4 s → 27.2 s, only feeds and one spindle speed changed.
Studio + AI

Let your AI assistant check its own G-code.

An MCP server is built into Studio. Turn on the AI switch and click Connect: Claude, ChatGPT, Cursor, VS Code or a local model can set up a blank, check, simulate and optimize a program, and look at pictures of the result — before anything reaches a real machine.

  • One-click setup for Claude Desktop, ChatGPT desktop, Cursor, VS Code and LM Studio
  • Or chat inside Studio with your own key (Anthropic, OpenAI, DeepSeek, Qwen, Kimi, GLM) or a local model
  • The AI works on twins, never the machine; changes to your window need your OK, and every call is logged
The machine

The MC-1: a small mill built like a big one.

Machined 6061-T6 plates, HGR15 linear rails on every axis, C7 ball screws with fixed and floating end supports, closed-loop steppers and an 800 W water-cooled spindle. 200 × 150 × 80 mm of travel for aluminium, brass and engineering plastics.

200 × 150 × 80 mmtravel X × Y × Z
800 W · 24,000 rpmwater-cooled ER11 spindle
HGR15 · SFU1204 C7rails and ball screws, all axes
~57 kgmachined aluminium frame
grblHALTeensy 4.1 controller
ISO 230-2measured before it ships

Founders’ batch from $4,990

Indicative prices. USD and EUR exclude VAT or sales tax, duties and shipping; CNY includes 13 % VAT.

MC-1
Example parts

Fifteen parts, proven in the twin.

From an ISO test piece to a watch wheel with 0.3-module teeth. Every program was run to the end in Studio and compared with its design part, then cross-checked with CAMotics.

Evidence

Checked, not just claimed.

Every run replays bit for bit. The example parts, the test results and the optimizer's benchmark are published with their numbers, and the bugs the twin found in the grblHAL firmware went upstream with reproductions. Where a figure is still a design value, we say so.

Start in the twin.

Join the early-access list for the free Studio preview. Load an example, change a line, run it — and when the part comes out right, the same program runs on the MC-1.