-
Notifications
You must be signed in to change notification settings - Fork 14
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
Maximum call stack size exceeded error #2
Comments
I'm aware of this problem. The package was a test and isn't ready for any serious use. The reader sends all data it can see to node with the tagdata attached, so node explodes. Normally you want the reader to notify you for changes and to read all tags every x milliseconds instead of the reader sending you everything. I still use LLRP toolkit (http://www.llrp.org) until I have time to write a good implementation in node. It's on my todo list. |
If I understand correctly, this is caused by very big/fast data blocks sent by the reader. I'm trying to dig this a bit. |
Yes the reader sends more events / data to node than node can handle. I have set myself the goal to have a proper node implementation by the end of the year. |
Hello... I am trying to implement this module with FX7500(zebra motorolla RFID reader) . can we stop the counting once it finished reading all tags in range ? now it's just keep counting ... |
That's how an RFID reader works, it reads till you tell it to stop reading. This library was a test, I do not intend to fix anything since I use other solutions (not LLRP), Zebra provides you with an SDK for your reader. |
Hello Glenngeenen thanks for this nice LLRP implementation. I found it useful to test my RFID reader(fx7500). it was reading the tags nicely... but now suddenly it does not count anything. nodejs just running and timeout. can u pls suggest me what can be the reason ? it will be really helpful for me. thanks in advance |
Sometimes it runs for minutes, sometimes it doesn't even start and throws the following error:
source is as follows:
The text was updated successfully, but these errors were encountered: