ioSender keeps stopping because a "hard limit is reached" when no hard limit has actually been reached.

[ssylvan]

I don't know if this is a grblHAL issue or EMI issue or something else, but it's hard to debug because there's no indication what limit was supposedly reached when this happens (the little icon doesn't light up, and AFAICT the log doesn't tell you either).

This is what I see in the log:

Alarm:1 - Hard limit has been triggered. Machine position is likely lost due to sudden halt. Re-homing is highly recommended.
[MSG:Reset to continue]
<Alarm|MPos:56.178,178.152,-32.000|Bf:0,1023|FS:0,0|A:>
<Alarm|MPos:56.178,178.152,-32.000|Bf:0,1023|FS:0,0>
<Alarm|MPos:56.178,178.152,-32.000|Bf:0,1023|FS:0,0|Ov:200,100,100>
<Alarm|MPos:56.178,178.152,-32.000|Bf:0,1023|FS:0,0|WCO:70.000,120.000,-31.000>

Furthermore, it sure would be nice if I could resume the gcode file at the current position when spurious errors such as these cause the processing to stop.

Is there some way to get more information about what limit it thinks is being triggered?

[terjeio]

Most likely this is due to EMI. Use the $LEV (last event) command to check which input was triggered.

If you right click in the program listing you get a menu with some options, one is Start from here. You will have to ensure the controller is in the correct state first.