This is more likely an issue with esp32 rather than grbl esp but I’ll ask just in case this isn’t the case
If I wire my control switches to the following pins everything works as expected:
“`
#define CONTROLCYCLESTARTPIN GPIONUM_18 //WORKS
#define CONTROLRESETPIN GPIONUM23 //WORKS
Wiring my switches to the following pins does not execute the interrupts. I've confirmed the internal pull ups are enabled using a volt meter and that it is pulled to ground when the switch is pressed
``
#define CONTROLCYCLESTARTPIN GPIONUM_26 //interrupt not called
#define CONTROLRESETPIN GPIONUM27 //interrupt not called
GPIO_5 also does not generate the ISR
Using these pins, the interrupts are not run I've confirmed the interrupt isn't being called by putting a debug message in-
``
void IRAMATTR isrcontrol_inputs() {
grblmsgsendf(CLIENT_SERIAL, MsgLevel::Info, "isr called"); //not called for GPIO 26,27 and 5
`
Is there any reason why this might be the case ? I've disabled SD card (//#define ENABLESDCARD“) as I know some of those pins may conflict. So I cant think of any other reason for this behavior. I’m using an MKS DLC32 v2.1 board with the LCD disabled so only have a certain number of pins available.
Any ideas ? All help appreciated, thanks.
#1 – MitchBradley 于 2023-05-23
We are no longer supporting Grbl_ESP32. Consider upgrading to its successor FluidNC.