- Sat Dec 13, 2014 10:38 am
#4748
@Bananis,
Its my minimal effort, you did the great part actually.
The AT+THINGSPEAK is really an interesting command I have added. What is actually does :
to communicate and send data to thingspeak IOT portal, the following commands need to send sequentially
1. AT+CIPSTART="TCP","184.106.153.149",80 [184.106.153.149" is the THINGSPEAK IP and 80 is the port]]
2. AT+CIPSEND=XX [XX is the length of data that to be sent in next statement as data]
3. after getting ">", we need to send the data as
GET /update?key=[THINGSPEAK_KEY]&field1=Y\r\n [where Y is a variable size or length of data]
The command will all job sequentially and internally without failure (almost!!)
There is the data I am transferring from my office space
https://thingspeak.com/channels/19285
And this is the link thorough which I am transfering data from my home [Data may be interrupted as my WLAN may needed to login periodically]:
https://thingspeak.com/channels/18190
However, as a core controller, I am using a PIC controller (which may not require after some weeks
)
@alonewolfx2,
I wish, I could. But it is really in very dirty shape as I have many many extra functions. I shall try to trim it as per needed. But you may please ask your quarries, I shall try to answer if I can with my limited knowledge [Please follow below why I am saying the present code condition is very dirty]
However, I am working with a new functionality. I feel, IOT SDK is slightly over-informed, and tremendously strong which may not be easy to digest. Hence, trying to grab it by parts. I am implementing a feature on AT SDK and something like:
1. ESP will start and start the server itself with predefined configuration [ AT+CWMODE=1;AT+CIPMUX=1;AT+CIPSERVER=1,9999; AT+CIPSTO=300)
2. Any client will just connect to it and send the custom command (AT+GPIOC=13,1) to switch ON the GPIO-13 or (AT+GPIOC=13,0) to switch OFF GPIO-13.
It will be just AT command through Client (instead of UART). And the server (ESP module) will reply back the result also over network.
3. The Server (ESP module) should be configured through network.
It is working fine as of now (a complex sequence of commands). But I am in dilemma of getting the Server (ESP module) IP [which was assigned by WiFi router if DHCP ON] from the client which is just another client in the WLAN.
As of now, I have following options to find the Server:
1. An ARP command and to map with MAC of the required or known server (ESP module)
2. Fix the Server-IP (ESP module) which is eventually just a client (in WLAN infrastructure view point) by disabling DHCP. But this may not work as the network may not be same and if the firmware is used in different place with different IP-addressing structure.
Lets see. I am behind this wild chip.
Its my minimal effort, you did the great part actually.
The AT+THINGSPEAK is really an interesting command I have added. What is actually does :
to communicate and send data to thingspeak IOT portal, the following commands need to send sequentially
1. AT+CIPSTART="TCP","184.106.153.149",80 [184.106.153.149" is the THINGSPEAK IP and 80 is the port]]
2. AT+CIPSEND=XX [XX is the length of data that to be sent in next statement as data]
3. after getting ">", we need to send the data as
GET /update?key=[THINGSPEAK_KEY]&field1=Y\r\n [where Y is a variable size or length of data]
The command will all job sequentially and internally without failure (almost!!)
There is the data I am transferring from my office space
https://thingspeak.com/channels/19285
And this is the link thorough which I am transfering data from my home [Data may be interrupted as my WLAN may needed to login periodically]:
https://thingspeak.com/channels/18190
However, as a core controller, I am using a PIC controller (which may not require after some weeks
)@alonewolfx2,
I wish, I could. But it is really in very dirty shape as I have many many extra functions. I shall try to trim it as per needed. But you may please ask your quarries, I shall try to answer if I can with my limited knowledge [Please follow below why I am saying the present code condition is very dirty]
However, I am working with a new functionality. I feel, IOT SDK is slightly over-informed, and tremendously strong which may not be easy to digest. Hence, trying to grab it by parts. I am implementing a feature on AT SDK and something like:
1. ESP will start and start the server itself with predefined configuration [ AT+CWMODE=1;AT+CIPMUX=1;AT+CIPSERVER=1,9999; AT+CIPSTO=300)
2. Any client will just connect to it and send the custom command (AT+GPIOC=13,1) to switch ON the GPIO-13 or (AT+GPIOC=13,0) to switch OFF GPIO-13.
It will be just AT command through Client (instead of UART). And the server (ESP module) will reply back the result also over network.
3. The Server (ESP module) should be configured through network.
It is working fine as of now (a complex sequence of commands). But I am in dilemma of getting the Server (ESP module) IP [which was assigned by WiFi router if DHCP ON] from the client which is just another client in the WLAN.
As of now, I have following options to find the Server:
1. An ARP command and to map with MAC of the required or known server (ESP module)
2. Fix the Server-IP (ESP module) which is eventually just a client (in WLAN infrastructure view point) by disabling DHCP. But this may not work as the network may not be same and if the firmware is used in different place with different IP-addressing structure.
Lets see. I am behind this wild chip.
