1. Configuring LinuxCNC
  3. Basic Configuration
  5. Cannot clear E-STOP, without error

Cannot clear E-STOP, without error

  • AlessandroEmm
  • Away
  • Junior Member
  • Junior Member
More
23 Feb 2026 15:47 #343346 by AlessandroEmm
Cannot clear E-STOP, without error was created by AlessandroEmm
Setup:
  • LinuxCNC with Remora SPI controller
  • 4-axis gantry configuration (XYYZ - dual Y motors)
My System is stuck in E-STOP state and cannot be cleared with F1 or any other method in Axis. F2 (Machine On) is greyed out all the time. The HAL states look fine from Remora side, thus i'm pretty certain that my issue is with some state/config that is LinuxCNC core. I tried other Frontends like gmoccapy and they behave pretty much the same except that they seem to have some timeout on e-stop blockage and claims that something external is blocking it while axis is keeping at it and never times out, but nothing ever changes even after minutes.

I have endstops configured too, but still tried no_force_homing to ensure its not a problem with endstops.

Some Infos about my setup:HAL Pin States:
iocontrol.0.emc-enable-in = TRUE (from remora.SPI-status)
iocontrol.0.user-enable-out = TRUE
iocontrol.0.user-request-enable = FALSE (never changes)
remora.SPI-status = TRUE
remora.SPI-enable = TRUE
motion.enable = TRUE
motion.motion-enabled = FALSE
HAL Configuration is default remora:
net user-enable-out <= iocontrol.0.user-enable-out => remora.SPI-enable
net user-request-enable <= iocontrol.0.user-request-enable => remora.SPI-reset
net remora-status <= remora.SPI-status => iocontrol.0.emc-enable-in

INI Configuration:
[TRAJ]
JOINTS = 4
NO_FORCE_HOMING = 1
COORDINATES = XYYZ

[KINS]
JOINTS = 4
KINEMATICS = trivkins coordinates=XYYZ kinstype=BOTH

[EMCMOT]
SERVO_PERIOD = 5000000
TRAJ_PERIOD = 5000000
BASE_PERIOD = 0

[TASK]
TASK = milltask
CYCLE_TIME = 0.010
 What is interesting is that noticed on click of e-stop the previously greyed out box of override limits becomes clickable.

Thanks for any help,
Alessandro

Please Log in or Create an account to join the conversation.

More
23 Feb 2026 17:57 #343351 by andrax
Replied by andrax on topic Cannot clear E-STOP, without error
Hi,

I think you have a syntax error.
setp iocontrol.0.emc-enable-in 1

Please Log in or Create an account to join the conversation.

More
23 Feb 2026 19:03 - 23 Feb 2026 19:12 #343355 by tuxcnc
Replied by tuxcnc on topic Cannot clear E-STOP, without error 

  • [b]Configuration is default remora:[/b]
  • [b][code]net user-enable-out <= iocontrol.0.user-enable-out => remora.SPI-enable
    [/code][/b]
  • [b][code]net user-request-enable <= iocontrol.0.user-request-enable => remora.SPI-reset
    [/code][/b]
  • [b][code]net remora-status <= remora.SPI-status => iocontrol.0.emc-enable-in
    [/code][/b]

I did it a long time ago and unfortunately I don't remember...
But I think I had the same problem.
My configuration looks like this:
# estop and SPI comms enable and feedback

#  net user-enable-out     <= iocontrol.0.user-enable-out          => remora.enable
#  net user-request-enable <= iocontrol.0.user-request-enable      => remora.reset
#  net remora-status       <= remora.status            => iocontrol.0.emc-enable-in

loadrt estop_latch
addf estop-latch.0 servo-thread
net estop-loopout       iocontrol.0.emc-enable-in  <= estop-latch.0.ok-out
net user-enable-out     iocontrol.0.user-enable-out  => remora.enable
net estop-loopin        remora.status  => estop-latch.0.ok-in => estop-latch.0.reset
net estop-reset         iocontrol.0.user-request-enable => remora.reset
net remote-estp         estop-latch.0.fault-in  <= remora.input.12.not
This is Remora via Ethernet, but the differences are probably cosmetic.
Last edit: 23 Feb 2026 19:12 by tuxcnc. Reason: Bad formatting
The following user(s) said Thank You: AlessandroEmm

Please Log in or Create an account to join the conversation.

  1. Configuring LinuxCNC
  3. Basic Configuration
  5. Cannot clear E-STOP, without error
Time to create page: 0.425 seconds
Powered by Kunena Forum