ah I see. Thanks for the quick reply. Looks like my issue was a result of the amp hat I was using. The gpio pass through pins are somehow not connected properly to the pi. bypassing them got the encoder working. still struggling to get the center click to register but I’m sure the solution is somewhere in here already.
I ran jumpers from the pi to the hat instead of mounting the hat directly to the pi. They way I could access the pi gpio directly for the encoder. For some reason the pins on the amp hat reduced power passing through the open gpio.
Would it be possible to let us know if you found a solution for the “push” on the rotary? Mine didn’t work either, even if connected directly to the Raspberry. (I’ll focus myself on controlling volume for now…)
It should be working, when you directly connect to the RPi.
What GPIO are you using, how do you connect, do you use an external pull resistor, any additional settings made in /Boot/userconfig.txt?
For some GPIOs that are not internally pulled up by default, you may need to enable the internal pull-up in /Boot/userconfig.txt.
Details here
E.g. to enable the pull-up on GPIO 18 you would add gpio=18=pu
No, the CLK and DT pins of KY-040 already have hardware pull-ups.
You should only add it for the push-button pin, which does not have a hardware pull-up.
Hi WP, welcome to the thread. The Post you are referring to is from the first Rotary Encoder Plug-in. This Thread is about the Rotary Encoder 2 plug-in.
I’m the author of the latter.
Since both plugins work differently, your issue is probably different.
To help you, we need more info.
You can find more information about using the plug-in and how to report issues in the first post.
Read your problem report again: normally the plug-in does not do anything with the wifi or Ethernet connection.
I can think of two explanations:
The hardware connection/wiring of the rotary is causing issues:e.g. some unwanted current affecting the power supply (if you have such current, the power may be too weak to drive the network)
Something is sending commands so fast, that the RPi is too busy to run the network. But I never experienced such high load ever on my system. I can always connect via ssh even during debugging.
First recommendation is to check proper wiring
Which version of the plug-in do you use? It is displayed in the plug-in section under installed plugins
Keep in mind, that the RPi officially needs a 5.1V power supply. If you are running on a regular Phone-USB-Charger, you may already be violating the spec. They are normally rated 5V and the RPi drops a little voltage over its input protection circuit.
The above link also has the maximum current, that each model can drive on the USB.
Good luck!