Purpose of the Serial AT Command Processor
Posted: Thu Jan 26, 2017 4:29 am
With the release of the Serial port AT Command Processor ... see:
http://espressif.com/sites/default/file ... les_en.pdf
I got to wondering about it. Are there any compelling use cases for it? If I understand it correctly, it is firmware (an application) that is precompiled and can be loaded into an ESP32. After which, the ESP32 will start communicating via UART to send and receive commands in "AT+" format. The commands allow us to form WiFi connections and from there TCP/IP network connections ... as either a sender or a receiver.
My core question is "When would one consider this pre-built application in a design?". Is there a core story that this would apply to? Is there some industry standard or specification to which these AT commands conform? For example, if the AT commands were a standard, then I could imagine building products that would talk these protocols and then choosing a supplier (eg. Espressif) to supply components that met the standards and hence not locking myself into one vendor.
http://espressif.com/sites/default/file ... les_en.pdf
I got to wondering about it. Are there any compelling use cases for it? If I understand it correctly, it is firmware (an application) that is precompiled and can be loaded into an ESP32. After which, the ESP32 will start communicating via UART to send and receive commands in "AT+" format. The commands allow us to form WiFi connections and from there TCP/IP network connections ... as either a sender or a receiver.
My core question is "When would one consider this pre-built application in a design?". Is there a core story that this would apply to? Is there some industry standard or specification to which these AT commands conform? For example, if the AT commands were a standard, then I could imagine building products that would talk these protocols and then choosing a supplier (eg. Espressif) to supply components that met the standards and hence not locking myself into one vendor.