-
Notifications
You must be signed in to change notification settings - Fork 108
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
Command Timeouts (IDFGH-8185) #129
Labels
Comments
david-cermak
added a commit
to david-cermak/esp-protocols
that referenced
this issue
Sep 9, 2022
And adds an explicit timeout parameter to the esp_modem_at() Closes espressif#129
Timeouts updated in #139, also added the timeout parameter to the |
espressif-bot
added
Status: In Progress
Status: Reviewing
and removed
Status: Opened
Status: In Progress
labels
Sep 9, 2022
euripedesrocha
pushed a commit
to euripedesrocha/esp-protocols
that referenced
this issue
Oct 17, 2022
And adds an explicit timeout parameter to the esp_modem_at() Closes espressif#129
gabsuren
pushed a commit
to gabsuren/esp-protocols-1
that referenced
this issue
Oct 31, 2022
And adds an explicit timeout parameter to the esp_modem_at() Closes espressif#129
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is somewhat related to #66
From testing and from the BG96/95 modem data sheet require longer timeouts.
I have from testing been seeing both of these commands timing out when using the default 300ms.
It would also be useful if the
esp_modem_at
function had a custom timeout parameter.See BG95&BG77_AT_Commands_Manual.pdf pages 27 and 134.
The text was updated successfully, but these errors were encountered: