- Thu Sep 11, 2014 4:13 pm
#460
Just a guess: Are you using appropriate delays between commands to give the chip sufficient time to fully execute the command?
- Sun Sep 28, 2014 9:47 pm
#997
I was, but things seem to work a lot better when I completely disable echo. Which reminds me - if people want, I can try to post that firmware somewhere.
Echo off seems to have helped so much I don't need to figure out how to make it buffer the TCP incoming packets.
Echo off seems to have helped so much I don't need to figure out how to make it buffer the TCP incoming packets.
- Mon Sep 29, 2014 10:33 am
#1014
To me it's not only the echo but the human like responses instead of a OK/NOK reply. Parsing the replies is not so easy.
Did anyone look into creating a decent AT firmware?
Did anyone look into creating a decent AT firmware?
- Mon Sep 29, 2014 11:09 am
#1016
Check out the "Community Project to fix AT+ Commands" section. But, I will admit, those responses are kind of annoying. Though I don't want to break human readability, I think there are things we can do to simplify it.
