PRIME MOTIONSupported controllers
The controller is the board that turns G-code into motion. Prime Motion talks to the controller, not to the frame around it, so what matters is the firmware the controller runs:
| Firmware | Typical machines | Settings written from the app |
|---|---|---|
| Grbl 1.1 | Most hobby routers: Shapeoko, LongMill MK2, Genmitsu 3018 and similar | Yes |
| grblHAL | Newer and 32-bit controllers: LongMill MK3, AltMill, OpenBuilds BlackBox X32 | Yes |
| FluidNC | ESP32 controllers | No: FluidNC keeps its settings in its own configuration file |
The split does not follow manufacturer lines. One maker can ship both Grbl 1.1 and grblHAL in different models, which is why the setup wizard shows the firmware beside each model.
How Prime Motion knows which it is
Each machine profile records an expected firmware family. When the controller connects, Prime Motion reads how it identifies itself and its settings, and from then on works with what the controller proved. Settings → Connection → Firmware shows the same family, version and source as Settings → Firmware. Live from controller identifies this connection's answer; Last read from or Catalog seed identifies a reference instead.
Firmware Family in Settings → Connection is only the starting point for a controller that says nothing about itself.
When the profile and the controller disagree
If the profile says one family and the controller proves another, Settings → Firmware shows a Firmware family card with both sides, under This machine and The controller, and a button, This machine runs family, that updates the profile.
Similar cards appear for other disagreements Prime Motion can measure:
- Homing switches — the profile expects homing and the controller has it switched off (
$22=0), or the other way round. The card offers to record that the machine has no switches, or to turn homing on in the controller. - Homing corner — the controller homes to a different corner than the profile says.
- Axis count — the controller reports a different number of axes.
Read each card's consequence line before choosing. A button that writes to the controller is unavailable on FluidNC, or with no live connection, and says why when you tap it.
What differs in practice
For ordinary three-axis work you are unlikely to notice which family you have. The differences that do show up in Prime Motion:
- Work coordinate systems. Grbl 1.1 reports six (G54 to G59). grblHAL can report nine, adding G59.1 to G59.3. Prime Motion offers whatever your controller reports and nothing more.
- Alarm codes. grblHAL adds alarms Grbl 1.1 does not have, such as an emergency-stop input (ALARM:10) and homing required (ALARM:11). The machine-condition drawer on Control explains each code it sees.
- Setting groups. On grblHAL, Settings → Firmware groups settings the way the controller groups them.
If your machine is not in the list
Choose Custom / Generic GRBL in the setup wizard. Nobody has filled in the travel for you, so the wizard asks for it. If the controller speaks Grbl 1.1, grblHAL or FluidNC, Prime Motion can drive it.