So I found that recompiling and downloaded resulted in inconsistent results. GPIO 35 and GPIO 34 both gave me errors if pulse_cnt tried to set them to outputs. As expected since these inputs are input only. Today; adding chan_a_config.flags.io_loop_back = 0; to turn the loop back off prior to runnin...

Previously we had run the rotary encoder with GPIO 26 and 32 as inputs. I reran them and found that sometimes they come up as Inputs only and sometimes they boot up with input and output enabled. For this application they work when input only, and sometimes they work with input/output. Though someti...

When my program starts the terminal shows that the input pins GPIO 25, 32, and 26 are all set for InputEn and OutputEn confirming that the esp32 is driving the input signals I want to count. Here is the terminal output at the beginning of my code execution: Note lines 559, 569, 619, and 629. These s...

<r>First I made a mistake in my post. GPIO25 pin out is low. I have to tie it to 3.3V to get the counter to see a high input. If I attach a 1k pullup resistor between GPIO25 and 3.3V the pin is still low. This implies to me that GPIO25 is driven low by the part. I've since created a second up/down c...

I've programmed a pulse counter to use gpio35 for counting up and gpio25 for counting down. We are using two optical detector pcbs to drive the input. Counting up on gpio35 works. But counting down does not. GPIO25 out is always high. Its as if the esp-idf is driving the output and I don't know how ...