[MSG:INFO: '$H'|'$X' to unlock]
$H
ok
G0 X1000
[MSG:INFO: Soft limit on X target:1000.000]
ALARM:2
[MSG:INFO: Reset to continue]
这里我在这里发送 G91 和 G0X10 没有回音或响应。 然后我发送 ^X 来清除警报。
[Reset]
ok
Grbl 3.3 [FluidNC v3.3.0 (FeedholdAfterSoftLimit-2505156) (wifi) '$' for help]
[MSG:INFO: '$H'|'$X' to unlock]
ok
G91
error:9
ok
G0 x10
error:9
switch (rtAlarm) {
case ExecAlarm::None:
return;
// System alarm. Everything has shutdown by something that has gone severely wrong. Report
case ExecAlarm::HardLimit:
case ExecAlarm::SoftLimit:
sys.state = State::Alarm; // Set system alarm state
alarm_msg(rtAlarm);
report_feedback_message(Message::CriticalEvent);
protocol_disable_steppers();
rtReset = false; // Disable any existing reset
do {
// Block everything except reset and status reports until user issues reset or power
// cycles. Hard limits typically occur while unattended or not paying attention. Gives
// the user and a GUI time to do what is needed before resetting, like killing the
// incoming stream. The same could be said about soft limits. While the position is not
// lost, continued streaming could cause a serious crash if by chance it gets executed.
pollChannels(); // Handle ^X realtime RESET command
} while (!rtReset);
break;
default:
sys.state = State::Alarm; // Set system alarm state
alarm_msg(rtAlarm);
break;
}
rtAlarm = ExecAlarm::None;
当您处于警报模式时,该字符不再在串行终端回显。一旦警报被清除,这些字符就会随响应一起回显。
这是一个示例会话..
这里我在这里发送 G91 和 G0X10 没有回音或响应。
然后我发送 ^X 来清除警报。