st0ff3r wrote:
Hi, we are currently using esp's to aquire temperature data coming in via uart.
All the esp's are setup as wifi stations and get ip addresses via dhcp.
They sends the data to a server on the internet via MQTT.
We want to switch from the infrastructure based on existing wifi base stations to the mesh topology in the new sdk from august.
For a start we would like to create a topology like the following:
1. an esp is connected to our existing wifi infrastructure and has an address giving by our dhcp router.
same esp acts as the mesh router
2. two other esp's acts as mesh nodes and are connected to the mesh router using your mesh implementation.
In the above defined scenario can we then expect the following features:
1. mesh nodes are able to be addressed from our existing ip ifrastruture
2. mesh nodes are able to make tcp/ip requests to the exiisting infrastructure through the mesh router.
3. the mesh router will give out addresses to the mesh nodes (what kind of addresses? ip?)
4. the meshnodes will be able to forward packets until they reach their destination in a mesh topology.
1. you can use API(espconn_mesh_server_init) set your server for mesh node, mesh will forward all packet to your server.
2. mesh just supports one server.
3. root device of mesh will addresses the packet to mesh node. We have released the mesh demo on github, please clone the current code:
https://github.com/espressif/ESP8266_MESH_DEMO
we also released the document, you can find it:
https://github.com/espressif/ESP8266_ME ... r/document
please construct mesh packet according the document.
Now, mesh supports HTTP/JSON/MQTT/BIN-STREAM, in addition, mesh supports bcast/mcast/unicast/P2P communicate among nodes.
4. all packets to node working in mesh network will be forwarded automatically to destination node finally.Statistics: Posted by Guest — Fri Mar 04, 2016 11:35 am
]]>