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

Initialization hangs without nonblock_io option #39

Open
phemmer opened this issue Jun 25, 2014 · 0 comments
Open

Initialization hangs without nonblock_io option #39

phemmer opened this issue Jun 25, 2014 · 0 comments

Comments

@phemmer
Copy link

phemmer commented Jun 25, 2014

When attempting to connect, if the nonblock_io option is not passed, it does not connect, and ends up hanging instead.
The code by default sets @read_byte_size = 9600, then in the read method, it blocks trying to read 9600 bytes. During connect, when it waits for the version report, it hangs because the version report is only 8 bytes.

Because it is sitting there sending the "version report" command over and over, the responses will eventually fill the buffer and cause the loop to end, but it takes a very long time.

@phemmer phemmer changed the title Does not work without nonblock_io option Initialization hangs without nonblock_io option Jun 25, 2014
phemmer added a commit to phemmer/arduino_firmata that referenced this issue Jun 27, 2014
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

1 participant