Echo off and TCP "don't interrupt"

Chat freely about anything...
 Reply

User avatar

Echo off and TCP "don't interrupt"

By cnlohr
- Mon Sep 08, 2014 2:14 am #350 In attempting to port my AVR Minecraft server over to this sucker, I found out that you really can't use the AT command set provided to do very much since you have a command echo, and it will +IPD the data in the middle of you trying to talk to the chip.

If I try the traditional ATE0 it just says something like like:
no that fun

Has anyone uncovered any way to turn off echo, or only receive when solicited? Until one or both of these is handled, it will not be possible to implement any kind of reliable, non-challenge, response transport mechanism on top of the AT command set.
User avatar

Re: Echo off and TCP "don't interrupt"

By RichardS
- Mon Sep 08, 2014 12:19 pm #352 Yeah that is a big issue! It must have a way to turn that off.....

Richard.
User avatar

Re: Echo off and TCP "don't interrupt"

By JDub
- Wed Sep 10, 2014 10:05 pm #436 I've had a related question: if data arrives as a command is executing, will it be interleaved with the command's response?

Say, for instance, you send "AT+CWMODE?" and the module gets as far as replying with "+CWMODE:1\r\n" when suddenly data comes in. Will the remaining "OK\r\n" take precedence, or will the module first transmit the "+IPD" message?

I haven't actually tried to create this situation yet.

- Jw
User avatar

Re: Echo off and TCP "don't interrupt"

By cnlohr
- Thu Sep 11, 2014 3:11 pm #456 I have and it seems to have unpredictable outcomes. One of which includes the chip apparently locking up. I tried spamming it with 0's and all sorts of stuff it it no talkie. I am thinking the default firmware might actually be unworkable for most tasks.
 Reply
Return to General Discussions