- Mon Dec 08, 2014 2:18 pm
#4308
There is absolutely no need to put GUI in ESP. Instead its better to create a server with web API (like IoTSDK) which will only respond with json response.
This will greatly reduce the space requirement and increase the response speed.
GUI can be design as Web, Desktop or Mobile client which'll only query ESP to get json response.
These devices can be used as sensor nodes (Clients) and can be deployed in the field to send data to coordinator (ESP server).
or ready programmed modules can be used to to replace wires .. where RS232 or RS485, ModBus/CAN is being used.
I hope you are expecting same...(?)
uhrheber wrote:There's a function I'd really like to have in the ESP, and I think it would help makers that are not capable of writing their own C code:
The ability to mirror a port pin to that of another ESP8266.
The GUI can already be used to connect one (or more) ESP in station mode to another one in AP mode.
There is absolutely no need to put GUI in ESP. Instead its better to create a server with web API (like IoTSDK) which will only respond with json response.
This will greatly reduce the space requirement and increase the response speed.
GUI can be design as Web, Desktop or Mobile client which'll only query ESP to get json response.
uhrheber wrote:So my suggestion is to add the functionality and the webpage to configure single GPIOs as input or output on the server, and then on the client, connect single GPIOs to that of the server.
So an input of the server would becomes an output of the client, and vice versa. Maybe even with the possibility to map the ADC input to a PWM output on the peer.
The firmware should then exchange the values of the ports in configurable intervals, and/or when the state of an input changes (by polling it, or using the interrupt).
With this functionality, makers could use ESPs as a simple, transparent wireless replacement for wired connections, and tailor it to their needs without writing a single line of code.
Is this understandable/doable?
These devices can be used as sensor nodes (Clients) and can be deployed in the field to send data to coordinator (ESP server).
or ready programmed modules can be used to to replace wires .. where RS232 or RS485, ModBus/CAN is being used.
I hope you are expecting same...(?)
