You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
I am working with a RPI with an attached AdaFruit 16x2 display plate that includes 5 pushbuttons. I have a Java app that sleeps for a second and then wakes to run some code that includes writing to the display. While that is going on, I have a GPIO listener configured for button presses. I have almost constant, repeatable GPIO read and write errors when both the button listener and the display writes are enabled. Turn either off and read/write errors disappear.
The code is based on the MCP23017GpioExample.java example included in pi4j distro.
Both display and buttons are connected to a single MCP27017 expander. Should I expect to be able to do this? Or is this architecturally a bad idea/not supported?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am working with a RPI with an attached AdaFruit 16x2 display plate that includes 5 pushbuttons. I have a Java app that sleeps for a second and then wakes to run some code that includes writing to the display. While that is going on, I have a GPIO listener configured for button presses. I have almost constant, repeatable GPIO read and write errors when both the button listener and the display writes are enabled. Turn either off and read/write errors disappear.
The code is based on the MCP23017GpioExample.java example included in pi4j distro.
Both display and buttons are connected to a single MCP27017 expander. Should I expect to be able to do this? Or is this architecturally a bad idea/not supported?
The text was updated successfully, but these errors were encountered: