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:
Code:
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:
Code:
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:
Code:
[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
