-
Notifications
You must be signed in to change notification settings - Fork 3
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
Is it possible to use multiple readers? #5
Comments
Hi, Sorry for the late reply!
I think this should work without any conflict. |
I actually tried. In theory it worked. But for whatever reason I always had some random pending bits on reader 2 if I scanned the transponder on reader 1 and vice versa. I was able to just throw those bits away in the script but also my pi's cpu usage was always between 100% and 150% when I instanciated two instances of the WiegandReader object. I figured that could not be healthy for the pi and since I have no clue about the cpp side of your code I just got second pi for a second door. |
I tried to execute 3 readers but without any Wiegand device on a Raspberry Zero W 2 today (I don't have a real environment with multiple keypads). from time import sleep wr1 = WiegandReader(1,2) for _ in range(30): I don't see any change on the CPU load. I went through the cpp code but I can't spot anything that is related. |
Hello,
first of all: thanks for your work! It works really well with one reader. I'm wondering if it would work with a second reader on different GPIOs? Will it create problems if two card readings happen at the same time? Can I prevent those problems somehow?
The text was updated successfully, but these errors were encountered: