ESP8266 Developer Zone

Re: [ignoredResponse] CRLF after +IPD

2016-07-30T13:15:52+08:00

I agree. We are sorry but because there is no demand for this feature, implementing this in the standard firmware will not be very useful or optimal. Please use the AT example in nonOS SDK to custom code your application requirements.

Statistics: Posted by Guest — Sat Jul 30, 2016 1:15 pm

Re: [ignoredResponse] CRLF after +IPD

2016-07-29T15:10:52+08:00

tilz0R wrote:
Why you don't want to add CRLF after +IPD statement with data?

Sorry, it does not make sense. +IPD command declares number of bytes to follow, you should use that.

Additional symbols CR LF after the data are just waste of time. Anyone who sends data where CR LF can appear inside data packet will not be able to use CR LF as symbols indicating end of data.

Statistics: Posted by akouz — Fri Jul 29, 2016 3:10 pm

Re: [ignoredResponse] CRLF after +IPD

2016-07-29T14:08:53+08:00

Is there any improvement regarding this?

Statistics: Posted by tilz0R — Fri Jul 29, 2016 2:08 pm

Re: CRLF after +IPD

2016-07-14T12:16:27+08:00

Hello,

I have forwarded this issue to the engineers working on the AT firmware. Meanwhile, you may always customize the AT commands according to your requirements by adding custom commands and responses. The demo is in the NONOS_SDK.
Thank you for your input!

Statistics: Posted by Guest — Thu Jul 14, 2016 12:16 pm

Re: CRLF after +IPD

2016-07-12T00:56:11+08:00

SIMx00 devices uses AT commands too, and they return CRLF after +IPD statement with data.

Easiest and cost performance is to save read data from device to buffers and read strings until you detect LF character. The problem is in this case:

+IPD,x,y:mydataislong0,CLOSED.

My working buffer has for example length that it will save +IPD...0,CLOS and not with ED at the end so I can't detect that "easily".
This makes me to write data back to cyclic buffers at the beginning of buffer and so on.

Or at least you can add command to enable characters before command response is received or add it to any +IPD at the end.

Using your SDK is not my option right now. I'm working with STM32 devices and I have ESP as device to access to internet a few times. I don't need to learn SDK right now. I have my own ESP parser library for AT and I have problems to solve this easily and without complications.

http://esp8266at.com is a website for parser.

Statistics: Posted by tilz0R — Tue Jul 12, 2016 12:56 am

Re: CRLF after +IPD

2016-07-10T22:05:38+08:00

Hello,
Your request has been noted.
However, we have issued a lot of updates already and by now, the AT responses have become rather standard. Changing the structure of a response will render many currently used parsers ineffective.

If you find the parsing CPU consuming or difficult, please use our SDK to write programs that run directly on the ESP8266. It can work at up to 160MHz, which can help simplify your design and eliminate the need for using AT command firmware as well.
Let us know if you need help getting started, we are happy to help!

Statistics: Posted by Guest — Sun Jul 10, 2016 10:05 pm

[ignoredResponse] CRLF after +IPD

2016-07-29T14:08:34+08:00

Why you don't want to add CRLF after +IPD statement with data?

This could provide better programming for AT parsing. Adding these 2 characters does not cost you more than 2 characters and 10 seconds of work.

You simply ignored this request previously.

It is added before +IPD, so:

CRLF
+IPD.....

Why not also after it?
If this makes problem for you, add CRLF before any command you send.
It is easier and performance better to check for CRLF than "any character" and always check what is it.

Statistics: Posted by tilz0R — Sun Jul 10, 2016 4:36 pm