FluidNC reset_pin

Software / Firmware Jackpot Board / FluidNC
1

Has anyone successfully used the reset_pin control pin with FluidNC?

I configured the reset_pin first using an Airedale expander pin:

control:
  reset_pin: uart_channel2.0:pu:low

…and after that didn’t work out, using an onboard input on the 6x CNC Controller:

control:
  reset_pin: gpio.2:pu:low

With either pin configuration, triggering the input (connecting the input to gnd) for only fractions of a second causes a reset as desired, but causes the controller to go into alarm over the reset_pin input being active on startup:

<Idle|MPos:0.000,0.000,0.000,0.000|Bf:15,256|FS:0,0|Ov:100,100,100|A:F>
Grbl 3.9 [FluidNC v3.9.8 (wifi) ‘’ for help]
[MSG:ERR: reset_pin is active at startup]
Grbl 3.9 [FluidNC v3.9.8 (wifi) ‘’ for help]
[MSG:ERR: reset_pin is active at startup]
Grbl 3.9 [FluidNC v3.9.8 (wifi) ‘’ for help]
[MSG:ERR: reset_pin is active at startup]
[MSG:INFO: ALARM: Control Pin Initially On]
ALARM:11
[MSG:INFO: ALARM: Control Pin Initially On]
ALARM:11
[MSG:INFO: ALARM: Control Pin Initially On]
ALARM:11
<Alarm|MPos:0.000,0.000,0.000,0.000|Bf:15,256|FS:0,0>
[MSG:INFO: ALARM: Control Pin Initially On]
ALARM:11
[MSG:INFO: ALARM: Control Pin Initially On]
ALARM:11

2

Interesting. Not sure how you could put a delay on to give you time to let go of the reset button unless it was on the pre-reset side of the code. I know the buttons on the esp32 have a debounce cap, I guess now I know why?

3

Maybe it could be changed to reset on the rising edge instead of the falling edge of the signal. Then it would reset when you released the button.

That should be an easy thing to change in the code, if you can’t change it in the config.

1 Like
4

I’m not sure what’s on the board for input debouncing. I think the simplest solution would be for the code to have a delay, at least for the reset input, to wait for the input(s) to stabilize on boot.

More than anything, I’m just surprised that something so simple doesn’t work. The docs say:

This section is used for control inputs. These are typically used with switches.

At least, unsurprisingly, the feed hold and cycle start inputs work as expected.

1 Like
5

Dang, you are good.

6

Hrm. Weird. I’m on v3.9.8. Mitch added a 1000ms delay on March 8.

bool Control::startup_check() {
    bool ret = false;
    for (auto pin : _pins) {
        if (pin->get()) {
            delay_ms(1000);
            if (pin->get()) {
                log_error(pin->legend() << " is active at startup");
                ret = true;
            }
        }
    }
    return ret;
}
1 Like