[LinuxCNC/linuxcnc Issue#117] UI becomes unresponsive after hitting limit switch About GRBL HAL

Issue #117 | 状态: 已关闭 | 作者: jepler | 创建时间: 2016-07-22

标签: affects 2.6 affects 2.7 affects master

Here are the steps I follow to reproduce the issue:

1. Use the attached config (it requires no particular hardware):

#1 – jepler 于 2016-07-22

In emcSendCommand echoserialnumber is never advancing. it’s stuck (in this case) at 23

(gdb) p ((EMCSTAT*)s->s->getaddress())->echoserialnumber
$7 = 23
(gdb) p s->serial
$8 = 30

task state (emcStatus->status) is rcs_exec (2), so task thinks it’s still doing .. something.

2.7.4 prints an interesting message before recovering:

Cannot unhome while moving, joint 0

is it possible that task is not fully clearing out an ongoing jog, and this ongoing jog is what prevents the jog from “ending”?

#2 – jepler 于 2016-07-22

@SebKuzminsky please let me know if you don’t reproduce it with this config file. @jethornton thanks for the config, it was easy enough to adapt to sim_parport.

#3 – c-morley 于 2016-07-23

I just had a similar problem on my lathe. Here I found the MPG was counting by it’s self do to a grounding issue.
This caused the axis to jog immediately at machine on, soon the ui was lagging behind commends.
It ran till estop or limit switch was tripped.
I assume the jogging flooded NML commands?
strangely after I would get that error ‘can’t unhome while axis 2 is moving’
Maybe this helps?
Chris M

#4 – SebKuzminsky 于 2016-07-27

I believe this is fixed in v2.6.12-63 and v2.7.5-31. I’d appreciate feedback from @jethornton and @c-morley, let me know if the issue is resolved for you in those versions.

原始Issue: https://github.com/LinuxCNC/linuxcnc/issues/117