Fixed homing fail alarm handling. Re-integrated software debouncing.
- [bug] Fixed a homing fail issue, where the alarm was not being set right, not cleared correctly. It would report the wrong code and enter an infinite alarm loop. This was due to how alarm codes were altered a while back. Now updated and fixed to show the right codes. - [feature] Re-installed optional software debouncing for hard limit switches. By request.
This commit is contained in:
parent
d5ed3bdb81
commit
864d1306b9
11 changed files with 66 additions and 28 deletions
|
|
@ -109,7 +109,6 @@ static void report_util_float_setting(uint8_t n, float val, uint8_t n_decimal) {
|
|||
// operation. Errors events can originate from the g-code parser, settings module, or asynchronously
|
||||
// from a critical error, such as a triggered hard limit. Interface should always monitor for these
|
||||
// responses.
|
||||
// NOTE: In REPORT_GUI_MODE, all error codes are greater than zero.
|
||||
void report_status_message(uint8_t status_code)
|
||||
{
|
||||
switch(status_code) {
|
||||
|
|
@ -123,7 +122,7 @@ void report_status_message(uint8_t status_code)
|
|||
}
|
||||
|
||||
// Prints alarm messages.
|
||||
void report_alarm_message(int8_t alarm_code)
|
||||
void report_alarm_message(uint8_t alarm_code)
|
||||
{
|
||||
printPgmString(PSTR("ALARM:"));
|
||||
print_uint8_base10(alarm_code);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue