-
Notifications
You must be signed in to change notification settings - Fork 78
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
Timeout? #47
Comments
Hi. Tnx for the question. What is the real use case of such feature? What would You like to achieve? |
I'm wondering on cases with disruption in the lines. Are there mechanisms to recover? |
Which side of the communication channel should retry after timeout? Master/Host/Server (cAT - which basically send responses only) or slave/client (external device with app which send requests and WAIT for responses)? Slave/Client side is responsible for ensuring that the cAT is in the "ready" state. Its very easy to achieve just by sending "\n" or "AT\n" and waiting for response. In both cases its job for Slave/Client app, not for cAT library. |
Does it make sense to add a timeout capabilities ?
Or is possible to implement some flush/reset of the internal state?
The text was updated successfully, but these errors were encountered: