From 9f7f2709912de5633ba50630fe4a523960177885 Mon Sep 17 00:00:00 2001 From: Martin Poelstra Date: Fri, 13 Feb 2015 22:50:07 +0100 Subject: [PATCH] Fix EXEC_ALARM_* flags: soft limit would lead to hard limit error. --- grbl/system.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/grbl/system.h b/grbl/system.h index 58b67d1..d6e190e 100644 --- a/grbl/system.h +++ b/grbl/system.h @@ -41,10 +41,10 @@ // this halts Grbl into an infinite loop until the user aknowledges the problem and issues a soft- // reset command. For example, a hard limit event needs this type of halt and aknowledgement. #define EXEC_CRITICAL_EVENT bit(0) // bitmask 00000001 (SPECIAL FLAG. See NOTE:) -#define EXEC_ALARM_HARD_LIMIT bit(0) // bitmask 00000010 -#define EXEC_ALARM_SOFT_LIMIT bit(1) // bitmask 00000100 -#define EXEC_ALARM_ABORT_CYCLE bit(2) // bitmask 00001000 -#define EXEC_ALARM_PROBE_FAIL bit(3) // bitmask 00010000 +#define EXEC_ALARM_HARD_LIMIT bit(1) // bitmask 00000010 +#define EXEC_ALARM_SOFT_LIMIT bit(2) // bitmask 00000100 +#define EXEC_ALARM_ABORT_CYCLE bit(3) // bitmask 00001000 +#define EXEC_ALARM_PROBE_FAIL bit(4) // bitmask 00010000 // Define system state bit map. The state variable primarily tracks the individual functions // of Grbl to manage each without overlapping. It is also used as a messaging flag for