When it refuses¶
Reflex declines to do things. Each message below is reproduced exactly as the machine renders it, because this page is generated from the same tables the app draws from — if a message changes and this page is not regenerated, the build fails.
A refusal is the controller working
None of these are faults in the software. Every one is the controller declining to cut something it cannot verify, and the alternative in each case is a ruined part or a crash. The useful response is to read what it asked for, not to look for a way around it.
Take-up refusals¶
Shown across the status gutter when a pass is stopped before it starts. Every one of these begins with Cut aborted, because the first thing an operator needs to know is the state of the machine, not the name of the fault.
Cut aborted — is the half-nut engaged?
The controller drove the leadscrew through its backlash and the Z scale did not move, so the carriage did not. Close the half nut and press Cut again — that is the whole recovery, and it is the fault this check exists to catch. If the half nut was closed, look for a slipping coupling, a disconnected Z scale, or a servo that is not enabled.
Cut aborted — WRONG-way motion. Check the Z scale direction.
The carriage moved, but the wrong way. This is a wiring or scale-direction fault, not a matter of not moving far enough, and it will corrupt every other ELS operation the same way. Check the Z scale direction in setup before doing anything else.
Cut aborted — servo in jog mode. Leave jog and press Cut again.
The servo is in jog mode, where the take-up is never consumed. Leave jog and press Cut again. Nothing is wrong with the machine.
Cut aborted — take-up did not complete. Re-engage the stop.
The take-up was commanded and never reached its target — the usual cause is the servo not being in sync mode at all. Pressing Cut again will not clear this: the motion gate stays shut until the ELS stop is disengaged and re-engaged.
Cut aborted — take-up stuck. Re-engage; the reference is lost.
The same fault, shown when you have a thread reference to lose. The remedy is forced — only the disengage/re-engage cycle releases the gate — and that cycle starts a new job, which clears the thread reference and any phase offset. There is no way around it; the message exists so it is not a surprise.
Cut aborted — backlash take-up failed.
The controller reported a take-up result this screen does not recognise, which usually means the UI is older than the firmware. Check the versions match.
Backlash calibration refusals¶
Shown in the calibration dialog. None of these move the machine.
Disengage the ELS stop before calibrating.
Re-engaging afterwards starts a new job, which clears the thread reference and any phase offset. Finish the thread first if you still need them.
A threading job is armed. Disengage first — but note the cost: re-engaging afterwards starts a new job, which clears the thread reference and any phase offset. Finish the thread before calibrating.
Servo is not in sync/index mode.
The servo is not in sync/index mode. The calibration normally puts it there itself, so seeing this means the mode could not be set — check the link and the servo's own state.
Calibration limits are not configured.
The calibration's limits are not configured. Set the ceiling and the motion threshold in setup; a zero motion threshold makes the firmware fail closed and is never a usable default.
Carriage did not move — is the half-nut engaged?
The calibration drove its full ceiling and the carriage never moved. Same physical fault as a refused take-up, and the same first check: is the half nut engaged?
Calibration aborted — conditions changed mid-run.
Conditions changed while the calibration was running — the ELS stop was engaged, or the servo mode changed. Re-run it undisturbed.
Thread phase offset refusals¶
Shown in the phase-offset dialog. Nothing is applied when one of these appears — the total on screen is still whatever the controller held before you pressed Apply.
Not connected to the controller, so there is nothing to apply the offset to. Reconnect and try again.
The link to the controller is down, so there is nothing holding the offset. Reconnect and try again; nothing was applied.
No threading job is engaged, and the controller discards the offset when one starts. Engage the ELS stop first.
No threading job is engaged. The controller discards a phase offset when a job starts, so it declines to hold one that would evaporate. Engage the ELS stop first.
No thread pitch is set — turning has no thread phase to shift. Choose a threading mode and a pitch first.
Turning has no thread phase to shift. Choose a threading mode and a pitch before setting an offset.
The machine geometry that turns a distance into leadscrew steps is missing or zero. Check the servo gearing in setup.
The servo gearing that converts a distance into leadscrew steps is missing or zero, so the offset cannot be expressed in steps. Fix the gearing in setup — and note that everything else the ELS commands is wrong by the same factor until you do.
A minus sign does not back the phase up — it becomes a forward move that opens the wrong side of the groove. Enter the distance without the sign, or press Clear.
A minus sign does not back the phase up: it becomes a forward move that opens the wrong side of the groove. Enter the distance without the sign, or press Clear.
That is a full pitch or more, which lands back in the groove you started at. Type a smaller offset, or press Clear.
A full pitch lands back in the groove you started at, so it is not a widening at all. Type a smaller offset, or press Clear. Note the field is absolute — the whole offset from the original groove, not an amount to add to what is already set.
Anything else¶
If you meet a message that is not on this page, the UI is older than the firmware driving it — the screens say so explicitly rather than printing a bare code. Check that the two halves are from the same release.