Error running self.i2c._initialize() when starting RFID
Closed this issue · 1 comments
aricearice commented
Steps to Reproduce
- Followed the instructions here: http://tessel.github.io/t2-start/modules/rfid.html
- Get the following error in the console:
$ t2 run rfid.js
INFO Looking for your Tessel...
INFO Connected to charizard over USB
INFO Writing rfid.js to RAM on charizard (58.368 kB)...
INFO Deployed.
INFO Running rfid.js...
/tmp/remote-script/node_modules/rfid-pn532/index.js:64
self.i2c._initialize();
^
TypeError: self.i2c._initialize is not a function
at new RFID (/tmp/remote-script/node_modules/rfid-pn532/index.js:64:12)
at Object.use (/tmp/remote-script/node_modules/rfid-pn532/index.js:723:10)
at Object.<anonymous> (/tmp/remote-script/rfid.js:13:20)
at Module._compile (module.js:426:26)
at Object.Module._extensions..js (module.js:444:10)
at Module.load (module.js:351:32)
at Function.Module._load (module.js:306:12)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:117:18)
at node.js:948:3
events.js:85
throw er; // Unhandled 'error' event
^
Error: Error upon remote process exit: 1
at USBProcess.<anonymous> (~/.nvm/versions/node/v0.12.5/lib/node_modules/t2-cli/lib/usb/usb_process.js:49:26)
at USBProcess.g (events.js:199:16)
at USBProcess.emit (events.js:107:17)
at Parser.<anonymous> (~/.nvm/versions/node/v0.12.5/lib/node_modules/t2-cli/lib/usb/usb_daemon.js:121:14)
at Parser.emit (events.js:107:17)
at Parser._write (~/.nvm/versions/node/v0.12.5/lib/node_modules/t2-cli/node_modules/usb-daemon-parser/index.js:152:16)
at doWrite (_stream_writable.js:301:12)
at writeOrBuffer (_stream_writable.js:288:5)
at Parser.Writable.write (_stream_writable.js:217:11)
at ondata (_stream_readable.js:540:20)
at emit (events.js:107:17)
at readableAddChunk (_stream_readable.js:163:16)
at Readable.push (_stream_readable.js:126:10)
at InEndpoint.emit (events.js:107:17)
at Transfer.transferDone (~/.nvm/versions/node/v0.12.5/lib/node_modules/t2-cli/node_modules/usb/usb.js:295:9)
I'm on OS X 10.10.5
johnnyman727 commented
Thanks for reporting this! It turns out it was actually fixed in tessel/rfid-pn532@c53246c but we forgot to publish it.