-
Notifications
You must be signed in to change notification settings - Fork 95
How to continue after error on serial port? #252
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
Comments
Hi @Artyrm, The serial port were an XBee is connected must only be used by one application. In this case, by the one using the library. There is no other mechanism to open/close the local connection with an XBee. Best Regards. |
Hi @tatianaleon Thank you for your reply. For now I came up with that:
Note the threaded run of |
Well, #252 (comment) seems suitable. |
This commit configures exclusive access for the provided XBee serial port by default. This can be overridden in the constructor (although not recommended) #222 #252 Signed-off-by: Tatiana Leon <[email protected]>
…reading #222 #252 Signed-off-by: Tatiana Leon <[email protected]>
This commit configures exclusive access for the provided XBee serial port by default. This can be overridden in the constructor (although not recommended) #222 #252 Signed-off-by: Tatiana Leon <[email protected]>
…reading #222 #252 Signed-off-by: Tatiana Leon <[email protected]>
If serial port being accessed by another application, or if it was briefly disconnected, device.reader gives an error, closes port and stops _packet_listener. But I want to reconnect after that. How to do it?
device.close() and device.open() sequence takes too much time (~1min) to use it.
The text was updated successfully, but these errors were encountered: