Skip to content
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

problem with the Write.py script. #68

Open
steaward opened this issue Feb 20, 2019 · 6 comments
Open

problem with the Write.py script. #68

steaward opened this issue Feb 20, 2019 · 6 comments

Comments

@steaward
Copy link

When trying to run the Write.py script, I get the following error:

Traceback (most recent call last):
File "Write.py", line 6, in <module>
reader = SimpleMFRC522.SimpleMFRC522()
File "/home/pi/MFRC522-python/SimpleMFRC522.py", line 14, in __init__
self.READER = MFRC522.MFRC522()
File "/home/pi/MFRC522-python/MFRC522.py", line 117, in __init__
self.MFRC522_Init()
File "/home/pi/MFRC522-python/MFRC522.py", line 390, in MFRC522_Init
self.MFRC522_Reset();
File "/home/pi/MFRC522-python/MFRC522.py", line 120, in MFRC522_Reset
self.Write_MFRC522(self.CommandReg, self.PCD_RESETPHASE)
File "/home/pi/MFRC522-python/MFRC522.py", line 123, in Write_MFRC522
spi.transfer(((addr<<1)&0x7E,val))
TypeError: function takes exactly 2 arguments (1 given)

Using Raspbian Stretch on a Pi 3.

@BombayCoast
Copy link

Same problem here. Doing it on a Raspberry pi 3 b+ with raspbian stretch.

@hawaii-do
Copy link

Same problem with python 2.7.13 on Raspbian 9.

@sandeeppusthey
Copy link

Me too having the same issue when Read.py is initialised

@steaward
Copy link
Author

@BombayCoast @te-ti @sandeeppusthey

Instead of going in and fixing the function call, I found it much easier to use pi-rc522.

Works no problem with Python 2.7, and I have tested it using the MFRC522 chip.
Takes a bit of reading, however.

Cheers!

@aa003
Copy link

aa003 commented Feb 22, 2019

Same problem with write.py on Raspberry Pi 3 Model B with python 3.5.3

@abrakhim
Copy link

Check my comment for issue #69 for a fix..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants