-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
edge detection nok #61
Comments
This issue happens on the latest, manually installed code as well. I achieved a little progress with a small change and now the error is not thrown anymore. But edges are only detected about 75% of the time and such race / threading is exceeding my capa. Also I assume that gpiod doesn't leverage interrupts and hence edges have to be detected by polling. If someone can point me to working edge detection on Fedora IOT that would be very much appreciated. Just found this which may be of help toradex/torizon-samples#4 |
Missed edges have been blocked by @theyoyojo to you think the multiple detections/debounce is fixable in |
Libgpiod does not currently support debounce and may get it in v2. We may consider to implement debounce as a workaround in |
Hi, I haven't had time to look through this until now but I will get to it soon. |
Issue
An state change (edge) on the rpi3's gpio will raise
TypeError: 'list' object is not callable
. Sometimes this issue requires two edges to occur andadd_event_detect
seems to fail to detect edges at all. I have tried a few variations in the code but the behavior seems consistent on two identical systems.System Info
Reproduction Script edge_test.py
Symptome
Can someone reproduce it or spot the issue in my code?
The text was updated successfully, but these errors were encountered: