Troubleshooting¶
Find what you see on screen, and follow the link.
Start at the status bar¶
| You see | Go to |
|---|---|
![]() Disconnected, or no port to pick |
Connection problems |
![]() Connected but Not responding |
Connected but not responding |
![]() A banner under the status bar |
Firmware problems |
![]() Green, Responding, no banner, but something else is wrong |
Keep going |
Then the Control screen¶
The coloured status banner says what the machine is doing and the next step.
| You see | Go to |
|---|---|
| Waiting for the machine, badges showing —, controls greyed out | The machine won't move |
Fault: anything but NONE (the badge is red) |
Faults |
Restriction: anything but NONE |
Restrictions |
| Motion is off, Jog and Home greyed out | The machine won't move → Motion is disabled |
Everything reads NONE but a jog does nothing |
The machine won't move |
Or by task¶
| Problem | Go to |
|---|---|
| Flashing fails or the version doesn't change | Firmware problems → Flashing fails |
| A calibration run stops or reports an error | Motor calibration → What the findings mean |
| Force reads wrong | Load cell calibration |
| A test stops early, hangs in running, or can't be viewed | Tests and data |
| The app asks for the data folder again, or saves fail | Tests and data → Data folder |
What "normal" looks like¶

Connected, Responding, no banner, Fault: NONE, Restriction: NONE, and
Enable motion available. Theory of operation
explains what each of those means inside the machine.
Still stuck?¶
File a report from About → Report a bug: it attaches the app's session log, which is what a problem gets traced from. See Reporting a bug.



