-
Notifications
You must be signed in to change notification settings - Fork 420
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
Code not working with Raspberry pi model B+ #40
Comments
First check wires:
If this is correct go to any tutorial and follow steps to install python-dev, enable SPI and change other settings on raspberry. If you are still stuck try to take fresh image and go by this tutorial; http://www.instructables.com/id/Raspberry-Pi-3-Model-B-MIFARE-RC522-RFID-Tag-Readi/ |
Similar problem. All wires are correct. $ lsmod | grep spi
spidev 7373 4
spi_bcm2835 7596 0 |
Similar problem.
|
I've got the same issues as the above - same reading as dingdayu. Followed the directions at http://www.instructables.com/id/Raspberry-Pi-3-Model-B-MIFARE-RC522-RFID-Tag-Readi/ I've actually got two Raspberry pi's with the same problem. One a model B V1.2 (in black case in photos 1 and 2) and one a B+ 2017 (in clear case photos 3 and 4). They are wired identically and using the same colour scheme - I can't see any problem with the wiring and I've tried replacing the wires.
Its powering up alright. I'm getting the following:
The config.txt is showing:
When I run lsmod I see:
I'm at my wits end trying to get this to work now for an office access card system. Can I please have help? |
Sorry should also add to the above that I've also tried two different RC522's. Currently got one hooked up to each pi but both having the same problem described at top of thread. All seems installed fine but not actually reading. |
Im not an expert, but the tutorial I followed suggested, that you have to enable bcm2708 instead of bcm 2835. I did that by adding the following line to the end of /boot/config.txt |
Thought that just related to the silicone of the chip itself which is different in the pi 3B. Since I'm out of ideas I gave it a go anyway though and still not working. Thanks for helping though. |
Well I bought a Raspberry Pi 3B+ two weeks ago and got it working following this git Edit: Nevermind, you're actually using the same library and did the same to implement it. |
I'm assuming you tried to run the Read.py file. What did that show? |
Same as the initial post unfortunately:
|
I did have the same problem with the 3B (two pi's tried and 2 different RFID readers) |
Would you possibly be able to post the read outs similar to the above you are getting with a working version please? Maybe I can work it out from there. |
Have you tried debugging or putting prints in the MFRC library, to see exactly which step, seems to be not working? |
Didn't hit any problems along the way when installing. Just didn't work at the end. |
Im not sure that I understand what you want from me, but this is the output I get (when it's working)
|
Could you tell me how things look when you run lsmod? |
and confirm that you are using the |
my lsmod output
|
If you bought it two weeks ago and downloaded the latest image rather than an old one it’ll be that |
Thank you - you’ve been very helpful |
yeah i downloaded the latest image, and even did an apt-get update IIRC |
Only lines I can see that differ are: Unfortunately I lack the skills to know any more about why yours works and mine doesn't. |
What type of RFID tags do you have? I noticed that MIFARE DESfire EV1 dont work, but EV2 do work Edit: You can check which ones you exactly have with an android app (NXP Tag Info for example) if your smart phone has NFC |
Same ones that came with the RFID-RC522 devices |
That means that they should work.... Then I'm out of ideas. Sorry! |
I appreaciate the help anyway. Seems unlikely to be hardware problems on two different pi's with two different RC522's. |
I am also facing the same problem with raspberry pi B+...When RFID tag says it works at 13.56Mhz, do we need to configure this frequency in the code, bcoz the spi speed is set to 1Mhz? i tried but it didn't work, any other ideas to make it work |
Hello, |
Hello,
In my case, the problem was the RFID board itself. I just used another one
from another seller and it worked fine
Le jeu. 23 mai 2019 à 10:45, Erjona1 <[email protected]> a écrit :
… Hello,
has anyone been able to solve this?
I am having the exact same issue.
I installed successfully but i cant make it read :/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40?email_source=notifications&email_token=ACE7BMBJ2IZQEHFUJU7HK4TPWZRS3A5CNFSM4DIVKMQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWBVTLY#issuecomment-495147439>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACE7BMD4LEEUEFU4GUX5NC3PWZRS3ANCNFSM4DIVKMQQ>
.
|
I was facing the same problem with MFRC522 and i just solve it connecting the RC522 IRQ pin into PIN 18 of GPIO |
Still not working. |
Yes! It works for me! ;) Keep trying Bro! |
Does not work for me. Any other ideas? Any test methods I could use? |
I would like to note that this code did not worked with the model B+
when executing (sudo python Read.py) I just got the following message:
Welcome to the MFRC522 data read example
Press Ctrl-C to stop.
when I touch the tag nothing happens.
Is there any diagnostic steps that I can follow to discover where is the bug?
The text was updated successfully, but these errors were encountered: